The document discusses the heart of Agile and emphasizes that individuals and interactions are more valued than processes and tools. It provides examples of situations where valuing individuals and interactions over rigid processes and contracts led to better outcomes. Building an effective Agile team requires collective code ownership, commitment to the team over any individual, and letting go of ego to value collaboration over individual accomplishments.

1. Kulawat Wongsaroj [email_address] @kluak110 Bangkok Barcamp 3 May 23 2009 The Heart of Agile

3. In early 2001, a group of industry experts in light-weight process like XP, Scrum, FDD, Crystal, DSDM, and etc, formed the Agile Alliance and created The Manifesto of the Agile Alliance . We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. agilemanifesto.org

5. Have flexible Release Plan but freeze Iteration Plan before it starts 1 3 5 1 1 3 1 2 2 1 5 5 Iteration 1 Iteration 2 Iteration 3 Velocity=10 Velocity=10 Velocity=10 HIGH PRIORITY LOW PRIORITY Release 2 3 New & High Priority I really need these 2 new reports Freeze! Freeze!

9. So what do we need to build an agile team ? Ownership Commitment Team Collective Code Ownership Planning Pokers with Whole Team (Rotating) Pair Programming Simplicity Daily Stand-Up Meeting Retrospective Continuous Integration Test Driven Development Refactor Coding Standard

11. Team vs Superstars Team = Ant Army Superstar = Egomaniac

13. If you are going to read one Agile book Special thanks my Agile evangelists @ proteusguy @korn4d