 |
 |
Again we were recently told Scope on an agile project is the same as scope on a waterfall project.
Well if you read the last few paragraphs this is obviously incorrect. The scope on waterfall projects is fixed it does not change.
If the scope is wrong on a waterfall project your project is in trouble. The project is aiming for the wrong target, it will deliver the wrong solution and the original business change is not going to be satisfied.
Therefore the benefits you proposed are unlikely to be right let alone realised and although the costs will probably be right, they are going to need to increase when the real scope and solution is uncovered and the project re-planned.
So I think we have nailed this one: the management of scope across the two project approaches is very different indeed.
|
 |
 |
|
 |
 |
|

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

SPADE: Successful Pragmatic Agile Delivery Everytime |
Topic: 430 Page: 432/444 Progress: 97.3% |
 |  |
|

|
 |
|
 |
|
 |
 |
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. |
 |