Effective brainstorming is critical in a retrospective. It is the very first thing you do during your retrospectives and serves as the foundation for the discussions that follow. So it’s not unexpected that I’m regularly asked how to have more engaging and effective brainstorm sessions.
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?
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.
Introverts and extroverts. Both have valid insights to share, but in most retrospectives, extroverts dominate the conversation.
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?