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,...
In a article at the Six Sigma IQPC site, Christian Loyer offers a new twist on the old fishbone diagram root cause analysis approach.
Martin Jul writes about a retrospective activity in the post “Retrospectives - Adapting to Reality.” He describes an interesting process for highlighting issues in the Generating Insights part of a retrospective session.
I’ve used “Park Bench” at the end of workshops as a way of reflecting on the day or as a debriefing technique after a training exercise to uncover group discoveries. You may be surprised that I hadn’t thought of it for retrospectives. I was. Luckily, Michael thought of it.
Today I invented a phrase (at least I think I invented it because I haven't heard anyone else say it): "Avoidable Heroism."
I invented it in response to a question, "Should my team work on the weekend to meet a commitment made under their control?"
Now, I don't know the background behind this question. Maybe it's perfectly reasonable for them to work on the weekend. Maybe they have no agreement about sustainable pace. And, it raises a few questions in my mind. How often does this happen? How far from the commitment are they? When was the first, best opportunity to...