Who is responsible for preventing scope creep?
The question assumes that scope creep is something to be managed and/or prevented.I saw this poll on LinkedIn:
Who is responsible for managing and preventing scope creep?
- Product Managers
- Developers
- Business stakeholders
- Scrum master/ project manager
Interesting question.
But it’s based on a flawed premise.
At least it is if we assume we’re aiming for something in line with the Manifesto for Agile Software Development. This seems to be an appropriate assumption, considering the inclusion of a Scrum master in the list, and the author’s agile-centric job title.
The question assumes that scope creep is something to be managed and/or prevented.
But remember that pesky phrase in the agile manifesto about responding to change over following a plan?
When the customer changes their mind about what’s important, that’s not scope creep, that’s just… normal!
We need to embrace that, if our goal is to achieve customer collaboration over contract negotiation, and deliver working software while valuing individuals and interactions.
