Agile Methodology

Paul Mohrbacher

Agile Manifesto

We are uncovering better ways of developingsoftware by doing it and helping others do it.Through this work we have come to value:

Individuals and interactions over processes and toolsWorking software over comprehensive documentation

Customer collaboration over contract negotiationResponding to change over following a plan

That is, while there is value in the items onthe right, we value the items on the left more.

Agile Principles

Changing requirements are welcomed Deliver working software in short time cycle Motivated individuals who can be trusted Face to face communication Constant review and enhancement of team Keep design simple Technical excellence and design

Agile Practices

Collective Ownership Test Driven Continuous Integration Coding Standards Pair Programming

Agile Suitability

Small to medium projects (< 20-40 people) Fewer but more competent people Communication friendly environment Developers make important decisions (trust)

Agile Cost Benefit

Agile Methodologies

Scrum (1986) Extreme Programming (XP 1996) Feature-Driven Development (FDD 1997) Adaptive Software Development (ASD)

Agile Problems

Large scale projects Q&A for changing requirements How to bill/contract

Agile Links

http://www.agilemanifesto.org/ Wiki on Agile http://www.agilealliance.org/ Agile overview Skeptics view

Questions?