Survey Results: Scrum Master Problem Dealing

TL;DR: Scrum Master Problem Dealing — The Survey Results

Scrum Master Problem Dealing: We all know it; changing the way we work is extremely difficult. It requires us to find novel solutions to wicked challenges, to deal with cultural baggage (‘the way we do things here’) and to bring along the people needed to make a change successful. And yet, this difficult challenge is a core responsibility of Scrum Masters: How can your organization work effectively with Scrum if it is not considering the entire system?

But how do Scrum Masters and Agile Coaches go about this? What strategies do they use to change the system? Who are their most important allies? And what else can we learn from them?

We teamed up with The Liberators to identify what works in the field. We gathered both quantitative as well as qualitative data from a survey completed by over 200 participants.

Survey Results: Scrum Master Problem Dealing — Age of Product

Continue reading Survey Results: Scrum Master Problem Dealing

Liberating Structures for Scrum (2): The Sprint Planning

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

The third Liberating Structures Scrum meetup addressed the Sprint Planning, more precisely the reasons why Sprint Plannings fail—despite all the efforts put into them in advance, from the Product Backlog refinement to the Sprint Review.

Liberating Structures for Scrum: The Sprint Planning — Hands-on Agile

Continue reading Liberating Structures for Scrum (2): The Sprint Planning

Liberating Structures 4 Scrum Workshop — From Daily Scrum to Sprint Review

TL;DR: Liberating Structures 4 Scrum Workshop

Join us for an exciting Liberating Structures Scrum workshop on July 6th, 2019 in Berlin. We will be exploring several microstructures, weave them into strings and apply those to Scrum events like the Daily Scrum, the Sprint Review, or the Sprint Retrospective. The workshop language will be English.

Liberating Structures 4 Scrum Workshop — From Daily Scrum to Sprint Review.

The Liberating Structures 4 Scrum workshop will take place at the Alte Kantine Wedding on Saturday, July 6th, 2019, from 9 am to 5 pm.

Continue reading Liberating Structures 4 Scrum Workshop — From Daily Scrum to Sprint Review

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]

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?