TL; DR: Faking Agile Metrics — An Eye-Opening Exercise
Imagine you’re a Scrum Master and the line manager of your team believes that the best sign for a successful agile transformation is a steady increase in the Scrum Team’s velocity. Moreover, if the team fails to deliver on that metric something is wrong with the Scrum Team. Alternatively, something is wrong with you as you are the Scrum Master and hence responsible for the team’s performance. (Apparently, not faking agile metrics, or being transparent in this case, does not seem to be valued here.)
Learn more about how to coach these kinds of line managers and help them overcome their preference for the industrial past with a simple exercise on how to cook the agile books.
The Fine Line Between Risk Mitigation and Falling Back into Covering Your Butt
The team hasn’t met its commitments once. Not once.
The atmosphere was becoming thicker by the minute. The management was displeased with the progress of the project and was looking for answers, starring at a bunch of Jira charts, I prepared earlier. “How can we claim that we are working in Scrum mode if the team is not sticking with the rules?”
Throughout the majority of projects I have been working on I could observe an obsession with burn-down charts and other Scrum metrics, mainly team commitments. And as a consequence, a side product of backlog grooming, estimation, and sprint planning is elevated to the most important management indicator that “Agile” works: The team’s commitment is matching or outperforming its average velocity.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
