Team member: How will we know when we've found an impediment? What do they look like?
Sponsor: How can I know what impediments block our teams' productivity?
Scrum Master: How can I get the team to mention impediments in our daily meeting and retrospectives?
Product Owner: Why is everyone whining about impediments? Why don't we just get the work done?
It's all fine and well to say identify and remove impediments but often we bump up against a stumbling block, find a way around, and make things work anyway without further thought. It's second nature. Moving forward is what's important. And,...
Sometimes teams get stuck at the point of “deciding what to do” in retrospectives. Team members may begin to point fingers and describe things that the ubiquitous “they” must do before the team can move forward or make improvements,. This may lead to a team-as-victim, “poor us, we’re stuck” syndrome, or blame and finger-pointing. “It’s their fault we’re in this mess!” Blame kills retrospectives and the perception of persecution stalls any hope of forward motion, so the retrospective leader has to shift this conversation, and fast! Team members also may perceive so much room for improvement they become paralyzed and can’t decide where to start improving their lot.
When victim-talk, blaming or overwhelm surfaces, I reach into my retrospective leaders toolbox and pull out a technique to help teams identify the kinds of action the team can take.