Remove retrospective
article thumbnail

Three Hidden Problems That can Ruin Your Agile Retrospectives

Mind the Product

Scrum.org defines a sprint retrospective as a time at the end of each sprint where the team discusses what went well, what could be improved, and aligns on specific actions the group can commit to improving for the next sprint. Retrospectives are an essential part of any organization running agile software development.

Agile 179
article thumbnail

Running your retrospective meetings, the right way

Mind the Product

A retrospective meeting can benefit any team, irrespective of whether you follow Agile or not. This article gives an overview of conducting retrospectives efficiently and can also be applied to our personal lives. [.]

Agile 149
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Remote Agile (Part 5): Retrospectives

The Product Coalition

Remote Agile (Part 5): Retrospectives with Distributed Teams TL; DR: A Remote Retrospective with a Distributed Team We started this series on remote agile with looking into practices and tools, followed by exploring virtual Liberating Structures, how to master Zoom as well as common remote agile anti-patterns.

Agile 78
article thumbnail

Data-Informed Retrospectives

The Product Coalition

TL; DR: Data-Informed Retrospectives In their book Agile Retrospectives , Esther Derby and Diana Larsen popularized the idea that a Sprint Retrospect comprises five stages. The second stage refers to gathering data so that the Scrum Team can have data-informed Retrospectives.

article thumbnail

Nine Agile Antipatterns That Lead To Disaster

The Product Coalition

Agile antipatterns or scrum antipatterns are (poor) practices that are utilized to enhance a process. Nonetheless, they impede your efforts and slow your progress towards attaining Agile objectives, thereby achieving the opposite effect. List of destructive agile antipatterns and how to avoid them 1.

Agile 118
article thumbnail

The Blame Game Retrospective

The Product Coalition

TL; DR: The Blame Game Retrospective There are plenty of failure possibilities with Scrum. Turning the Sprint Retrospective into a Blame Game Retrospective demonstrates a Scrum team’s lack of skills and professionalism. You can sign up here for the ‘Food for Agile Thought’ newsletter and join 31,000-plus other subscribers.

article thumbnail

Successful Agility In Product Delivery Requires Dynamic Implementation

The Product Coalition

Challenging an emerging myth that Agile is dead, and providing insight on key principles & tactics to finding success with Agile-based product teams. Nowadays it seems to have an opinion of Agile product methods like Scrum. Agile methods like Scrum are not a one-size-fits-all framework.

Agile 109