Post on 18-Dec-2014
description
© 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
3© ThoughtWorks, 2006
Traditional Process
50 % done
?
4© ThoughtWorks, 2006
Better way of doing the same
End-to-End small slices of work 20 % done = 100 %
usable
5© ThoughtWorks, 2006
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.”
6© ThoughtWorks, 2006
Just the right amount of documentation
7© ThoughtWorks, 2006
Collective Ownership
No bottlenecksTeam responsibilityImproves code and processReduced risk of staff absence
8© ThoughtWorks, 2006
Collaboration
IT and Business working together
9© ThoughtWorks, 2006
Pairing
Developer (Driver)
Developer (Co-Driver)
Business
Analyst
10© ThoughtWorks, 2006
Continuous Integration
Integrate early, integrate oftenAutomated buildsCulture of accountability
11© ThoughtWorks, 2006
Frequent Short Releases
Prioritized features
Adds business value early
Showcases for feedback
12© ThoughtWorks, 2006
CollocationCollocation
Everyone in the same area to Improve communication
13© ThoughtWorks, 2006
“Yesterday, I …”
“Problems …”
“Today, I ...”
Daily Stand-Ups
© ThoughtWorks, 2007
Story Wall shows the project health
15© ThoughtWorks, 2006
Project objective
16© ThoughtWorks, 2006
Simplest thing that adds business value
17© ThoughtWorks, 2006
Incrementally adding business value
18© ThoughtWorks, 2006
Successfully accommodating changed requirements
19© ThoughtWorks, 2006
Result of iterative and incremental development
Original objective
20© ThoughtWorks, 2006
Questions?