✋ Do Not Miss Out: Join the 10,000-plus Strong ‘Hands-on Agile’ Slack Team Have you been overly protective in your Scrum Master career? Please share your reasons with us in the comments. Being overly protective is a Scrum Master anti-pattern. Moreover, being accountable for the team’s effectiveness does not mean shielding the team from every problem or challenge. However, “causing the removal of impediments to the Scrum Team’s progress” does not imply solving any issue on behalf of the Scrum Team. Scrum thrives when the Scrum teams are self-managing while Scrum Masters embrace their role as servant-leaders. When the Scrum Master Fails by Being Overly Protective - Conclusion (I still like “become a servant-leader” better…) Instead, relax and let the team evolve, experience problems, and learn how to solve them. The Solution: Stop ordering stickies or booking meeting roomy. They tend to tolerate damaging behavior from a team member in the (futile) hope the culprit will be insightful and improve over time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |