2 Agile Development

Syllabus
Agility and agile process model,
Extreme programming, Other process models ofagile developmert
and 1ools.

Contents
Model.. Summer-2018, 2019,
2.1 Agility and Agile Process
Winter-2018, . . Marks 4
. 7
2.2 Extreme Programming .. Winter-2019,
2.3 Other Process Models of Agile Development.. Summer-2016, 2018, -. - - Marks 7
... Witer-2017, 2018,
2.4 Tools for Agile Process
 Software Engineering 2-2
Agile Developme
2.1 Agility and Agile Process Model prnen
GTU: Summer-2018 2019,
In 1980's the heavy weight, plan based software development apDroat
Winter-2018,Malks
h was used
software product. In this many things are d
approach too
develop any
not directly related to software product being produced. This approach done wrich were
means if requirements get changed, then rework was essential. Henco
was rigid. Tha
were proposed in 1990's which are known as agile processes. new metho
The agile processes are the light-weight methods are people-based
plan-based methods. The agile process forces the development team torather than
software itself rather than design and documentation. The agile procese ocus on
iterative method. The aim of agile process is to deliver the working model o

quickly to the customer. sotwate

For example : Extreme programming is the best known of agile process.

Conventional Software Development Methodology

A s the software project makes the progress, the cost of the changes increases
non
linearly.
I t is easy to accommodate changes during the requirement gathering stage. At thi
scenarios are modified, list of funcio
stage to accommodate the changes usage
can be extended, or written specification
be edited.
As the progresses and if the customer suggest the changes during the testing

phase of the software development life cycle then to accommodate these changs
these changes wil
the architectural design needs to be modified and ultimately
affect other phases of software development cycle. These changes are actually

costly to execute.

Agile Methodology
The agile method proponents claim that if the software development is carried ou

the agile approach then it will allow the software team to accommocat
using
changes late in a software project without dramatic cost and time impact
Such
I n other words, if the incremental delivery is combined with agile pracices
as continuous unit testing and pair programming then the cost of changes

controlled. has a

The following graph represents the how the software development approa
strong influence on the development cost due to changes suggested.

TECHNICAL PUBLICATIONSs - An up thrust for knowledge

Software Engineening 2-3 Agile Development

|Cost of changes
due to conventional
software process

Cost of changes
due to agile process

Time
Fig. 2.1.1 Influence of software development approach on agile process

2.1.1 Agility Principles

There are famous 12 principles used as agility principles

1. Satisfy the customer by early and continuous delivery of valuable software.

2. The changes in the requirements must be accommodated. Even though the changes
occur late in the software development process, the agile process should help to
accommodate them.

quite often. Within the shorter time span deliver the

3. Deliver working software
working unit.
the project.
4. Business people and developers must work together throughput
and
the projects. Provide the environment
5. Motivate the people who are building
to be done.
trust them for the job
support to the development team and
measure of the progress of the software
6. The working software is the primary
development.
the constant project
7. The agile software development approach promote must be
The constant speed for the development
of the product
development.
maintained.
continuous technical excellence
8. To enhance the agility there should be
be given to technical
excellence and good design.
9. The proper attention to this
maintained while developing the project using
10. The simplicity must be

approach. best architecture,

team for getting
11. The teams must be the self-organizing
requirements and design.

TECHNICAL PUBLICATIONS An up thrust for krnowledge

 2-4
Software Engineering Aglle
nvolopma
intervals the team thinks over
the issue of becoming effective
12. At regular
their behavior accordingly.
After the
careful review the team members adjusts

2.1.2 Concept of Agile Process

about software projects
Agile process is based on following assumptions
requirements in advance. Similarly the
predict
is difficult to the software
1.It
customer priority often get changed.
before the implementation
2. It is difficult to predict how much design is necessary
activities such as analysis,
design, construction anid and

3. All the software development

are just difficult to predict.
testing
Characteristics of are
Agile process
and environmental changes. Tha
processes must be adaptable to technical
1. Agile occur, then the agile process must
must
means if any technological changes
accommodate it.
in each
in each
be incremental. That
means,
2. The development of agile processes must that can be tested
should contain some functionality
development the increment
and verified by customer.
be used to create the next increment of the process.
3. The customer feedback must

