 |
|
This debate can go on forever.
Basically agile does have Requirements Gathering but it does it in a different way. Requirements are listed, prioritised and turned into user stories. The stories are worked on in sequence and requirement details emerge by a combination of demonstrations, assessments and collaboration with user teams.
All we can say is that in our waterfall days, we remember the big thick requirements document and how much of that was wasted effort by the time the project came to a close. The business may have stated a requirements document was correct but by the nature of changing demands it swiftly got out of date.
In this situation the projects often progressed on regardless, wasting resources on a solution that was not what was intended and was no longer able to deliver the originally proposed benefits.
|
|
|
|
|
|
|
|
|
|
|
|
Glossary: »
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
|
|
|
|
|
|
|
|
|
|
| | |
| | |
|
 
 SPADE: Successful Pragmatic Agile Delivery Everytime™ |
| Topic: 428 Page: 430/444 Progress: 96.8% |
 | |
|
|
|
|
|
|
|
|
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. |
|
