The following 70 Scrum Master theses describe the role of a holistic product creation perspective.
The theses cover the accountabilities of the Scrum Master from product discovery to product delivery in a hands-on practical manner. On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint 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 framework of the 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 often work better than quantitative metrics. At the organizational level, this is reversed: quantitative agile metrics provide better insights than qualitative ones.
Let’s stop guessing and start crowdsourcing data and information on this critical topic: Who is using what metrics under which context to what success? Participate in the agile metrics survey now.
Update 2020-07-21: We reopened the survey! We have joined forces with empiriks.de, a German consultancy specializing in statistical analysis, and we plan to take the study to the next level. The Agile Metrics Survey already complies with academic standards. However, what we need now is more participants to improve the sample size. So far, we have 535 contributors; let’s strive for 1,000 contributions. A first article based on the preliminary findings is already in the works. I will keep you posted!
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 Agile Metrics Survey 2020 Design: Usually, we start an initiative or project by defining what success would look like and how we would learn that we are successful. Which immediately points at metrics of all kinds. This approach is not different for any attempt to become agile, to turn into a learning organization—at least it should not be.
The question is which metrics have been proven to be successful in the past to support that approach. In other words: is there life beyond velocity?
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.
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.