increment must be
delivered in short span of time.
4. The software
increment can be evaluated regularly.
that each
5. It must be iterative, so

Review Questions
used in agility software development.
1. Discuss agility principles
2. Discuss the concept of agility.
GTU: Summer-2018, 2019, Marks 4
and explain any one with suitable examvle.
different agile process model
3. List the
GTU Winter-2018, Marks 4

2 . 2 Extreme Programming GTU: Winter-2019, Marks 7

is one or tne DEt OWn
agile process. It is
Evtreme Programming (XP) suggested hy

2000.
Kent Beck in

2 . 2 . 1 XP Values

values serve as
that
lsuos that serve as aa basis far
toOr the
the set of five work
Beck defined performed in
XP. These
values are -

UUCAL PUALICATIONS. Ar
Software Engineerning 2-6 Agile Devlopnent

1 Communication : The effective communication must be established between

software developers and stakeholders in order to convey the important concepts
and to get the important feedback.
2. Simplicity: XP focuses on the current needs instead of futures needs to
incorporate in the design. Hence the XP believes that the Software design should
be simple.
3.Feedback: The feedback for the software product can be obtained from the
developers of the software, customers, and other software team members.
adherence to certain XP practices require courage. The agile XP
4. Courage : The strict
to design the system today, recognize the future
team must be disciplined
the demand.
requirements and make the changes dramatically per
as

the above states XP values the agile team can win the
5.Respect: By following
respect of stakeholders.

2.2.2 Process

The extreme programming process is explained as follows -

Customer becomes one
Customer specifies priorities the system requirements.
and
and customer
members of development team. The developer
of the important
needs are mentioned.
story-card in which customer
together prepare a

scenarios in the story-card.

then aims to implement the
The developer team
work
team breaks down the total
After developing the story-card
the development
these tasks are
required for
efforts and the estimated
resources
in small tasks. The
estimated.
implementation. If the requirement
changes
stories for
.The customer priorities the discarded. Then release
the
stories have to be
then sometimes unimplemented
software in small and frequent releases.
complete developed.
F o r accommodating
new changes, new story-card must be
with the customer.
Evaluate, the system along 2.2.1.
This process is
demonstrated by the following Fig.
Design
Planning

Refactoring9

Coding
Testing

Release or
increment
XP process
Fig. 2.21

PUBLICATIONS
An up thrust for knowledge
TECHNICAL
 Software Engineering 2-6
Agile
Various rules and practices used in extreme programming are as given
en below -
Developmen
XP Principle Descrlption
User story-cards Instead of creating a
large requirement docum.
stories are written by the customer in
need is mentioned.
which .User
us sursstts** **********************************
***************************
************** .. thev
Release planning A release plan for overall project is
the iteration plan can be prepared
prepared fromm which
iteration.
for individ
******** **
************** ****************
* * * * * *****
.

Planning Small releases The developer breaks down the user stories inta
to
releases and a plan for releasing the small
is prepared. functionaliSmall
Iterative process Divide the development work into small iterations
the iteration of nearly constant
length. Keep
Iterative
development helps in quick agile development.
wwww
or
www

wwwwwwwww.wwwwwwm
Stand up meetings The stand up meetings must be conducted for the
outcomes of the project. Current
****

*******::******* *******************************
****************************sn
********

Simple design Simple design always takes less time than the
compler
design. It is always good to keep the things simple to
meet the current requirements.
wwww ww*. *
wwwwawwwwmwww
www. w ws

Spike solution F answering the tough technical problems create the

Designing spike solutions. The goal of these solutions should be to
reduce the technical risks.
***************** ********************** ****
*********

Refactoring Refactoring means

redundancy, reductions in the
elimination of unused functionalities, redesignt
obsolete designs. This will improve the
project.
quality of the
***************************************
****u*noaomane
****************************************** ** * ******at

Customer The most essential

