The Scrum Guide Reordered

TL;DR: The Scrum Guide Reordered

The Scrum Guide Reordered is based on about 90 percent of the text of the 2017 Scrum Guide, extending its original structure by adding additional categories. For example, you will find all quotes that can be attributed to the role of the Scrum Master in one place. While the Scrum Guide is mainly focused on the three roles, five events, and three artifacts, I aggregated quotes on specific topics as well, for example, on self-organization, finance or technical debt.

The Scrum Guide–Reordered allows you to get a first understanding of Scrum-related questions quickly. For example, it is good at relating a specific topis — say “stakeholder” — with Scrum first principles such as Scrum Values, or empiricism.

Scrum Guide Reordered — Age-of-Product.com

Continue reading The Scrum Guide Reordered

Liberating Structures for Scrum (1): The Sprint Retrospective

TL;DR: Liberating Structures for Scrum: The Sprint Retrospective

Liberating Structures Sprint Retrospective: A few weeks ago, I started an event series with my Berlin-based Hands-on Agile Meetup group on how to improve Scrum events utilizing Liberating Structures — a set of easy to learn, yet powerful ways to collaborate as a team. The results have been fantastic so far, and I like to share these outcomes with those who cannot participate in person.

In this first post, learn more on how you can use Liberating Structures strings to improve the level of collaboration and engagement at Sprint Retrospectives.

Liberating Structures for Scrum (1): The Sprint Retrospective — Age-of-Product.com

Continue reading Liberating Structures for Scrum (1): The Sprint Retrospective

Webinar #10: Sprint Retrospective Anti-Patterns [Video]

TL;DR: Webinar Sprint Retrospective Anti-Patterns

The tenth Hands-on Agile webinar sprint retrospective anti-patterns covers twelve anti-patterns of the sprint retrospective—from #NoRetro to the dispensable buffer to UNSMART action items to a missing product owner.

Webinar Sprint Retrospective — Hands-on Agile Webinar #10

Continue reading Webinar #10: Sprint Retrospective Anti-Patterns [Video]

Scrum Master Trends Report 2019 — Free Download

TL; DR: Scrum Master Trends Report 2019

Back in 2017, we started the Scrum Master Salary Report 2017—the first industry report that covered in depth the educational background, working experience, industries, and organizational details of the companies Scrum Masters or agile coaches work for. For its 2019 edition—the Scrum Master Trends Report 2019—, we partnered with Scrum.org—the leading Scrum training and certification institution founded by Scrum co-founder Ken Schwaber—to improve the underlying data set.

Learn more about the state of the industry and download for free the Scrum Master Trends Report 2019.

Scrum Master Trends Report 2019 by Scrum.org and Age-of-Product.com

Continue reading Scrum Master Trends Report 2019 — Free Download

Agile Failure Patterns in Organizations 2.0

TL;DR: Agile Failure Patterns — Why Agile is Simple and Complex at the Same Time

Agile failure seems to be increasingly more prominent nowadays despite all the efforts undertaken by numerous organization embarking on their journeys to become agile.

The funny thing is: Who would disagree that the four core principles of the Agile Manifesto

  1. Individuals and interactions over processes and tools
  2. Working software over comprehensive documentation
  3. Customer collaboration over contract negotiation
  4. Responding to change over following a plan

— are derived from applying common sense to a challenging problem? Moreover, the application of those principles might be suited to fix numerous organizational dysfunctions and reduce an error-prone and complex social setting to maybe just a complicated one?

Age of Product: Agile Failure Patterns in Organizations

Continue reading Agile Failure Patterns in Organizations 2.0

Technical Debt & Scrum: Who Is Responsible?

TL;DR: Technical Debt & Scrum

If technical debt is the plague of our industry, why isn’t the Scrum Guide addressing the question of who is responsibly dealing with it? To make things worse, if the Product Owner’s responsibility is to maximize the value customers derive from the Development Team’s work, and the Development Team’s responsibility is to deliver a product Increment (at least) at the end of the sprint adhering to the definition of “Done,” aren’t those two responsibilities possibly causing a conflict of interest?

This post analyzes the situation by going back to first principles, as laid out in the Scrum Guide to answer a simple question: Who is responsible for keeping technical debt at bay in a Scrum Team?

Technical Debt & Scrum: Who Is Responsible?

Continue reading Technical Debt & Scrum: Who Is Responsible?