Product Retrospectives TIPS

GET THE LATEST TIPS EACH WEEK

Get product resources, conference updates, along with access to an exclusive Slack channel by subscribing below.

My Product Management toolkit: ‘pre-mortem’

Marc Abraham has an idea — flip the discussion on its head. Instead of waiting until after a product launch, why not make assumptions before building the product on why it theoretically failed. “A pre-mortem thus enables you to start working backward, and look at the individual factors that could lead to failure”.

How to conduct a productive launch retrospective meeting

Heather McCloskey also gives guidance on how to structure these discussions.

What’s the best way to run a post-mortem review of a product launch?

Josh Elman has shared tips that he has learned from talented product people he knows how to structure a launch post-mortem. First, he implores, is that you don’t call it a post-mortem (no one died). A product retrospective is better. And then center the conversation on your team organizing things that went awesome, ok, and not-so-good.

The product owners guide to the sprint retrospective

Even if a separate retrospective does not exist, a Product Manager can get a lot of value from a scrum retrospective. Roman Pichler encourages you to take part, be an active participant and improve the wider collaboration.

Why we need a product retrospective

Retrospectives are a key part of Agile Engineering, and a Product Manager can play a role in them, but Marc Abraham argues that there should be a separate product retrospective. During these regularly staged exercises, the product team will ask themselves how the product is performing, what users are saying, what product ideas people have, and other questions. He also suggests a structure to follow for these retrospective meetings.