requirement of the XP is availability
availability of the customer. In Extreme
programming the customer
not only helps the developer team but it should be the
part of the project.
******************************************
*****************

Paired All the code to be

Coding included in the project must be code
programming by groups of two people working at the same compu
Ihis will increase the
*****
************************************ sma quality of coding
*************************************t*****i***ra****.************************

Collective code By having collective the

ownership app code Pproach

ownership everyone contributes new ideas and not any single can

person becomes the bottleneck of the project. Anyone

change any line of code to fix a bug or to refactor.
Sofwee Enginesng 2.7 hgie evelnerd

Unit testing The test-first devekopment is done in XP. The test

framework that contaíns the automated test case suite is
used to test the code. All the code must be tested using
unit testing before its release.

Continuous As soon as one task is finished integate it into the whole

Testing integration systern. Again after such integration unit testirg must be
Conducted
No overtime Working overtime lose the spirit and motivation of the
team Conduct the release planning meeting to change
the project scope or to reschedule the project.

As mentioned earlier in Extreme Programming instead of creating large requirement

is prepared. For example If a project is for creating a
douments the user story-card
software then the sample story card can be prepared as follows
banking
1. Customer makes the balance enquiry.

withdraws some amount.

2 Customer
some amount.
3. Customer deposits
Banking software checking balance, depositing and withdrawing

When the check the balance then he just enters his

customer wants to
in his account is
account number and the total amount present
displayed to him.
account. The limit
Then customer can withdraw some amount from his
If the customer crosses
of amount to be withdrawn must be specified.
amount withdrawn must be
that limit then he must be warned. The
deducted from the available balance.
in his account. The
The customer can deposit the desired amount
amount must be added to the available
balance.
deposited

various tasks and simple classes must be

Note that, the user story is broken into
clear that the useful class in the project
created for these tasks. From above example it is
customer name, address,
could be 'account'. Various data attributes can be account_n0,
check_balancel).
balance and the useful functions can be deposit(), withdraw),
Each task can be separately tested using the automated test cases.

2.2.3 Industrial XP
evolution of XP. It is
The industrial XP (XP) can be defined as the organic
and advanced technical
customer centric. It has expanded role for customers

practices

TECHNICAL PUBLICATIONS - An up thrust for knowledge

 2-8

Software Engineering
to XP XP to ecreate IXP, are as folows.
to
appended

that
are
following issu
following issues are
new
practices
In this
a s s e s s m e n t ,

XP.
assessed
vailable to support
. V a r i o u s

A s s e s s n m e n t :

avai.
R e a d i n e s s
must
be
1. environment
and skilled
stakh.
older
Proper appropriate

i. contain Dro

Team
should
should
support quality
quality
programs and
contimrn
ii.
organization

The
ii.
i m p r o v e m e n t .

culture
ould
shou support new values of agile team.
u s t ho
people mnust be choser
o r g a n i z a t i o n a l

iv. The and

efficient
the agjle
2. Project
Community
:
Skilled

ss of the
of project.
the project.
The team is
is considered. The
referred as the
commAmunih
project communi
success

members
for the approach
is

when
extreme
programming

customers,
and other
stakeholders who play the vit
consists of
technologies,
The role of the community members must
success
of the project.
for the
explicitly defined.

chartering
means assessing the jusi.cation
Chartering: Project the XP team
team assess whether
3.Project business application.
That means,
as a organization.
project of the
and objectives
satisfies the goals
project the state of the proiect andd its progas
For assessing
Driven management:
4. Test measurable criteria.
In test driven driven management t
the industrial needs some XP measurable criteria.
tested with the help of these
project is reri
software increment, the specialized
After delivering the
5. Retrospectives: The intention of retrospectives is
is called as retrospective.
conducted which
industrial XP process.
improve the
The team members are inspired
and encouraged tolem
6. Continuous learning:
that can improve the quality
of the product.
new methods and techniques

Review Questions
1. Discuss XP values and XP process.
GTU:Winter-2019,Marks
Extreme Programming (XP) in detail.
2 Explain

2.3 Other Process Models of Agile Development

