We just completed a CSM course and Agile Release Planning workshop in Charleston. Here are some of the impediments they identified. They are somewhat duplicative and they are not in any particular order. In my opinion, the list should also include automating the testing, better continuous integration, and better automated integration/regression testing. These were issues that were discussed later in the course.
- Untrained in Scrum
- Imposed deadlines
- Conflicting, competing priorities
- Software tools are down (Env. Issues)
- Waiting on Service Contract completion (3rd party)
- Lacking skills
- Scope creep
- Lack of dedicated people
- Not considering all that’s involved with project, like testing and deployment
- Unreasonable timelines
- Learning curve of AngularJS
- Micro-management
- Unplanned work gets added to sprint so you can never effectively plan
- Fragmentation
- Uninformed clients
- Technology stack
- Team & Organization new to Scrum
- Diverse data sets
- Failing to set client expectations
- Unfunded
- Misalignment of Work v. Strategy
- Poorly managed; no checkpoints, milestones
- Culture / language barriers
- Poor or lack of requirements
- Bad communication
- Not sticking to agreed time table
- Lack of technical knowledge
- Outside development
- Lack of knowledge in particular tech
- Lack of customer commitment
- Client knowledge (lack of?)
- Lack of infrastructure
- Less than 100% commitment from team
- Lack of budget
- Design conflict
- Unmet dependencies
- Changing requirements
- Unclear success criteria
- Dysfunctional development teams
- Unclear roles and responsibilities of Teams / Members
- Lack of project support
- Unrealistic expectations
No comments:
Post a Comment