The document discusses why agile software development works better than traditional predictive methods. It argues that software development is a creative process that is difficult to plan and predict due to variability from factors like changing requirements, people's availability and performance. This variability can lead to queues and delays if not managed properly. Agile methods help manage this variability through techniques like limiting work in progress, reducing task size, and accepting changes in priorities. The document emphasizes that agile is more about adapting processes and putting people first rather than following practices rigidly.

1. Another look at why Agile works Be Agile rather than Do Agile Agile Tour 2009 in Chengdu

3. Difference between building a… And a Bridge… A Software…

7. Design effort for building a bridge is about 10% of the job Building a software for a large project , design is at least 50% of the work By Steve McConnell

12. A Stochastic System with Queues

13. As utilization goes up in a system with lots of variability, average cycle time gets worse

15. Analogy to Traditional Product Development with big batches

29. Hierarchies in Agile

30. Specialization in Agile