hi @Diyab 

I recommend to define clear ownership of each module and maintain effective communication between teams. Proper documentation and component reusability are essential for a sustainable solution, and, most importantly, ensure that your application is architected properly for long-term success.

Best wishes 

S

Hello,

First of all this is required more collaboration between two times and high communication and this may be happened between team leaders and including some team members if needed.

- Its better to make each team to create and work into different OutSystems applications in case this is applicable and you can create separate application for one functionality.

- If its required to work in same OutSystems application try to make each team work in a separate module if its possible.

- During development if more than one developer working in same module, they have take care in case they get any conflict while they are publishing their changes. They may need to sit with the other team developer to fix this conflict to make sure doesn't override important changes.

- Testing application after integrating the work done by two teams

- Two teams need to align before any deployment and create deployment plan together.

Please also check below links: 

https://www.outsystems.com/forums/discussion/83105/can-2-teams-work-on-same-application-branches-and-merge-code-after-sit/

https://success.outsystems.com/documentation/best_practices/architecture/building_mobile_apps_with_multiple_independent_teams/best_practices_with_multiple_teams/

Hey @Diyab 

Please consult this Outsystems Documentation regarding Application Sponsorship and Ownership.

I think this will help you!