Winter-2017, 2018, Mars
GTU: Summer-2016, 2018, are
Various other agile process models apart from extreme programming
1. Adaptive Software Development
2. Dynamic System Development Method

3. Scrum
4. Feature Driven Development

5. Agile Modeling
TECHNICAL PUBLICATIONS An up thrust for knowledge
Sofware Engineering 2-9 Agile Development

us disctuss
them in detail.
Let

23.1 Adaptive Software Development (ASD)

.The adaptive software development approach was

proposed by Jim Highsmith.
This approach is useful in building the complex software systems using iterative
apporach

.The focus of this method is on

working in collaboration and team self
organization.

The life cycle of ASD consists of three

phases of software
are
development and those

1. Speculation 2. Collaboration 3. Learning. (Refer Fig. 2.3.1)

Speculation

Release
or
software Collaboration
increment

Learning
Fig. 2.3.1 Adaptive software development life cycle
1. Speculation: This is initial
phase of the adaptive software development process.
an
In this phase the
adaptive cycle planning is conducted. In this cycle planning
mainly three types of information is used such as Customer's mission
project constraints (delivery date, user description, budgets and so on) statement,
and basic
requirements of the project.
2. Collaboration: The motivated people work collaboration to develop the desired
in
software product. In this
phase collaboration among the members of development
team is a key factor. For successful collaboration and
coordination it is necessary to
have following qualities in every individual -
Assist each other without resentment
Work hard.
O Posses the required skill set.
O Communicate problems and help each other to accomplish the given task.
o Criticize without any hate.

TECHNICAL PUBLICATIONS An up thrust for knowledge

 Software Engineering 2-10
Agite Development
3. Learning: As the team members go on develoni

learning new skills and the

emphasize is on techniques, There are components, the
the team members learn - three
ways by which
groups: The feedback from
o Focus the end-t6ors
is
software component being developed. Thus obtained
direct feedback about the
developed componernt can be obtained,
about the
o Formal technical revieW This
review for
conducted for better quality. software
components
o Postmortems The team analyses its own
appropriate improvements. performance and mak
2.3.2 Dynamic System Development Method(DSDM
In this agile method, the project
met aeaaine 1s
using the the incromes
prototyping approach. This is an iterative development process. menta
The Dvnamic System Development Method (DSDM) consortium has defined an
an arile
process model called DSDM life cycle.

Various phases in this life cycle model are as follows -

1, Feasibility study: By analyzing the business
requirements and constraints
the
viability of thee
application determined in this phase.
is

2. Business study: The functional and informational

requirements are identified
and then the business value of the application is determined. The basic
application
architecture is decided in this phase.
3. Functional model iteration : The incremental approach is
adopted
for development. The basic functionalities are demonstrated to the customer by
building the suitable increments. The intention of iterative cycle is to gather
additional requirements by eliciting the requirements from the customer as each
prototype is being developed.
4. Design and build iteration: Each prototype is revisited during the functional
model iteration to ensure that the business requirements are satistied by each
software component. Sometimes if possible, the design and build activities can be
carried out in parallel.

5. Implementation : In this phase, the software increment is placed in the working

environment. If changes are suggested or if the end-user feels it incomplete then
the increment is placed in iteration for further improvement.
The DSDM can be combined with XP method or ASD concepts to create a
combination model.

TECHNICAL PUBLICATIONS An up thrust for knowledge

 Software Engineering
2-11 Agile Development

2.3.3 Scrum

SCRUM is an agile process model which is used for developing the complex
software systems.
. I t is a lightweight process framework that can be used to manage and control the
iterative and incremental approach. Here the term
software development using
of the process is kept as small as possible in
lightweight means the overhead
order to maximize productive time.
in 1995.
.This model is developed by Jeff Sutherland and Ken Schwaber

Principles below
SCRUM works given are as
. Variousprinciples using which the Due to
teams on the software developmernt projects.
1. There are small working
minimum overhead.and
maximum communication
this there is
clean packets or
people must be partitioned into small and
2. The tasks of
partitions.
business changes if they occur.
must accommodate the technical or
3. The process
increments must be
software increments. These
4. The process should produce
documented and built on.
tested,
inspected, documentation must be
the constant testing and
5.
5. During the product building
conducted.
model of the product
SCRUM process
must produce the working
6 The
whenever demanded or required. and
activities (requirements analysis, design, evolution
Various development
SCRUM principles
delivery) are guided by
Development Activities software process pattern
software process pattern. The
is on
In SCRUM emphasize
activities. Refer Fig. 2.3.2.
defines a set of development
SCRUM are
-

activities in must be
Various development or
features that
requirements
list of project backlog list at any
It is basically
a
in the
1. Backlog : The items can be included
as per the
customer. the priorities
provided to the this list and updates
manager analyses
time. The product
the requirements
achieve
requirements. needed to time-box
units that are
duration o r
These the work
are have fixed
the sprints work in stable
2. Sprint: the backlogs. Typically team
members to
m e n t i o n e d in allow the
Thus sprints
of 2 to 4 weeks).
(typically
a n d s h o r t - t e r m environment.

d a tn thrust forknowiedge
 Sovare Engineemy 2-12

Agialle Developmas
155 min dalih
.Whatmeetinarge
24 Hour
2.NetObsacitavcdteemesaite
plan?
30 Days

Sprint backlog
Product backlog Software
iwithnctement
Specific
Fig. 2.3.2 SCRUM workflow activities
functionalty
3. Meetings: These are 15 minutes daily
meetings to
report
obstacles and plan for next activities. Following are three the completed.
discussed during the meetings questions that

i) What are the tasks done since last meeting ?

