Webinar #10: Sprint Retrospective Anti-Patterns

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

Solving Impediments as a Team

TL;DR: Solving Impediments as a Team

The main message of the retrospective was clear: there are too many interruptions by stakeholders and the senior management. The interruptions impeded the flow of work through the team. Consequently, achieving the sprint goal had been at risk several times in the past. Moreover, the team missed the sprint goal twice recently. Solving impediments as a team has become a necessity.

Learn more on how to tackle impediments as a team by running experiments and iterating on the solution.

Solving Impediments as a Scrum Team Interruption Buckets v2 — Age of Product Retrospectives

Continue reading Solving Impediments as a Team

The Meta-Retrospective — How To Get Customers and Stakeholders Onboard

TL;DR: The Meta-Retrospective

A meta-retrospective is an excellent exercise to foster collaboration within the extended team, create a shared understanding of the big picture, and immediately create valuable action-items. It comprises of the team members of one or several product teams—or representative from those—and stakeholders. Participants from the stakeholder side are people from the business as well as customers.

Meta-retrospectives are useful both as a regular event, say once a quarter, or after achieving a particular milestone, for example, a specific release of the product. Read more on how to organize such a meta-retrospective.

Meta-Retrospective — Age-of-Product.com

Continue reading The Meta-Retrospective — How To Get Customers and Stakeholders Onboard

Reverse Retrospective — Aligning Scrum Team and Scrum Master

TL;DR: The Reverse Retrospective

Are you—as a scrum master or agile coach—experiencing more communication kerfuffles with “your” team? Is its speed of improvement stalling? Are you under the impression that the team is slipping back into old habits and patterns? Maybe, it is time to run a reverse retrospective where your share your observations with the team.

Learn how to run a reverse retrospective to realign with your scrum team.

Reverse Retrospective — Aligning Scrum Team and Scrum Master

Continue reading Reverse Retrospective — Aligning Scrum Team and Scrum Master

The Overall Retrospective for Team and Stakeholders

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 recommendation 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.

Age of Product: The Overall Retrospective for Team and Stakeholders

Continue reading The Overall Retrospective for Team and Stakeholders

Retrospective Exercises Repository

TL;DR: The Retrospective Exercises Repository

How to prevent retrospective boredom? One way to achieve that is never to repeat the same combination of retrospective exercises twice.

Avoiding repetitions might sound like much work for a single team. However, if your product delivery organization comprises of more than one Scrum team, I can highly recommend creating a retrospective exercises repository as it improves the quality of the retrospectives and saves much time if you share the retrospective exercises with your fellow scrum masters.

Learn how to build such a retrospective exercises repository.

Continue reading Retrospective Exercises Repository