Scrum Product Owner Spotter’s Guide11-12-2023
Fact-Driven Retrospectives (FDR)13-12-2023
Do your retrospectives lack energy? Let’s take a quick look at what the “retro” is supposed to accomplish and discover what’s usually missing. Usually it’s purpose. Includes one thing the Scrum Guide got right, and one it got wrong.
We do retrospectives to improve our quality and effectiveness. (The Scrum Guide really only got right in the 2020 edition.) Remind your team why you are holding this event, and check the output against the purpose before you’re done.
The Retrospective is for Scrum Team and anyone else they choose to invite, according to the Guide.
I think the Scrum Guide got this one wrong.
For me, the Retrospective is for the Developers, and anyone they choose to invite. If the Developers have issues with their Scrum Master or Product Owner, the retro is an obvious place to discuss it – if it is a safe space. Having said that, normally, I would expect the whole Scrum Team to be present.
Your retro is a success if you commit to at least one improvement item in next sprint. Put it straight onto the task board at the top of the forecast. To use the woodcutter metaphor, sharpen then axe, then start chopping.
The Product Owner doesn’t get to say no to sharpening the axe.
Post the Retrospective in a Nutshell infographic on the wall as an information radiator and reminder how it’s supposed to be… and check it for more tips on a good retro.
Two things to remember:
- The retrospectives is to improve quality and effectiveness.
- Implement at least one item every sprint!