It sounds great doesn’t it, no more dependencies to manage, and complete control of everything you need to deliver within your team

When this is possible AND done right,  the impact can be huge, for instance

✅ No more relying on another team to complete and release config and small changes, complete these tasks as part of your deliverable and release.

✅ Or, if you have a constant flow of tasks that need a specific skill set within another team, onboard a new team member with the skills and take control.

BUT, as always you should think twice before you leap. 

Before you bring extra work into your team

⚠️ Consider the impact on your roadmap. Are the work items small enough to absorb into your team, or will doing this impact on your main objectives?

⚠️ Be sure that you are not creating a dependency for the original team to manage. The new arrangement may be great for your team, but if you accidentally slow down the original team then you will not be popular. 

Before you bring in new team members 

⚠️ Be sure that you have a steady flow of work to keep them busy. Else they may well become bored, frustrated and leave. 

⚠️ If you are struggling to provide the right type of work for your new team member then you may be  tempted to ask them  to reskill and  be ‘T shaped’, will they be interested in this though? Find out before you move them into your team.