Recommended
More Related Content
Similar to Controlling scope creep in agile sprints
Similar to Controlling scope creep in agile sprints (20)
More from Martin Bailey
More from Martin Bailey (10)
Recently uploaded
Recently uploaded (20)
Controlling scope creep in agile sprints
- 1. Discussion and Prioritization is key Martin R. Bailey, PMP, ACP, CSM, ITIL
- 2. Task A 1 hr Task B 2 hrs Task C 8 hrs Task D 12 hrs Support & Overhead 10 hrs Task E 4 hrs This one week plan uses 37 out of 40 hours
- 3. Task A 1 hr Task B 2 hrs Task C 8 hrs Task D 12 hrs Support & Overhead 10 hrs Task E 4 hrs Even without committing to new scope – Analysis could take up the remaining 3 hours or cut into planned work. New Scope 20 hours
- 4. Task A 1 hr Task B 2 hrs Task C 8 hrs Task D 12 hrs Support & Overhead 10 hrs Task E 4 hrs New Scope 20 hours We can’t easily fit the new 20 hr Scope into the week What do we move out? Tasks C & D
- 5. Task A 1 hr Task B 2 hrs Support & Overhead 10 hrs Task E 4 hrs New Scope 20 hours Tasks C & D are moved to the Product Backlog To be part of prioritization discussion for the next Sprint.
- 6. Menlo Innovations demonstrates this concept using proportionately sized paper on a poster board in one of their videos. Customers and stakeholders are part of the discussion on how to “make room” for new scope. Visualization helps stakeholders understand tradeoffs and potential delays. The new scope might be eliminated or delayed as a result of frank discussion.