Agile Project Management

Agile Project Management Marco Jansen (marco@thoughtworks.com) Kedar Kulkarni ( kedar@thoughtworks.com)

The Agile Contract

Customer

What should be delivered

Priority: What is the most important functionality to deliver first.

Development Team

How will it be delivered

Estimates: How long will it take to deliver.

Agile Manifesto (2001)

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 interaction 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 .

Principal #1: Individuals and interaction over processes and tools

Principal #2: Working Software over Comprehensive Documentation Requirements Gathering Use Cases / Scenarios Functional Specs Design Specs Code Integrate Test Fix User Stories / Project Plan Iteration 1 Iteration 2 Iteration 3 Iteration 4 Design / Code / Test Stories for Next Iteration

Principal #3: Customer collaboration over contract negotiation

Principal #4: Responding to change over following a plan

Total Transparency At any time the status of the project is visible for everybody

Build trust by having Total Transparency At any time the status of the project is visible for everybody

Total Transparency At any time the status of the project is visible for everybody

Agile Practices ORGANIZATIONAL Automated Build/Deploy Automated Testing Short Releases Coding Standards Continuous Integration On-site Customer Co-location Collective Ownership TEAM Retrospectives Iterations Iteration KO User Stories Velocity Metrics Story Wall Pair Programming Sustainable Pace Daily Stand-ups INDIVIDUAL Refactoring Simple Design Test Driven Development

Some great Agile reading