Agile Methodologies

Dhaval Dalal
software-artisan.com

dhaval.dalal@software-artisan.com

Feedback

Product Knowledge

Software
Requirement
Specs
Product Development

Analysis Develop/UT QA


Rapid Feedback

Small Product Knowledge
Batch

S/W
Req.
Specs
as
a
“Big Product Development
Batch”


Waterfall Model Iterative &
Evolutionary Models
Software dev is predictable Software dev is changeable

Big up-front specs Evolutionary specs

Upfront perfection Continuous Improvement

Predictive planning Adaptive planning

Batch Manufacturing Flow of Value


 Extreme Programming (XP)

 Scrum

 Crystal

 DSDM (Dynamic System Development Method)

 Lean

 ...and many more


Individuals and interactions over processes and tools

Working software over comprehensive Documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

While there is value in the items on the right,
We value the items on the left more.
Kent Beck, Mike Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler,
James Grenning, Jim Highsmith, Ron Jeffries, Jon Kern, Brian Marick, Robert C. Martin, Steve
Mellor, Ken Schwaber, Jeff Sutherland, Dave Thomas, Andrew Hunt


 Primary measure of progress is Working
Software.
 Deliver frequently.
 Satisfy customer by adding business value.

 Customer Collaboration and Visibility
 On-site Customer.
 Show Progress Charts publicly.

 Constant Communication.
 No substitute for a face-to-face conversation.


 Documents can be created, but don’t capture all
project information in writing.

 Documentation complements Code and Speech
 Document shouldn’t try to do what the code already
does well.
 Vital detail about design is captured in the code.

 It takes fastidiousness to write code that
doesn’t just do the right thing, but also says
the right thing.
Source: Eric Evans, Domain Driven Design


 Eliminate Waste
 Design
 Defects
 Hand-over

 Embrace Change and Adaptive
Planning
We will plan by quickly making an overall plan, then reﬁning it further and
further on shorter and shorter time horizons – years, months, weeks, days. We
will make the plan quickly and cheaply, so there will be little inertia when we
must change it.

Kent Beck


 Technical Excellence
 Team-members commit to produce the
highest quality code they can.
 Continuous attention to good design
enhances agility.
 Sustainable Pace.
 Self-Organizing Teams.


 Developers make estimates
 Responsibilities are not handed to individual team members from
the outside.

 Responsibilities are communicated to the team as a
whole, and the team determines the best way to fulfill
them.

 Best architectures, requirements, and designs emerge
from self-organizing teams.

 No “Blame Game”
 Team members work together on all aspects of the project.
 No single team member is responsible for the architecture, or
the requirements, or the tests, etc.


Master
Story
List


Release #1
Story
List

Master Release #2
Story Story
List List

Typically 3
Months
Time boxed


Iteration #1
Release #1 Story List
Story
List Iteration #6
Story List

Iteration #1
Master Release #2 Story List
Story Story
List List

Typically 2
Weeks
Time boxed

Typically 3
Months
Time boxed


Iteration #1 Story #1
Release #1 Story List A story is a
Story #2
Story Story #3
smallest unit
List Iteration #6 of work
Story List

Iteration #1
Typically 1-2
Master Release #2 Story List Days
Story Story Time boxed
List List

Typically 2
Weeks
Time boxed

Typically 3
Months
Time boxed


Iteration #1 Story #1
Release #1 Story List A story is a
Story #2
Story Story #3
smallest unit
List Iteration #6 of work
Story List

Typically 1-2 Generates
Iteration #1 Unit Test
Master Release #2 Story List Days
Story Story Time boxed Cases.
List List
Sample Story Card
Typically 2 Story <No.>
Weeks As a <Role>,
Time boxed I’d like to do <Task>,
So that <Larger Goal>.
Typically 3
Establishes Given That <>
Months
Acceptance When <>
Time boxed
Criteria. Then <>

Acceptance
Criteria.


 Schedule High priority and low-
confidence stories first.

 A Story with low-confidence can be
“spiked”
 Similar to a POC.



Story Card
Story <No.>
As a <Role>,
I’d like to do <Task>,
Story Card
Story <No.>
As a <Role>,
So that <Larger Goal>. Story Card
Story <No.>
As a <Role>,

Iteration N+1 Iteration N Iteration N-1


 Short, high energy, effective, to the point meeting.

 To provide early and regular feedback on the team‘s
progress
 Achievements, Impediments, Problems Faced

 When?
 BOD
 Upcoming work is described
 Pairs Sign-up for stories
 EOD
 What were the problems faced and impediments raised.
 What needs to be done and what was achieved.


 Test-first approach (TDD)
 Evolve Code from Tests

 Refactoring
 Improves code, usually increasing the function while
reducing code bulk.

 Continuous Integration (CI)

 Pair Programming and Pairing.


 Green field project
 Unknown/Unstable Reqs., Unfamiliar territory.

 High or Low Risk.
 Time, Technology, complex biz. etc…

 High or Low Team Expertise.

 Short or Long project duration.


 http://www.agilemanifesto.org
 http://www.agilealliance.com/articles
 Agile Process
 Robert C. Martin, Object Mentor Inc.
 Extreme Programming Explained
 Kent Beck, Three Rivers Institute.
 http://www.martinfowler.com
 ASCI Conference, April 2005, Bangalore.
 Craig Larman’s Keynote, Valtech.
 Agile Overview, Managing Iterations.
 Naresh Jain, ThoughtWorks.
 Distributed Agile Development
 Bapiraju Nandury, Cúram Software.
 Agile User Group Meeting, Chennai.
 Sanjiv Augustine’s Keynote, CC Pace Inc.

Agile Methodologies

Recommended

Recommended

More Related Content

Similar to Agile Methodologies

Similar to Agile Methodologies (20)

More from Dhaval Dalal

More from Dhaval Dalal (20)

Recently uploaded

Recently uploaded (20)

Agile Methodologies