Comic Agilé no. 177 - Involving the Scrum Master (reshare) The Scrum Master is a true leader who serves the Scrum Team and the larger organization by, e.g., causing the removal of impediments to the Scrum Team’s progress, the Scrum Guide states—and reorganizations are inevitable impediments. More and more Managers are starting to understand that the Scrum Master should be involved before making any changes to the team. However, they’re generally involved way too late. Let’s teach our Managers that Scrum Masters are Agile Coaches; someone who can contribute to not only implementing reorganizations, but also to designing it by answering the why, how and what of reorganizing. Especially in regards to removing systemic impediments, such as cross-team dependencies where several Scrum Teams might be affected by the change, is something that Scrum Masters feel the consequence of on a daily basis, so they’ll not only have the motivation, but also insights to properly address. #agile #scrummaster #comicagile
The question is still why should there be a reorg of the teams to begin with? To split wellfunctioning and selfmanaging teams can be disastrous to productivity, not to mention morale of the team members. By doing this the company will guarantee a productivity reduction for 3-6 months, at least, as learning to work with new team members takes time, both on skill and trust level. I can understand why companies may do this if there is a shift in product, like pivotng, but otherwise I don't think that it is a good idea. And in the end, not involving the Scrum Master is definitely a recipe for low productivity and loss of product completion.
How'bout?...