 |
 |
We often hear that agile projects should be small, in both timeframe and team size.
It is only correct to say that small projects are easier to deliver, normally.
If a smaller project has a smaller timeframe then there is less time for things to go wrong.
If there are less people on a small project then there are less people to break things.
In our experience, it is not the size of the delivery it is the size of the shipment that should be smaller.
Small, regular shipments are fine in smaller projects as well as large agile projects.
|
 |
 |
|
 |
 |
|

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

SPADE: Successful Pragmatic Agile Delivery Everytime |
| Topic: 422 Page: 424/444 Progress: 95.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. |
 |