You're facilitating a retrospective. You're creating action items to ensure the team walks away with tasks to help us improve. But a simple question reveals there are different interpretations to the same discussion and action item. Sound familiar?
There are several quotes that have stuck with me about agile retrospectives. These range from the importance of retrospectives as the real catalyst for continuous improvement in scrum to the fact that people struggle with holding effective retrospectives so much that the decision is often made to no longer have retrospectives. And the challenges teams face in retrospectives are just as varied.
Ever finish a meeting and ask yourself, "So what did we accomplish in that meeting, anyway?"
To be vulnerable is to expose yourself. In other words, increasing your vulnerability makes you more susceptible to being hurt.
It's such a common problem. Your team simply refuses to take the time to run retrospectives. "We're too busy!" they say. What should you do?
The first 30 seconds. Such a small amount of time, yet so critical to the success of your retrospectives.
It's a question I get all the time. Should the Product Owner take part in your retrospectives?
If you're running retrospectives and your team just doesn't care, whatever you do, don't skip the retrospective!
Have you ever tried to make a complicated meal without a recipe? If you’re not culinarily inclined, it can be risky. Recipes can be an amateur cook’s best friend because they’re tested and proven.