The iterative nature of Scrum is a risk management mechanism that, even when poorly implemented, usually results in at least a 30% improvement in productivity. The rules of Scrum are simple and straightforward, and the underlying principles are intuitive. That is not to say, however, that Scrum is free of pitfalls. In this course, Scrum Pitfalls I, we discuss topics relating to User Stories not truly Ready and Done.
The Scrum Inc team covers:
- The role of the Product Owner not being well defined or under-resourced
- The importance of Product Backlog Refinement
- User Stories that are too big or not independent, vertical slices of functionality
- Teams over committing, or being committed, to too much work in a Sprint
- Team members working individually on the Sprint Backlog rather than together
- Found work Interrupting the Team during the Sprint
These are several typical missteps that keep both new and experienced Scrum teams from reaching their full potential. This course reviews the most common pitfalls we see our clients encounter. We will discuss ways to recognize and avoid these traps in advance.
Back to All Topics