Impediments – Raleigh-Durham Feb 2014
February 28, 2014
I really want to advocate again that we must make the impediments visible in a public impediment list. And never stop aggressively attacking them. If you prefer to call it ‘our list of things to improve on,’ I won’t arrest you.
Here’s the list the group made in this class. They are not on order, they are not framed the same way, there will probably be some redundancies. These are in random order.
- Team commitment to Scrum
- Singular voice from PO
- Team commitment to project
- Unqualified Team members
- Quality agile process training (Gee, I hope they were not talking about me? (smile))
- (lack of) collocation
- Finalizing sprint work / goals
- Communication / collaboration
- Definition of Done / of Ready
- Replacing communication with documents
- Non-value process for process’ sake
- Unclear requirements
- Unrealistic or undefined scope
- Clear definition of done (lack of)
- Misunderstood requirements
- Well defined sprint – days
- Lack of team commitment
- No vision or backlog of work
- Unrealistic expectations
- No support of team
- Clear goal each sprint (lack of)
- No unified team or stakeholders
- (No) realistic expectations
- Lack of senior leadership commitment
- Actual list of impediments
- Overall goal / delivery
- Scope creep
- No idea of what ‘done’ means
- Self goals over project / team goals
- Poor leadership
- Resource constraints
- No single voice (I think it was of requirements to team, eg, PO was not really there)
- Expanded teams skills (need training)
- No shared vision
« « Question: More on Agile Contracts || Public Impediment List – Charleston Mar 2014 » »