Impediments – Charlotte – Oct 2014

This the list that this class identified:

1. Indecisive
2. Little stakeholder engagement
3. Started development late
4. LOB changed strategic direction
5. Assumptions
6. Lack of Test Environment & Data
7. Undefined risk
8. Lack of communication
9. Missing requirements
10. Too many bugs
11. No DOD
12. Time constraints (this is not yet a actionable impediments…but an issue for analysis IMO)
13. Backing into dates
14. Unreasonable deadlines
15. Poor leadership
16. Politics
17. Loss of team members
18. Opaque decision-making
19. No standards and practices
20. Third parties
21. No team – everyone for themselves
22. Change
23. Scope creep
24. No mitigation strategy
25. Poorly defined success criteria
26. Bad or no acceptance criteria
27. No business face time
28. Uncooperative team members
29. Laziness*
30. Lack of clear communication
31. Poor documentation
32. Difference in down time
33. Additional server & DBAs (lack of)
34. Product delivered on time with fewer defects (lack of)
35. Cloning test envronment
36. Team location distributed
37. New requirements
38. Bad requirements (or changing, in the waterfall model)
39. Requirements never done
40. Poor grooming
41. No plan
42. Changing needs
43. Not tested properly
44. QA too little too late
45. Poor testing/QA
46. Disengaged product owner
47. Bad attitude
48. Competing priorities
49. Loss of funding
50. Epics as stories
51. Change priorities
52. Poor quality
53. Not focused team members
54. Organizational dysfunction
55. Bad coding practices
56. Lack of full participation
57. Incompetent people
58. Single points of failure
59. Technical solution determined by Business was not achievable by Technology
60. Shifting business priorities
61. Decentralized execution teams working in silos
62. Needed expertise not available
63. Budget
64. Not enough time (again, an issue but not clearly an impediment itself…needs further analysis IMO)
65. Non-team players
66. Mis-managed timelines
67. Budget overruns
68. Poor grasp of requirements
69. Multiple priorities
70. Complete requirements (lack of)

See earlier lists for further discussion.

 

« « 3 Ways a Scrum Team is Managed || Why are we doing Agile? » »