I hope this video was helpful. If you need support and guidance on your professional journey, check out my guides and templates: store.scrummastered.com/collections/all Subscribe to my newsletter to get updates on new stuff and special offers: scrummastered.com/free-downloads/
@ToriMarinucci Жыл бұрын
This is always an interesting topic. I did want to talk about teams that have a lot of interdependencies/blockers between each other. IMO - it's useful for intertwined teams to build relationships and remove dependencies between each other directly. As a SM, I don't want to be the middle man for that & become a blocker myself. I am scrum master for a few service teams (ops/big data, etc.). Big Data used to have many blockers w/ Operations - permissions for data, pii security, etc. Early on I'd handle coordinating with outside teams to remove dependencies, but over time I'd introduce BD to Operations and ask them to coordinate dependency removal. Since they built a relationship, team members learned how to remove their own cross-team impediments while also learning how to best schedule work with the 'blocking team'. I was no longer needed (much) as the middle woman. :) Also, we generally have a lot less blockers because BD members and this other team automated processes to make us less interdependent. Note: This is a 3 year old team so it took awhile to get here!
@ScrumMastered Жыл бұрын
Yes, that's the approach to take. You can start by being the middle man at first, but you also want to help your team become more self-organized and stop depending on you for resolving blockers that they often can resolve themselves.