Below is a list of ‘failure modes’ for projects, as identified via the experience (in waterfall, whatever, agile or scrum) by the people in the Montreal July 2013 class. These are not in priority order. They might suggest certain impediments to add to the list for your team.
Lack of communication
Too many impediments
Not responsive to change
Scope creep
No (or different) work approach
Too much indirect communication
No budget
Bad (or lack of) leadership
Poor quality
Too much process
Toxic teammate
No access to client
Too much documentation
Too many meetings
No teamwork (individual work silos)
Change in requirements
No Org support
Unsatisfied customer (at the end)
No vision
Unclear requirements
Delivered late
Too little experience in Team
Lack of planning
Unrealistic timelines
No fun
Lack of consistency
Hidden agendas
Lone wolves
Switching team members
Micro-managing
Too many chiefs
Over-work
No Buy-in
Lack of communication
Too many impediments
Not responsive to change
Scope creep
No (or different) work approach
Too much indirect communication
No budget
Bad (or lack of) leadership
Poor quality
Too much process
Toxic teammate
No access to client
Too much documentation
Too many meetings
No teamwork (individual work silos)
Change in requirements
No Org support
Unsatisfied customer (at the end)
No vision
Unclear requirements
Delivered late
Too little experience in Team
Lack of planning
Unrealistic timelines
No fun
Lack of consistency
Hidden agendas
Lone wolves
Switching team members
Micro-managing
Too many chiefs
Over-work
No Buy-in
No comments:
Post a Comment