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?
Back in October and November 2017, I ran a survey to identify contributing factors to an organization’s or a team’s agile maturity. In total, 86 people participated. Based on their answers, I aggregated a preliminary taxonomy of agility related factors.
This taxonomy was first presented on the Hands-on Agile Berlin meetup on November 30th, 2017.
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.
🏖 & 📖: Free Download of ‘How to Get Hired as a Scrum Master’ as a Kindle Ebook on Amazon
Summer 2019 is coming, and I like to give away two Kindle ebooks you might consider adding to your reading list. From today until next Monday, that is June 20–24th, 2019, ‘ How to Get Hired as a Scrum Master’ will be available for free on Amazon: Download your copy of ‘How to Get Hired as a Scrum Master’ now.
Check also for ‘Lean User Testing.’ This title is also available for free in Amazon’s Kindle shop.
TL;DR: Scrum Master Career: How to Get Hired as a Scrum Master
Scrum Master Career: How to Get Hired as a Scrum Master: From Job Ads to Your Trial Day — Learn How to Pick the Right Employer or Client details how Scrum Masters and Agile Coaches can systematically identify suitable employers or clients to avoid mismatches and disappointments at a later stage. If you are planning a career move into the Scrum Master profession, don’t miss out on these tips.
Scrum Master Career: How to Get Hired as a Scrum Master is currently available as a Kindle ebook. Shortly, the paperback version will be available, too.
TL;DR: The Overall Retrospective
After rebuilding an existing application on a new tech stack within time and under budget our team had an overall retrospective with stakeholders this week to identify systemic issues. We found more than 20 problems in total and derived eight detailed recommendations the organization will need to address when moving forward to the next level of agile product creation.
Read on and learn how we achieved this result in under two hours with an overall retrospective attended by 16 people.
TL;DR: Product Discovery Anti-Patterns
Scrum has proven to be an effective product delivery framework for digital products like applications or apps. However, Scrum is equally suited to build the wrong product efficiently as its Achilles heel has always been the product discovery part. What product discovery part, you may think now. And this is precisely the point: The product owner miraculously identifies what is the best way to proceed as a team by gating and prioritizing the product backlog. How that is supposed to happen is nowhere described in the Scrum Guide. Consequently, when everyone is for himself, product discovery anti-patterns emerge.
From sunk costs, HIPPO-ism, my-budget-my-features to self-fulfilling prophecies — learn more about the numerous product discovery anti-patterns that can manifest themselves when you try to fill Scrum’s product discovery void.
TL;DR: Participate in the Agile Maturity Survey to Help Us Understand Agile Maturity’s Nature
Participate in the anonymous agile maturity survey and help us find out: Is agile maturity a fad, a trend or the holy grail of an agile transition?
(Update 2017-12-02: The preliminary results of the agile maturity survey are available, see below.)
TL;DR: The Scrum Master Theses
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 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 Scrum Guide.