--- title: Effective working practices for multi-team environments url: "https://b13.com/knowledge/how-to-involve-multiple-teams-in-typo3-projects-efficiently" description: Our top tips for getting everyone pulling in the same direction across developer teams—whether external or internal. image: "https://b13.com/fileadmin/_processed_/9/0/csm_multi-team-environment_191-1_7182b201bf.png" date: 2023-03-09 modified: 2026-08-19 lastUpdated: 2026-08-19 --- # Effective working practices for multi-team environments [ Open Source ](https://b13.com/knowledge/open-source) [ Project Management ](https://b13.com/knowledge/project-management) [ TYPO3 ](https://b13.com/knowledge/typo3) How to Involve Multiple Teams in TYPO3 Projects Efficiently ============================================================= Get everyone pulling in the same direction ![](https://b13.com/fileadmin/_processed_/a/d/csm_david_5ce18d41e2.jpg)David Steeb 29 March 2023 [ RSS Feed ](https://b13.com/rss.xml) ![Multiple hands in various colors reach towards four interlocking puzzle pieces, symbolizing collaboration and teamwork. The puzzle pieces are orange and red, set against a dark green background.](https://b13.com/fileadmin/_processed_/0/3/csm_multi-team-environment_757bbab8a0.webp) Large organizations and agencies face the same challenge: it’s one thing to get everybody tugging on the same rope—but it’s another to have them pull in the same direction. This is all the more difficult when you have several development teams that need to work together. We are often asked to be an external partner to internal developer teams. People need us to get their development workflows in shape and review their code. Here are the tools we use to maximize productivity in multi-team environments. You can adopt our approach within a single company, or when involving external teams of freelancers or agencies. Our approach minimizes confusion, shortens onboarding processes, and means no more overwriting each other’s code! Find out how we upskill BRAND staff and optimize their TYPO3 development processes! ------------------------------------------------------------------------------------- [ Read Case Study ](https://b13.com/services/success-stories/brand-brings-typo3-expertise-in-house) Git and Gitlab for code collaboration and change tracking ----------------------------------------------------------- [Git](https://git-scm.com/) is the version-control system we use for tracking changes to code and collaborating within teams. A developer fetches their own copy of a project’s code, works on their own branch, explains what they’ve done so other developers can understand the changes, and merges their work into the staging environment. We have a wide range of best practices—honed through our work on TYPO3 Core—that minimize errors and maximize transparency. In particular, our “one feature per branch” stops one change holding up others, and helps us debug faster. Although each developer has their own copy of the Git repository, the repository needs to be hosted centrally so everyone can copy the latest version. We choose [GitLab](https://about.gitlab.com/) because the code behind it is open source, so it aligns with our values as a company. Alternatively, you can use [GitHub](https://github.com/), which is closed-source and owned by Microsoft. Our product managers have a good understanding of Git too, because some of them quite frequently add changes to a project, especially for things like labels and localized strings. This gives them a good understanding of how the development process works. Local development environment ------------------------------- Our TYPO3 developers often have to modify code, for example: - Debugging - Refactoring (optimizing code for performance or readability) - Adding features - Installing third-party code (such as a TYPO3 extension or integration) - Updating TYPO3 Core or extensions If developers did this on the live site, the chances are there would be outages when things misfire—which would be stressful for everyone involved. Additionally, only one person would be able to work on the site at a time to avoid overwriting each other or causing adverse effects. There are so many things that could go wrong! Which is why we never do it. Instead, each developer grabs a copy of the live site, runs it on their own machine, and makes any changes there. Local test server mirrors live environment -------------------------------------------- Another advantage of local development is that all code can be tested before being integrated with the work of other developers. Automated testing ensures bugs or breakages that might be easily overlooked can be weeded out. It’s a great help to eliminate bugs before code gets merged because debugging is more difficult if you don’t know which changes are the cause. To this end, each developer has their own local test server that mirrors the online site. At the click of a button, they can import the live database so the code gets tested in real-world conditions. Merge request and staging environment --------------------------------------- In many projects, our role is to sign off code before it gets deployed. We check the code to make sure it’s in line with the style requirements that make code easier for unfamiliar developers to understand, and eliminate any obvious errors. At this stage, though, we don’t perform functional testing—in other words, checking that the code actually works. (That should be done by the developer themselves before merging, and finally when the code is integrated into the stage environment.) If the merge request is accepted, the code gets merged into the staging environment—a process that is fully automated. This is where the work of all the team members is pulled together. Even if each individual change doesn’t break anything, we now need to check that everything works when the changes from developers in different teams have been merged together. We thoroughly test for security and functionality, using a combination of automated tests and manual user tests. Finally, the code can be deployed. We do this automatically: it’s a question of changing a tag in Git. Adopt best practices to improve cross-team working ---------------------------------------------------- Over the years, we’ve learned techniques for standardizing our work. Primarily, this reduces the time developers have to invest when trying to understand someone else’s code—a scenario that is more likely the larger the number of developers and teams. Our top tips are: - **Adopt and apply coding standards:** We adhere to the [coding guidelines](https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/CodingGuidelines/Index.html) stipulated for working on the TYPO3 project. Consistency within organizations is great because code is familiar to whoever wrote it, but having agreed standards across organizations is a huge bonus. If you hire new TYPO3 developers or change your agency, then they will probably already be familiar with your coding standards, so onboarding is faster. - **Use standardized commit messages**: For every Git commit, a developer has an opportunity to explain what they have done. We do these in a standardized format, and link each change to a ticket, so an unfamiliar developer can see exactly what has been done, when, and why. This is a huge help when retracing steps to debug code or make changes in the correct manner. - **Encourage a culture of communication**: Alongside code comments and commit messages, communication is key to working together and a pillar within our company culture. Sometimes it’s a question of a friendly tap on the shoulder or picking up the phone to unblock an issue; but be mindful that developers need to concentrate for long periods of time so asynchronous communication should be preferred. Establish excellent processes to get the most out of your development teams ----------------------------------------------------------------------------- TYPO3 grows with your needs as an organization, and as your project becomes bigger you are more likely to involve more people—including other teams. A thought-through, standardized process makes it much quicker to onboard new people and to get all teams pulling in the same direction. Do you need to involve internal teams or external agencies in your development process? ----------------------------------------------------------------------------------------- Get in touch to find out how we can help! [ Let’s Connect ](https://b13.com/lets-connect) ### Written by: ![Bild von David Steeb](https://b13.com/fileadmin/_processed_/a/d/csm_david_cf042ebb7f.webp) b13 Founder and CEO, David, is someone you’ll meet if you’re thinking about working with our agency. He is constantly learning new skills and is an influential part of our cutting-edge frontend practice. David Steeb CEO [ more from David Steeb ](https://b13.com/team/david-steeb) Related Articles ------------------ - ![A purple graphic featuring a smartphone icon with three horizontal bars, surrounded by illustrations of vintage telephones.](https://b13.com/fileadmin/_processed_/2/5/csm_EXTphonenumber_Headerbild_93d5de1696.webp) ### Clean Phone Numbers in TYPO3: Why We Built EXT:phone\_number 11 August 2026 | David Steeb TYPO3 stores phone numbers as tel: links, but doesn’t format them for output. Meet EXT:phone\_number, a Fluid ViewHelper for clean, consistent numbers. [ Read more: Clean Phone Numbers in TYPO3: Why We Built EXT:phone\_number ](https://b13.com/knowledge/clean-phone-numbers-in-typo3) - ![Cartoon trophy character surrounded by hands giving thumbs up and a heart gesture, set against a gear-patterned background.](https://b13.com/fileadmin/_processed_/f/7/csm_T3ppy_Design_Kit_Headerbild_b51eb9dc31.webp) ### T3ppy Gives TYPO3 a Friendly Face 06 August 2026 | Florian “Flix” Keitgen TYPO3 is powerful—but it doesn’t have to feel impersonal. Meet T3ppy, our friendly companion for the backend. [ Read more: T3ppy Gives TYPO3 a Friendly Face ](https://b13.com/knowledge/t3ppy-design-kit) - ![Gavel labeled "AI" on a circuit-patterned background with yellow stars, symbolizing regulation or legislation related to artificial intelligence in the EU.](https://b13.com/fileadmin/_processed_/1/0/csm_EUAIAct_Headerbild_510724b3de.webp) ### AI Content in TYPO3: Labelling Needs Accountability 02 August 2026 | Benni Mack The EU AI Act brings the origins of AI-generated content into focus. AI Label marks AI-generated and AI-edited content in TYPO3 and records who signed off the published version—for… [ Read more: AI Content in TYPO3: Labelling Needs Accountability ](https://b13.com/knowledge/ai-content-in-typo3-labelling-needs-accountability) - ![Hands holding puzzle pieces are positioned around a partially completed puzzle depicting a computer interface.](https://b13.com/fileadmin/_processed_/d/7/csm_StopBuyingPlatforms_Headerbild_8a41a82f8a.webp) ### Stop Buying Platforms. Start Building Ecosystems. 09 June 2026 | David Steeb The first TYPO3 Summit North America opened with a keynote that reframes how enterprise teams should think about content management—from platforms to ecosystems, from vendor… [ Read more: Stop Buying Platforms. Start Building Ecosystems. ](https://b13.com/knowledge/stop-buying-platforms-start-building-ecosystems) - ![Colorful fish illustrations surround a central logo that reads "TYPO3 Summit.](https://b13.com/fileadmin/_processed_/4/3/csm_NorthAmericaSummit_Headerbild_5fbbbbb529.webp) ### Notes from Atlanta—What the First TYPO3 Summit North America Says About the Next Decade of Enterprise CMS 22 May 2026 | David Steeb Field report from the first TYPO3 Summit North America in Atlanta. On governance that can’t be acquired, predictable seven-year lifecycles, the FAIR distribution layer, and why the… [ Read more: Notes from Atlanta—What the First TYPO3 Summit North America Says About the Next Decade of Enterprise CMS ](https://b13.com/knowledge/atlanta-typo3-summit-north-america-enterprise-cms) - ![A series of stylized figures in various poses, each with a distinctive orange hat, depict a progression from walking to standing still while looking at a phone, set against a purple grid background.](https://b13.com/fileadmin/_processed_/d/7/csm_QueuesDDEV_Headerbild_f640931350.webp) ### Better scalability with decoupled queues: How to set up RabbitMQ with TYPO3 10 April 2024 | Jochen Roth When built-in message transports hit their limits, RabbitMQ can provide TYPO3 with a scalable, robust message queue. [ Read more: Better scalability with decoupled queues: How to set up RabbitMQ with TYPO3 ](https://b13.com/knowledge/better-scalability-with-decoupled-queues-how-to-set-up-rabbitmq-with-typo3) - ![A rocket labeled "V14" launches into the sky, surrounded by a group of people celebrating with raised arms.](https://b13.com/fileadmin/_processed_/3/d/csm_v14_Celebration_Headerbild_3d4170fdc5.webp) ### Happy Release Day TYPO3 v14: Why This Release Shows the True Strength of Open Source 21 April 2026 | Florian “Flix” Keitgen TYPO3 v14 improves workflows for editors, marketing teams, and developers—and shows how community-driven open source creates real impact. [ Read more: Happy Release Day TYPO3 v14: Why This Release Shows the True Strength of Open Source ](https://b13.com/knowledge/happy-release-day-typo3-v14-why-this-release-shows-the-true-strength-of-open-source) - ![A cartoon character resembling a shield gives a thumbs up in front of a computer interface with various menu options.](https://b13.com/fileadmin/_processed_/e/6/csm_Header_cda1f80173.webp) ### Meet T3ppy: A New Era for Editorial Work in TYPO3 01 April 2026 | Florian “Flix” Keitgen T3ppy and the AiM extension bring AI directly into the TYPO3 backend—enhancing SEO, content quality, and workflows with centralized control. [ Read more: Meet T3ppy: A New Era for Editorial Work in TYPO3 ](https://b13.com/knowledge/meet-t3ppy-a-new-era-for-editorial-work-in-typo3) - ![Four file folders displaying a bar graph with orange bars, set against a light blue background with abstract document outlines.](https://b13.com/fileadmin/_processed_/7/2/csm_PageInfoTabs_Headerbild_1e3eda44e5.webp) ### Taming the Page Module Header—Why We Built EXT:page\_info\_tabs 31 March 2026 | David Steeb When multiple TYPO3 extensions add content to the page module header, things quickly become messy. EXT:page\_info\_tabs structures everything into clean Bootstrap tabs, with zero… [ Read more: Taming the Page Module Header—Why We Built EXT:page\_info\_tabs ](https://b13.com/knowledge/taming-the-page-module-header-why-we-built-extpage-info-tabs) - ![Retro microphone illustration with a shopping cart icon in the background, symbolizing e-commerce or online shopping.](https://b13.com/fileadmin/_processed_/f/8/csm_Marketplace_Headerbild_ee1575614c.webp) ### Why TYPO3 Needs a Marketplace for Products 25 March 2026 | Florian “Flix” Keitgen A marketplace would make TYPO3 products more discoverable, easier to compare, and benefit both agencies and clients alike. [ Read more: Why TYPO3 Needs a Marketplace for Products ](https://b13.com/knowledge/why-typo3-needs-a-marketplace-for-products)