This slide share will help users to understand the agile software development methodology and how does it work. It also defines the whole process to implement scrum methodology.

1. Agile Software Development
Model
Agile Software Development Model describes the set
of principles for software development under which
requirements and solutions evolve through the
collaborative effort of self-organizing cross functional
teams.
Why do we need to adopt Agile Software
Development Model?
• Too much emphasis on producing documentation and
tools.
• Later changes to the requirements after the SRS
document has been completed are discouraged.
• No customer/ stakeholders interactions after the
requirement has been specified.

2. Agile Manifesto
Some of the principles behind the agile model were
published in the agile manifesto as follows:
-Our highest priority is to satisfy the customer through
early and continuous delivery of valuable software.
-Welcome changing requirements, even late in
development. Agile processes harness change for the
customer's competitive advantage.
-Deliver working software frequently, from a couple of
weeks to a couple of months, with a preference to the
shorter timescale.
-Business people and developers must work together
daily throughout the project.

3. -Build projects around motivated individuals. Give
them the environment and support they need, and
trust them to get the job done.
For more principle refer www. http://agilemanifesto.org
How does agile work?
The agile model emphasizes incremental release of
working software as the primary measure of progress.
Below are the popular Agile SDLC models:
•Scrum
•Crystal
•Atern (formerly DSDM(Dynamic System
Development Method))
•Feature-driven development FDD
•Extreme Programming(XP)
•Lean Development
•Unified process

4. Agile Scrum XP
Agile Team
Leader
Scrum Master Team Leader
Customer
Representative
Product Owner Customer
Representative
Team Members Scrum Team Team Members
Time Box Sprint Time Box
Type of Roles in Agile

5. Scrum Methodology
Scrum is a process framework that has been used
to manage complex product development since the
early 1990.
Scrum Master is a keeper of scrum team.
Product Owner is only responsible for product
backlog by expressing product backlog items
clearly and prioritize the product backlog items to
achieve goal.
Scrum Team is s self organized and cross
functional. To develop the software product, scrum
team will works in collaboration. Scrum team
include all developers, designer, tester, analyst,
according to the requiremnt.

6. Scrum master’s responsibility
 To the Product Owner
› By finding technique for effective product backlog
management.
› Ensure that product owner knows how to arrange
the product backlog to maximize value.
› Helps the product owner in prioritize the product
backlog and create sprint backlog.
 To the Scrum Team
› Helps the scrum team to understand the need for
clear and concise product backlog items.
› Couching the scrum team about scrum
methodology.
 To the Organization
› Leading and couching the organization in its scrum
adoption
› Planning scrum implementing with the

7. Scrum Process Framework
Sprint(2-weak/ 1-
month)
Sprint
Review
Sprint
Backlog
Product
Backlog
Prioritized
Product
Feature
Sprint
Retrospective
Sprint
Planning
&
Monitorin
g
Releas
e
(Working Product
Increments)
Daily
Scrum
Meeting
Product
Feature
Assigned to
sprint

8. Type of Artifacts and Events
The following artifacts are defined in Scrum
Process Framework
• Product Backlog
• Sprint Backlog
• Burn-Down Chart
• Increment
The vital events of scrum are following:
• The Sprint
• Sprint Planning
• Daily Scrum Meetings
• The Sprint Review
• The Sprint Retrospective

9. User Story
User story is very high level definition requirement ,
contain just enough information so that developer can
produce a reasonable estimate of the effort to
implement it.
User Story Structure:
As a <Type of user>,
I want <to perfume some task>,
So that <I can achieve some benefits/ goals/ values>.
Scenario: The name of scenario
Given < an initial condition >
When <some thing happens >
Then <this is the result >

10. Example of User story :
Customer’s cash withdrawal
As a customer,
I want to withdraw cash from ATM,
So that I don’t have to wait in line at the bank.
Acceptance Criteria
Given that the account is credit worthy
- And credit is valid
- And the dispenser contains cash,
When the customer requires the cash
Then ensure the account is debited
- And ensure cash is dispensed
- And ensure the card is returned

11. What are the advantages of acceptance criteria ?
- Triggers the thought process for the team to think
through how feature will work from the end user
perspective.
- Helps the team to write accurate test cases without
any ambiguity to under stand business values.
- Eliminate the un-necessary scope that will add no
value to the story, in other word, it will keep the right
content.
- User story is not completed until it has verified
acceptance criteria
- Acceptance criteria also help the team quickly size
the user story will be verified, they understand they
effort needed to make it happen.