I am a strong supporter of identifying small things that we can take action on, one at a time, to get better. In Scrum, we call this an impediment list. This week, the class identified these impediments. I think I have it right....
- Lack of governance
- 0% transparency
- Actively disengaged team members
- Competing goals
- Adversarial sponsors
- Poorly understood technology
- Losing people mid-project
- Too many cooks
- No change management
- No requirements
- Individual contributions [not team contributions]
- Finger-pointing
- Lack of support
- Ill-defined teams / structure
- Lack of team collaboration (incl vendor-client)
- Unrealistic estimates
- Exit criteria [lack of??]
- Too high expectations
- Insufficient funding
- Silos
- Changing scope without adjusting (R or T or B).
- Poor communication
- Lack of Buy-in
- Absences from meetings
- People availability
- Poor estimates of time
- Poorly defined tasks
- No direction
- No / lack of leadership
- No understanding of benefits
- Personal agendas
- Command and conquer
- Constant distractions
- Unrealistic expectations
- Business ownership / partnership
- Lack of communication
- Lack of buy0in / ownership
- Disengaged team
- Unrealistic value
- Skillsets
- Lack of coordination
- Hidden assumptions
- Complete assumptions
- Just get 'it' done - don't know what
- Unhealthy communication
- Confusion
- Lack of involvement from customer
- Unclear purpose
- Poor definition
- Poor team dynamics
- Single points of failure
There is some duplication, I think, for many reasons. But perhaps useful in suggesting relative priorities.
A couple of key points:
- We have a list to prioritize and act on the most useful stuff first
- Prioritize mainly by 'how much is it slowing down the team'
- Use cost-benefit analysis to some degree (maybe only intuitive)
- Drive one to completion at a time
- Make them small. No bigger than one sprint.
- Get the managers to help you (and the Team as well)
- Show results
No comments:
Post a Comment