As a brand new just getting started SCRUM convert, I feel good to
provide some input to the group on a new term to describe what we
recognize as traditional Scope Creep. We have adopted the
term "Progressive Elaboration" as the politically correct term that
has smoothed the feathers of our Product Managers.
Primavera Systems, Inc
--- In email@example.com
, "Mary Poppendieck"
> During the discussion of burn-up charts, now renamed build-up
charts, I have
> encountered several people talking about 'scope creep'.
> Personally, I do not believe in scope creep, and when viewed from
> of a customer, 'scope creep' can come across as a condescending
> find it difficult to use the word 'scope creep' in front of a
customer in a
> way which does not sound pejorative.
> Customers have needs that they understand with more or less
> have a budget and a timeframe in which they wish to get those needs
> satisfied. In the process of satisfying those needs, the details
> clarified and things change. Thus the original understanding of
> to be done changes. This is a normal, natural pattern in software
> development, but when it is labeled 'scope creep' it is thought of
> Software development is a series of try-it-test-it-fix it cycles
> as much of the system as possible. These cycles improve
> what it takes to achieve the business mission or objective. As
> understanding improves, it is useful to add ideas to the list of
> be done. There is nothing wrong with a long backlog list - it
> together everyone's good ideas.
> The game to be played is to have a clear understanding that not
> on the backlog is expected to be completed, and where the line is
> depends on when we run out of time and other resources. The
> creep' focuses people on the length of the list, which is
> instead of the necessity of drawing the line part way down the
> matter how long it is. It is a waste of time to worry about
> list, what we need to worry about is how to stop working when the
> justification and or time for the work is used up. Any method
> people to draw this line is useful. But it is not useful to focus
> movement of items above and below the line as learning increases.
> Perhaps we might worry about 'mission creep', but it would seem to
> with Scrum there is no such thing as scope creep, because there is
> attempt to fix scope to begin with, so there is nothing for scope
> away from.
> Mary Poppendieck
> www.poppendieck.com <http://www.poppendieck.com/>
> Author of
> Software Development: An Agile Toolkit