i) What are the issues (obstacles) that team is facing?
ii) What are the next activities that are
planned?
4. Demo: During this phase, the software increment is delivered to
implemented functionality which is demonstrated to the customer.
the custome Ihe
focuses
Note that de
on only implemented functionalities and not all the
planned functionali
(and yet to get implemented) of the software product.
Roles
1. Scrum Master The Scrum master leads the
each team member. The
meeting and analyses the response o
potential problems are discussed and solved in t
meeting with the help of master.
2. Team Members These are the
persons working in a team to develop the softwa:
solutions.
Advantages and Disadvantages
Advantages
1. SCRUM model brings transparency in project development status.
2. It
provides flexibility towards the changes.
3. There is improved communication, minimum overhead in development oCess

pl
4. The productivity can be improved.

TECHNIGAL PUBLICATIONSs - An up thrust for knowledge

 Software Engineering 2113
Agile Osveoprriart

Disadvantages:

1. Some decisions are hard to track in fixed time span.

2 There are problems to deal with non-functional requirements of the system.

2.3.4 Feature Drlven Development (FDD)

. Originally Peter Coad suggested this approach for object oriented software
engineering
Stephen Palmer and John Flesing has extended and enhanced Coad's work.
I n FDD, the feature means client valued function. It is an iterative and
incremental software development process
In FDD, the collaborative activities are carried out. These activities are called as
process as shown in Fig. 2.3.3.

Develop Build Plan Design Build

H
an a by by by
Overall feature feature feature feature
model list

List of Development Design Client valued

features plan package functionality

Fig. 2.3.3 Feature driven development life cycle

Various phases in the FDD life cycle are

1. Develop overall model: In this phase the high-level walkthrough of scope and
detailed domain walkthroughs are conducted. Later on peer reviews and
discussions are carried out on these walkthroughs and domain area models are
created. These domain area models are then merged into the overall models.
2. Build features list: Initially the list of features is created. The domain is

functionally decomposed into various subject areas. These subject areas contain the
business activities. The steps within business activity forms the categorized feature
list. Features are basically the client valued functions and can be expressed in the
form.
action> <result> <by|for| of|to> <object>

TECHNICAL PUBLICATIONS- An up thust for knowiedge

 2-14
