Agile Development

1
 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.” Kent Beck et al 2
 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

Yielding …

• Rapid, incremental delivery of software

3
 Agility and the Cost of Change
The conventional wisdom in
software development
(supported by decades of
experience) is that the cost of
change increases nonlinearly
as a project progresses

Proponents of agility argue

that a well-designed agile
process “flattens” the cost of
change curve, allowing a
software team to
accommodate changes late in a
software project without
dramatic cost and time impact.
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
 Agility Principles - I
Any agile software process is characterized in a manner that addresses a number of key assumptions about the
majority of software projects:
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. Agile processes harness change for the
customer's competitive advantage.

3. Deliver working software frequently, from a couple of weeks to a 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.

6. The most efficient and effective method of conveying information to and within a development team
6
is face–to–face conversation.
 Agility Principles - II
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 – the art of maximizing the amount of work not done – is essential.

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, then tunes and
adjusts its behavior accordingly.

7
 Human Factors
• The process molds to the needs of the people and team, not the other way around
• Key traits must exist among the people on an agile team and the team itself:
• Competence.
• Common focus.
• Collaboration.
• Decision-making ability.
• Fuzzy problem-solving ability.
• Mutual trust and respect.
• Self-organization.

8
 Extreme Programming (XP)

• The most widely used agile process, originally proposed by Kent Beck
• More recently, a variant of XP, called Industrial XP (IXP) has been proposed
[Ker05]

• XP Values
• Beck defines a set of five values that establish a foundation for all work per-
formed as part of XP—communication, simplicity, feedback, courage, and respect.
• Each of these values is used as a driver for specific XP activities, actions, and tasks.

9
 Extreme Programming (XP) Extreme Programming process

Extreme Programming uses an

object-oriented approach as its
preferred development paradigm
and encompasses a set of rules
and practices that occur within
the context of four framework
activities: planning, design,
coding, and testing.

10
 Extreme Programming (XP)

• 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
• After the first increment “project velocity” is used to help define
subsequent delivery dates for other increments

11
 Extreme Programming (XP)
• XP Design
• Follows the KIS principle
• Encourage the use of CRC cards (see Chapter 8)
• 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 store before coding commences
• Encourages “pair programming”
• XP Testing
• All unit tests are executed daily
• “Acceptance tests” are defined by the customer and excuted to assess customer visible
functionality 12
 Industrial XP
Joshua Kerievsky describes Industrial Extreme Programming (IXP) as:

“IXP is an organic evolution of XP. It is imbued with XP’s minimal- ist, customer-
centric, test-driven spirit. IXP differs most from the original XP in its greater
inclusion of management, its expanded role for customers, and its upgraded
technical practices.”

IXP incorporates six new practices that are designed to help ensure that an XP
project works successfully for significant projects within a large organization.
13
 Industrial XP
The most widely used of all agile process models is extreme programming (XP). But
many other agile process models have been proposed and are in use across the
industry. Among the most common are:
• Adaptive Software Development (ASD)
• Scrum
• Dynamic Systems Development Method (DSDM)
• Crystal
• Feature Drive Development (FDD)
• Lean Software Development (LSD)
• Agile Modeling (AM)
• Agile Unified Process (AUP)

All agile process models conform (to a greater or lesser degree) to the manifesto
14
for agile software development and the prin- ciples said earlier
 Adaptive Software Development
• Adaptive Software Development (ASD) proposed by Jim Highsmith as a technique for building
complex software and systems. The philosophical underpinnings of ASD focus on human
collaboration and team self-organization.

• ASD — distinguishing features

• Mission-driven planning

• Component-based focus

• Uses “time-boxing”

• Explicit consideration of risks

• Emphasizes collaboration for requirements gathering

• Emphasizes “learning” throughout the process 15

Scrum(the name is derived from an activity that occurs during a rugby match)

• Scrum principles are consistent with the agile manifesto and are
used to guide development activities within a process that
incorporates the following framework activities: requirements,
analysis, design, evolution, and delivery.

• Within each framework activity, work tasks occur within a process

pattern (discussed in the following paragraph) called a sprint.

16
 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

17
18
 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 baselined at a high level
• Testing is integrated throughout the life-cycle. 19
•(DSDM) is an agile software development
approach that “provides a framework
for building and maintaining systems
which meet tight time constraints
through the use of incremental
prototyping in a controlled project
environment”.

•The DSDM philosophy is borrowed from

a modified version of the Pareto
principle—80 percent of an application
can be delivered in 20 percent of the
time it would take to deliver the
complete (100 percent) application.

•DSDM is an iterative software process in

which each iteration follows the 80
percent rule. DSDM Life Cycle (with permission of the DSDM consortium) 20
 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 21
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 22

Feature Driven Development

Reprinted with permission of Peter Coad

23
 Lean Software Development (LSD)
• Lean Software Development (LSD) has adapted the principles of lean
manufacturing to the world of software engineering.
• The lean principles that inspire the LSD process can be summarized as eliminate
waste, build quality in, create knowledge, defer commitment, deliver fast, respect
people, and optimize the whole.
• Each of these principles can be adapted to the software process. For example,
eliminate waste within the context of an agile software project can be interpreted
to mean
(1) adding no extraneous features or functions,
(2) assessing the cost and schedule impact of any newly requested requirement,
(3) removing any superfluous process steps,
(4) establishing mechanisms to improve the way team members find information,
(5) ensuring the testing finds as many errors as possible,
(6) reducing the time required to request and get a decision that affects the software or the process that is
applied to create it, and
(7) streamlining the manner in which information is transmitted to all stakeholders involved in the process.
24
 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
25
 Agile Unified Process (AUP)
• The Agile Unified Process (AUP) adopts a “serial in the large” and
“iterative in the small” philosophy for building computer-based
systems. By adopting the classic UP phased activities—inception,
elaboration, construction, and transition—AUP provides a serial overlay
(i.e., a linear sequence of software engineering activities) that enables a
team to visualize the overall process flow for a software project.
• Each AUP iteration addresses the following activities :
• Modeling.
• Implementation.
• Testing.
• Deployment.
• Configuration and project management.
• Environment management. 26
Thanks…

27