 |
 |
Well that is not true either. Scope is defined as part of the User Requirements Workshop.
Learned representatives of the organisation provide their assessment of the high level requirements to be delivered in the resultant solution. Whilst deriving these requirements in the workshop these personnel will have uncovered confusion and clarified misunderstanding surrounding the area of scope and features, thus defining it more accurately and concisely.
The workshop technique delivers a definition of scope and features that more closely match true business needs while eliminating what is often termed "feature frenzy" or "feature creep" and other wasted efforts to deliver functionality that the business simply does not demand.
|
 |
 |
|
 |
 |
|

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

SPADE: Successful Pragmatic Agile Delivery Everytime |
| Topic: 431 Page: 433/444 Progress: 97.5% |
 |  |
|

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