Impediment List: Toronto
We just completed a CSM course in Toronto.
Here are the impediments they identified, although some are phrased in a positive way. Eg, for some you need to add “…, lack of.”
This list, as with others here, supports the idea of a public impediment list. The real issue is ‘fixing impediments regularly and aggressively.” But we find that starts with a prioritized list of impediments. And we attack them one at a time. Single piece continuous flow, as the Lean guys propose.
Here’s their list (not in order):
- Small teams (<5) & timelines [I think the first notion is that the teams are too small now, and I think this person is right that Scrum will work better for them with a Team size closer to 7.]
- Making time to meet
- Changing requirements
- Task breakdown (poor)
- Being in the office at the same time (not now)
- Compressed timeline
- Admitting we need agile or a Proj Mgmt solution (we haven’t yet)
- Tight timelines
- Technical challenges
- Lack of people with diverse and required skills
- Waterfall/Agile hybrid
- Lack of people for given schedule
- Delays (outside the team that mean the team will ‘fail’)
- Lack of flexibility
- Poor communication
- Too much planning, not enough execution
- Old fashioned technology
- Lack of people
- Over budget
- Lack of proper planning
- Lack of approach
- Lack of customer feedback
- Incorrect requirements delivered
- Lack feedback
- Lack of detail in scope or requirements
- Lack skills
- Too ambitious feature list
- High level design
- Lack of collaboration between teams
- Poor scheduling
- Too complex
- Inadequate testing
- Lack of leadership
***
Find some your team can use?
Comments?
« « What is a Real Team? || Impediments – Charlotte » »
2 thoughts on “Impediment List: Toronto”
Leave a Reply
You must be logged in to post a comment.
Pingback: Frederick
There’s alot of wisdom hidden in that list. Thanks for sharing it in the open.