Public Impediments – Charlotte March 2014
We are a strong advocate of a public impediment list. Why? There are many reasons, but my top 3 are:
- Team members know when to tell and when not to tell the ScrumMaster about a new impediment
- Assuming some attempt at prioritization has been made, the Team knows when to give the SM feedback about the priorities (‘mine is more important’ is the simple version…).
- Everyone knows what the SM is working on now or next.
Of course, the real reason is to enable the best improvements to be made sooner. But that is too obvious.
The group came up with the following impediments.
- People issues
- Distractions (multitasking)
- Lack of resources
- Arbitrary long time estimates
- Lack of feedback
- Black box projects
- Management constraints
- Team too big or too small
- No clear roles
- No funding
- Unrealistic expectations, time or $
- Team improperly formed
- Too many impediments (main cause of failure)
- Inexperience (wrong skills)
- Poor listening
- (lack of) localization support
- No direction
- Stubborn people not aligned with Team
- Budgeting not clear
- Shareholders having diverse interests
- Lack leadership
- Teams not talking to associated teams
- Lack of resources dedicated to Team
- People turnover
- Performance not measured – no data
- Real product owner is not identified
- No clear process / product owner
- Cross-purposed stakeholders
- Lack of stakeholder buy-in / support
- Upstream / downstream dependencies
We hope this list helps your team get more creative about the impediments.