Yes there is definitely risk and extra work involved, so you need to weigh that against any time savings that could be achieved. My idea was as follows.
- Process ABC already uses Object 123
- Dev2 makes a copy called Object123.1 and adds new pages to it.
- If Dev2 needs to spy new elements, he creates a new branch in the application model and adds all new elements under it.
- Dev2 makes sure not to amend any existing elements or pages.
- To test his new object, DEV2 makes a new temporary 'test rig' process.
- When ready, Dev2 uses copy&paste to transfer the new pages and elements back into the original object.
In my experience it's best to create multiple small objects in order to reduce the likelihood that two developers both need to make changes to the same object at the same time. This won't eliminate the problem but there's more chance Dev2 won't be stuck waiting for Dev1 to complete his work. It will also make testing and implementation easier to manage.
------------------------------
John Carter
Professional Services
Blue Prism
------------------------------
