Multiple developers working together on the same sub production instance

[SC9]

We have a situation where multiple developers have to work in the same sub production instance, in different update sets. Sometimes in scoped applications (same table as well, modifying the table schema) and at other times in the same instance on routine admin related tasks such as modifying groups, user records etc -  outside of the scoped app. We are aware of the publish feature of Studio to control versions of a scoped app, but that is not helping our situation here, when we are not working in a scoped app. The order in which each developer commits his/her update set seems to dictate what changes remain. We have had situations where changes made by one developer to the same table is over written by another.  Is anyone else encountering this situation? I have been trying to understand what solutions are available to handle this situation. Would appreciate responses. Thus far we have not been successful battling this situation. Thanks

[Arun81]

Hey SC,

Start using update set batching. It will automatically align the order best on the date of the change. It simplifies the deployment to higher instance with single XML. Have the parent update-set and map it to you child one's. Parent will act as Base update set. You can preview and update the base update-set. Batching feature is available from Jakarta start using it you will love it.

Go through the below community thread.

Update Set Best Practice:

ServiceNow Update Set Batching - Best Practices & Lessons Learnt

This blog is pretty well laid out and covered most of the scenarios.

How to Backup Your Update Sets in 4 Easy Steps

Team Development:

Properly deploy changes using Team Development

[SC9]

Thank you for your response! Will go through the threads!