Agile Development

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

Agility
Agility is ability to move quickly and easily.
It is a property consisting of quickness, lightness, & ease of
movement;
The ability to create and respond to change in order to profit in a
turbulent global business environment
The ability to quickly reprioritize use of resources when
requirements, technology, and knowledge shift
A very fast response to sudden market changes and emerging
threats by intensive customer interaction
Use of evolutionary, incremental, and iterative delivery to
converge on an optimal customer solution
Maximizing BUSINESS VALUE with right sized, just- enough,
and
just-in-time processes and documentation

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

What is Agility?
Current Functionality

Effective
response
to change
Change Request

Organizing
a team Effective
so that it is communication
in control among all
to perform stakeholders
the work

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

What is Agility? Cont.
Software Development Team
Rapid and Incremental delivery of software

Customer

Drawing the
customer onto
the team

Eliminate the
“us and them”
attitude

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

Agile Process
Agile software process addresses few assumptions
• Difficulty in predicting changes of requirements and customer
priorities.
• For many types of software; design and construction are
interleaved (mixed).
• Analysis, design, construction and testing are not as predictable
as we might like.
An agile process must be adaptable
Requires customer feedback

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

Agility Principles
Highest priority is to satisfy the customer through early &
continuous delivery if software
Welcome changing requirements
Deliver working software frequently
Business people and developers must work together
Build projects around motivated individuals
Emphasize face-to-face conversation
Working software is the measure of progress
Continuous attention to technical excellence and good design
Simplicity – the art of maximizing the amount of work done
The best designs emerge from self-organizing teams
The team tunes and adjusts its behaviour to become more
effective

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

Where agile methodology not work

Project plan & requirements Unclear understanding of Agile

are clear & unlikely to Approach among Teams
change

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

Where agile methodology not work

Big Enterprises where team

collaboration is tough

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

Agile Process Models
Extreme Programming (XP)
Adaptive Software Development (ASD)
Dynamic Systems Development Method (DSDM
Scrum )
Feature Driven Development
(FDD)
Crystal
Agile Modelling (AM)

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

Extreme Programming (XP)

Extreme Programming (XP) is an agile software

development framework that aims to produce higher
quality software, and higher quality of life for the
development team.

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

 XP Values
Communication: To achieve effective communication, it
emphasized close & informal (verbal) collaboration between
customers and developers
Simplicity: It restricts developers to design for immediate needs
not for future needs
Feedback: It is derived from three sources the implemented
software, the customer and other software team members, it
uses Unit testing as primary testing
Courage: It demands courage (discipline), there is often
significant pressure to design for future requirements, XP team
must have the discipline (courage) to design for today
Respect: XP team respect among members

Unit-2: Agile Development Darshan Institute of Engineering & Technology

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari
The XP Process
It considers four
framework
activities

1. Planning
2. Design
3. Coding
4. Testing

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

The XP Process cont.
Planning • User Stories
• Customers assigns value (priority)
• Developers assigns cost (number of development weeks)
• Project velocity
• Computed at the end of first release
• Number of stories implemented in first release
• Estimates for future release
• Guard against over-commitment

Design • Keep-it-Simple (Design of extra functionality is discouraged)

• Preparation of CRC card is work project
CRC • CRC cards identify and organize object oriented classes
card • Spike Solutions
• Operational prototype intended to clear confusion
• Refactoring
• Modify internals of code, No observable change

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

The XP Process cont.
Coding • Develops a series of Unit test for stories
included in current release
• Complete code perform unit-test to get
immediate feedback
• X recommend pair-programming, “Two
P
heads are better than one”
• Integrate code with other team members, this “continuous
integration” helps to avoid compatibility & interfacing problems,
“smoke testing” environment to uncover errors early

Testing
• Unit test by developers & fix small
problems
• Acceptance tests - Specified by customer

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

What is Scrum?

A scrum is a method of restarting play in rugby that

involves
players packing closely together with their heads down and
attempting to gain possession of the ball. ...

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

Scrum
Scrum is a framework that helps teams work together. ... Often
thought of as an agile project management
framework, Scrum describes a set of meetings, tools, and roles that
work in concert to help teams structure and manage their work.

Product Backlog Sprint Daily Scrum Meeting

Product Owner
Product

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

Scrum framework at a glance
Inputs from Customers,
Team, Managers

Team Selects starting at Scrum

top as much as it can Master
commit to deliver by Daily Scrum
end of sprint Meetings

