Scope Creep - the unintentional growth of the scope of a project - is a major concern in traditional, phased projects. How do you avoid scope creep in Scrum? Does the Scrum framework offer any tools or practices to avoid this destructive force? The answer is not as straight forward as you might think and may surprise you!
In this Responsive Advisors Lightning Round, we discuss how to deal with scope creep on a Scrum team.
I'd look at differently than scope-creep doesn't exist in Scrum. Scrum doesn't necessitate there is predefined scope, but I believe there can be e.g project requirements or product roadmap, perhaps defined at a higher level and the Scrum team works to deliver on this, so maybe they don't concern themselves with the larger scope to maintain agility, but it may still be there in some form. Also beyond the overall project or product roadmap scope, each sprint has its own scope when initiated. Pulling tasks in from the back-log mid-sprint is scope-creep for the individual sprint, but maybe not scope-creep overall.
