The Manifesto for

Agile Software Development

“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.”
1
 What is “Agility”?
• Effective (rapid and adaptive) response to change
• Effective communication among all stakeholders
• Drawing the customer onto the team
• Organizing a team so that it is in control of the work performed
• Rapid, incremental delivery of software

2
• The agile alliance defines 12 principles for those who want to
achieve agility :
1. Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software.
2. Welcome changing requirements even late in development
3. Deliver working software frequently, from couple of weeks to
couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily
throughout the project.
5. Build projects around motivated individuals. Give them the
environment and support they need and trust them to get the job
done.

3
6. The most effective and efficient method of conveying information
to and within a development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors,
developers and users should be able to maintain a constant pace
indefinitely.
9. Continuous attention to technical excellence and good design
enhances agility.
10. Simplicity
11.The best architectures , requirements and designs emerge from
self-organizing teams.
12.At regular intervals, the team reflects on how to become more
effective.
4
 An Agile Process
• Is driven by customer descriptions of what is
required (scenarios)
• Recognizes that plans are short-lived
• Develops software iteratively with a heavy
emphasis on construction activities
• Delivers multiple ‘software increments’
• Adapts as changes occur
5
 Extreme Programming (XP)
• The most widely used agile process, originally
proposed by Kent Beck
• XP Planning
– Begins with the creation of “user stories”
– Agile team assesses each story and assigns a cost
– Stories are grouped to for a deliverable increment
– A commitment is made on delivery date.

6
• The XP team orders for the stories that will be developed in one of
three ways :
1. All stories will be implemented immediately (within a few weeks)
2. The stories with highest value will be moved up in the schedule
and implemented first.
3. The riskiest stories will be moved up in the schedule and
implemented first.
 After the first release also called software increment has been
delivered , the XP team computes the Project Velocity.
Project Velocity is “the number of customer stories
implemented during the first release”.

7
• Project velocity can then be used to help :
1. Help estimate delivery dates and schedule for subsequent releases
2. Determine whether an over commitment has been made for all
stories across the entire development project.

8
 Extreme Programming (XP)
• XP Design
– Follows the KIS (Keep it simple) principle
– Encourage the use of CRC (class responsibility collaboration) cards .
– For difficult design problems, suggests the creation of “spike solutions”—a design
prototype
– Encourages “refactoring”—an iterative refinement of the internal program design
• XP Coding
– Recommends the construction of a unit test for a stories before coding commences
– Encourages “pair programming”
– Integration responsibiliity
– Smoke testing
• XP Testing
– All unit tests are executed daily
– “Acceptance tests” are defined by the customer and executed to assess customer
visible functionality

9
Extreme Programming (XP)

10
 Adaptive Software Development

• Originally proposed by Jim Highsmith

• ASD — distinguishing features
– Mission-driven planning
– Component-based focus
– Explicit consideration of risks
– Emphasizes collaboration for requirements
gathering
– Emphasizes “learning” throughout the process

11
• Collaboration :
People work together must have trust one another to
1. Criticize without animosity.
2. Assist without resentment.
3. Work as hard or harder as they do.
4. Have the skill set to contribute to the work at hand.
5. Communicate problems or concerns in a way that leads to effective
action.
Learning :
1. Focus groups
2. Formal technical reviews
3. Post mortems
12
Adaptive Software Development

13
 Dynamic Systems Development Method
• Promoted by the DSDM Consortium
• DSDM—distinguishing features
– Similar in most respects to XP and/or ASD
– Nine guiding principles
• Active user involvement is imperative.
• DSDM teams must be empowered to make decisions.
• The focus is on frequent delivery of products.
• Fitness for business purpose is the essential criterion for acceptance of
deliverables.
• Iterative and incremental development is necessary to converge on an
accurate business solution.
• All changes during development are reversible.
• Requirements are baseline at a high level
• Testing is integrated throughout the life-cycle.

14
• Feasibility study
• Business study
• Functional model iteration
• Design and build iteration
• Implementation

15
 Scrum
• Originally proposed by Schwaber and Beedle
• Scrum—distinguishing features
– Development work is partitioned into “packets”
– Testing and documentation are on-going as the
product is constructed
– Work occurs in “sprints” and is derived from a
“backlog” of existing requirements
– Meetings are very short and sometimes conducted
without chairs
– “demos” are delivered to the customer with the time-
box allocated

16
Scrum

17
 Crystal
• Proposed by Cockburn and Highsmith
• Crystal—distinguishing features
– Actually a family of process models that allow
“maneuverability” based on problem
characteristics
– Face-to-face communication is emphasized
– Suggests the use of “reflection workshops” to
review the work habits of the team
18
 Feature Driven Development
• Originally proposed by Peter Coad
• FDD—distinguishing features
– Emphasis is on defining “features”
• a feature “is a client-valued function that can be
implemented in two weeks or less.”
– Uses a feature template
• <action> the <result> <by | for | of | to> a(n)
<object>
– A features list is created and “plan by feature” is
conducted
– Design and construction merge in FDD
19
Feature Driven Development

20
 Agile Modeling
• Originally proposed by Scott Ambler
• Suggests a set of agile modeling principles
– Model with a purpose
– Use multiple models
– Travel light
– Content is more important than representation
– Know the models and the tools you use to
create them
– Adapt locally
21