 |
 |
Well let us see. Scope is defined in the User Requirements Workshop and agreed with the project sponsor.
So the project scope is correct and confirmed at the very start. Scope Creep is a derogatory term for uncontrolled adjustment to or change of scope.
However in an agile project we welcome change and fully recognise that a business team may wish to alter the aim of a project to deliver adjusted and new outcomes as the project emerges. Scope Creep is a derogatory term because, when it applies to waterfall projects, there is an assumption the project will deliver the new scope along with all the other scope it signed up to deliver too. On an agile project we do no such thing. With adjustment to scope in one area comes an equal and instant reduction of scope in another. With Scope Creep, we will also experience and confirm some Scope Seep.
|
 |
 |
|
 |
 |
|

|
 |
 |
 |
 |
Glossary: »
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
|
 |
 |
 |
 |
 |
 |
 |
 |
 |
| | |
| | |
|

SPADE: Successful Pragmatic Agile Delivery Everytime |
| Topic: 432 Page: 434/444 Progress: 97.7% |
 |  |
|

|
 |
|
 |
|
 |
 |
This content can be copied to third parties for personal use if you acknowledge the source of the material with website URL (http://www.bigagiletoolkit.com/) and Twitter hashtag (#BigAgileToolkit).
In all other cases, no part of bigagiletoolkit or associated text or website may be copied reproduced or redistributed in any form or by any means without prior permission in writing from the author.
Agile Project Governance for Cost Conscious Companies
All rights reserved. |
 |