Sotwere Engineening Agile Development
For example
of the produot
"Display product-specifications
<result> cot> <object>
<Action
3. Plan by feature: After completing the building of feature list
list #hthe developr
are assigned as classes and are chi
plan is created. The features
the class owner is assigned
with appropriate classes. ammer
4. Design by feature: A design package was produced for each fa
ure.
small group of features and these featuresAcAchiuet
programmer selects
a
feature the sequence diacram
developed within two weeks. For each
5. Build by feature : Finally a complete client valued function is da.
each feature. The class owners develop the actual code for their clae eloped
ses and thie
code is promoted to the main build.

Following are some benefits of the features

1. Features represent small block of deliverable functionalities hence
can
better describe, understand and review them.
2 The features can be arranged into hierarchical business related grouping

3. The team can develop every feature within the two weeks.

4. The features are typically smaller in size and therefore can be analyzed
effectively.
5. Project planning, scheduling and tracking can be driven by features.

The FDD can be used to develop complex projects or bigger projects. It can also be
used for the developing the projects having more novice developers

2.3.5 Crystal
Cockburn and Highsmith suggested the crystal family of agile methods
The primary goal of this method is to deliver useful and working software.
I n this model, a set of methodologies are defined which contains the coreeleme
that are common to all. These methodologies also contain roles, process pane
work products and practice that are unique to each.
eful for
Thus the crystal family is actually a set of agile processes that are use
different types of projects. The agile team has to select the memebers or tne
nt.
family that is most approapriate for their ongoing project and environmenl

TECHNICAL PUBLICATIONS An up thrust for knowledge

Sofware Engineering
2-15 Agila Davelopmant

(AM)
2.3.6 Aglle Modellng
The agile modeling can be used for large and complex projects. By adopting agile

modeling techniques the scope and complexity of the project can be understood.

The problems can be partitioned effectively among the group of people. And the
quality of the working model can be assessed at every step of development.
the Agile modeling as "Agile modeling is a collection of
Scott Ambler described
values, principles and practices for modeling the software. Agile Modeling (AM)
is

a practice-based methodology for effective modeling and documentation of

software-based systems. This modeling technique is more effective and light

weight than the traditional modeling technique."

are as follows
Various features suggested by Scott Ambler for agile modeling
-

1. Specify the purpose

for the model: Prior to development of the software
model the goals and objective of the model must be known to the developer
2. Make use of multiple models : Various models can be used to gain the insight
A small
in the software product. Each model can have different perspective.
desired software
amount of set of mnodels can be useful for building the
product.
path: Use only those models that give long term value
so
3. Follow a definite
be
that the work can proceed in definite direction. Every work product must
maintained as changes occur.

not the presentation: The correct

4. Give importance to contents and
information in the model is more important than the flawed representation.

tools: It is necessary to understand

5. Understand the models and supporting
are used and the tools that are
the strengths and weaknesses of the model that
used in development process.
6. Adapt locally: The needs of modeling
team must be satisfied by adopting
appropriate modeling approach.

Review Questions
1. Explain the Scrum agile development process.
2. Write a note on Feature driven dervelopement.
3. List the diferent agile process model and explain any one with suitable example.
GTU: Summer-2016, Marks 7
4. Explain the merits and demerits of SCRUM.
GTU: Winter-2017, Marks 4; Winter-2018, Marks 7
5. Explain adaptive software development process model. GTU: Summer-2018, Marks 7

TECHNICAL PUBLICATIONS An up thrust for knowledge

Sofware Engineering 2- 16 Agile Development
2.4 Tools for Agile Process
The objective of agile development tools is to help in one or more activitiesi
agile development. Due to use of such tools the operational development softwara
can be created rapidly.
The agile tool set consists of automated
support for project planning, use case
development, and requirements gathering, code generation and testing.
The project management tools focus on preparing 'Earned value charts' instead of
preparing the Gnatt charts.
The purpose of agile tools is to enhance the environment.
Examples of various agile tools
1. Actif Extreme This tool is
:
developed by Microtool. It provides the support for
various technical activities.
2. Ideogramic UML : It is develoed by Ideogramic. This tool is used within the
agile
process.
3.Together tool set It is distributed
by Borland. It
technical activities within the XP (Extreme provides the support for the
Programming) and other agile processes.