Introducing Agile

© ThoughtWorks, 2007

Introducing Agile

2© ThoughtWorks, 2006

Realities of software development

• Requirements will change

• Cost of change is high

• Plans don’t effectively accommodate change


Traditional Process

50 % done

?


Better way of doing the same

End-to-End small slices of work 20 % done = 100 %

usable


Agile Manifesto

“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.”


Just the right amount of documentation


Collective Ownership

No bottlenecksTeam responsibilityImproves code and processReduced risk of staff absence


Collaboration

IT and Business working together


Pairing

Developer (Driver)

Developer (Co-Driver)

Business

Analyst


Continuous Integration

Integrate early, integrate oftenAutomated buildsCulture of accountability


Frequent Short Releases

Prioritized features

Adds business value early

Showcases for feedback


CollocationCollocation

Everyone in the same area to Improve communication


“Yesterday, I …”

“Problems …”

“Today, I ...”

Daily Stand-Ups


Project objective


Simplest thing that adds business value


Incrementally adding business value


Successfully accommodating changed requirements


Result of iterative and incremental development

Original objective


Questions?

Introducing Agile

Technology

Transcript of Introducing Agile