Product Owner Sprint Review

Sprint Finished Work

Product Sprint Planning Backlog
Backlog Meeting

Prioritized list of what is required: Sprint end date and team

features, bugs to fix... deliverable do not change
Sprint Retrospective

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

Scrum cont.
1. Backlog
• It is a prioritized list of project requirements or features that
must be provided to the customer.
• The items can be included in the backlog at any time.
• The product manager analyses this list and updates the
priorities as per the requirements.
2. Sprint
• These are the work units that are needed to achieve the
requirements mentioned in the backlogs.
• Typically the sprints have fixed duration or time box (of 2 to 4
weeks, 30 days).
• Change are not introduced during the sprint.
• Thus sprints allow the team members to work in stable and
short-term environment.

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

Scrum cont.
3. Scrum Meetings
• There are 15 minutes daily meetings to report the completed
activities, obstacles and plan for next activities.
• Following are three questions that are mainly discussed during
the meetings.
1. What are the tasks done since last meeting ?
2. What are the issues that team is facing ?
3. What are the next activities that are planned?
• The scrum master leads the meeting and analyses the response of
each team member.
• Scrum meeting helps the team to uncover potential problems as
early as possible
• It leads to “knowledge socialization” & promotes “self-organizing
team structure”

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

Scrum cont.
4. Demo
• Deliver software increment to customer
• Implemented functionalities are demonstrated to the customer

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

Adaptive Software development (ASD)
This is a technique for building complex software systems using
iterative approach.
ASD focus on working in collaboration team self-organization.
and
ASD incorporates three phases

1. Speculation
2. Collaboration
3. Learning

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari

 Speculation (ASD)
The adaptive cycle planning is conducted.
In this cycle planning mainly three types of information is used
• Customer’s mission statement
• Project constraints
• Delivery date, budgets etc…
• Basic requirements of the project

Unit-2: Agile Development 24 Darshan Institute

Darshan Institute of
of Engineering
Engineering &
& Technology
Technology
© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari
 Collaboration (ASD)
In this, 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 (offense)
• Work hard
• Posses the required skill set
• Communicate problems and help each other
• Criticize without any hate

Unit-2: Agile Development 25 Darshan Institute

Darshan Institute of
of Engineering
Engineering &
& Technology
Technology
© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari
 Learning (ASD)
Emphasize is on learning new skills and techniques.
There are three ways by which the team members learn
• Focus groups
• The feedback from the end-users is obtained.
• Formal technical review
• This review is conducted for better quality.
• Postmortems
• Team analyses its own performance and makes appropriate
improvements.

Unit-2: Agile Development 26 Darshan Institute

Darshan Institute of
of Engineering
Engineering &
& Technology
Technology
© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari
Dynamic Systems Development Methods
(DSDM)
Ø Various phases of this life cycle model

• Feasibility study
• By analysing the business requirements and constraints the
viability of the application is determined
• Business study
• The functional and informational requirements are identified and
then the business value of the application is determined
• Functional model iteration
• The incremental approach is adopted for development
• Design and build iteration
• If possible design and build activities can be carried out in parallel
• Implementation
• The software increment is placed in the working environment
Unit-2: Agile Development 27 Darshan Institute
Darshan Institute of
of Engineering
Engineering &
& Technology
Technology
© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari
 Feature Driven Development (FDD)

Unit-2: Agile Development 28 Darshan Institute

Darshan Institute of
of Engineering
Engineering &
& Technology
Technology
© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari
 FDD cont.
It is practical process model for object oriented software
engineering.
In FDD, the feature means client valued
function. Various phases in the FDD life cycle
1. Develop overall model
• The high-level walkthrough of scope and detailed domain
walkthrough are conducted to create overall models.
2. Build feature list
• List of features is created and expressed in the following
form
– <action> the <result> <by for of to> a(n) <object>
– For Ex. “Display product-specifications of the product”

Unit-2: Agile Development 29 Darshan Institute

Darshan Institute of
of Engineering
Engineering &
& Technology
Technology
© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari
 FDD cont.
3. Plan by feature
• After completing the feature list The development plan is
created
4. Design by feature
• For each feature the sequence diagram is created
5. Build by feature
• Finally the class owner develop the actual code for their
classes

Unit-2: Agile Development Darshan Institute of Engineering & Technology

© LPU :: CAP437: SOFTWARE ENGINEERING PRACTICES : Ashwani Kumar Tewari