Домой United States dc3 United States software in english pdf Scrum Master Anti-Patterns

Scrum Master Anti-Patterns

271
0
ПОДЕЛИТЬСЯ

Scrum Master Anti-Patterns: From Ill-suited Personal Traits to Complacency to Pursuing Individual Agendas.
Join the DZone community and get the full member experience. The reasons Scrum Masters violate the spirit of the Scrum Guide are multi-faceted. Typical Scrum Master anti-patterns run from ill-suited personal traits to complacency to pursuing individual agendas to frustration with the team itself. Read on and learn in this post on Scrum anti-patterns how you can identify if your Scrum Master needs support from the team. Before we start dissecting probable reasons and manifestations of Scrum Master anti-patterns, let us revisit how the Scrum Guide defines the role of the Scrum Master: The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. The Scrum Master is accountable for the Scrum Team’s effectiveness. They do this by enabling the Scrum Team to improve its practices, within the Scrum framework. Scrum Masters are true leaders who serve the Scrum Team and the larger organization. Source: Scrum Guide 2020. The keystone of the definition of the Scrum Master role is the leadership aspect. (Too bad, it is no longer called “servant leadership;” I found that description to be better suited.) Unfortunately, in most cases of Scrum Master anti-patterns, it is precisely this idea that an individual is not meeting. (See also the detailed lists of services rendered to the Product Owner, the Developers, and the organization by the Scrum Master as defined by the Scrum Guide.) The reasons Scrum Masters violate the spirit of the Scrum Guide are multi-faceted. They run from ill-suited personal traits to pursuing their agendas to frustration with the Scrum team. Some often-observed reasons are: In my eyes, ‘agile management’ is an oxymoron. The primary purpose of any agile practice is empowering those closest to a problem with finding a solution. In other words, the team shall become self-organizing over time, thus contributing at an appropriate level to the business agility of the organization. Self-organizing teams need coaches, mentors, and servant leaders, however, not a manager in the taylorist meaning of the word. Watch out for the Scrum Master anti-patterns corresponding to this ‘agile manager’ attitude: The following anti-patterns focus on the Sprint Planning: The following Scrum Master anti-patterns focus on the mishandling of the Sprint itself: The final set of Scrum Master anti-patterns addresses the Sprint Retrospective: There are plenty of possibilities to fail as a Scrum Master. Sometimes, it is the lack of organizational support. Some people are not suited for the job. Others put themselves above their teams for questionable reasons. Some Scrum Masters simply lack feedback from their Scrum Teams and stakeholders. Whatever the case may be, though, try and lend your Scrum Master in need a hand to overcome the misery. Scrum is a team sport. What Scrum Master anti-patterns did I miss? Please share it with us in the comments. The video of the webinar is available now: Note: If the browser will not start the video automatically, click here to watch the replay of the webinar Scrum Master anti-patterns directly on Youtube. Published at DZone with permission of Stefan Wolpers, DZone MVB. See the original article here. Opinions expressed by DZone contributors are their own.