TL;DR: How to Measure Agility of Organizations and Teams
Is every organization suited to become ‘agile?’ If so: How to measure agility? And if not: Wouldn’t it be great figuring that out before embarking on a futile and expensive journey?
On February 3rd, 2018, 20-plus people will join a hackathon to build an agility assessment framework based on this taxonomy. The goal of the workshop is to provide the first version of a tool that empowers agile practitioners to measure agility, be it an organization’s suitability for agile practices or a team’s progress on its path to becoming agile.
The following 70 scrum master theses describe the role of the scrum master from a holistic product creation perspective.
The scrum master theses cover the role of the scrum master from product discovery to product delivery in hands-on practical manner. On the one side, they address typical scrum ceremonies such as sprint planning, sprint review, and the retrospective. On the other hand, the scrum master theses also cover, for example, the relationship with the product owner, they deal with agile metrics, and how to kick-off an agile transition, thus moving beyond the original scrum guide.
Suitable agile metrics reflect either a team’s progress in becoming agile or your organization’s progress in becoming a learning organization.
At the team level, qualitative agile metrics typically work better than quantitative metrics. At the organizational level, this is reversed: quantitative agile metrics provide better insights than qualitative ones.
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, which may include third party cookies, to improve your browsing experience and deliver personalized marketing content. To find out more, including how to disable the cookies, read our Cookie Policy. By continuing to browse this website, you agree to our use of cookies.Got it!
