Professional Documents
Culture Documents
Months
1 2 3 4 5 6 7 8 9 10 11 12
Software Development
Construction
4 weeks 5 weeks 42 weeks 1week
As each phase of the project is delayed, the remaining phases get moved back
but the deadline remains the same, causing compression in the last stages.
Delays are often caused by individuals who are reticent to sign-off the preceding
stage.
6
Where Will Agile Fit
unknown
chaotic
CO
M
requirements
difficult PL
EX
simple difficult
known unknown
technology
What is Agile
Agile Methodology
• An iterative and incremental (evolutionary) approach to software development which is performed in a
highly collaborative manner by self-organizing teams within an effective governance framework with
"just enough" ceremony that produces high quality software in a cost effective and timely manner which
meets the changing needs of its stakeholders
10
Agile Manifesto
Onsite customer
Metaphor
Sprints Release plan
Small releases
Continuous Integration
Errors
Weekly Build
Daily Build
Time
Value added
Processes
Cost Of Change
Cost of change
Project stage
Agile - SCRUM
• Jeff Sutherland – One of the originators of Scrum and was one of the first
people to apply Scrum to a real project
• Ken Schwaber – One of the originators of Scrum
• Mike Beedle – Successfully used Scrum in numerous large-scale projects and
authored the book “Agile Software Development with Scrum” along with Ken
Schwaber
Waterfall vs. SCRUM
Analysis
Design
Code
Waterfall Test
A A A A
D C D C D C D C
T T T T
Agile
Scrum
SCRUM Dev Model
QMS With SCRUM
• CMMI-
descriptive
and not
prescriptive
• QMS can
include agile
methods
and achieve
CMMI
Characteristics Of SCRUM
• Self-organizing teams
• Product progresses in a series of month-long “sprints”
• Requirements are captured in a list of “product backlog”
• No specific engineering practices prescribed
• Impediments to releasing finished software become visible sooner
• Time-boxed
• Values delivering software over documentation
• No software can be demonstrated to the Product Owner that is not “done
Involvement Vs Commitment
Chicken and a Pig are together when the chicken says “ Lets start a restaurant!”
The pig thinks it over and says’ “ What would we call this restaurant?”
The chicken says, “Ham n’ Eggs!”
The pig says,” No thanks, I’d be committed, but you’d be only involved!”
S3 (Release Scrum
of Scrums)
S2 (Cross- Module /
Component Scrum of
Scrums)
S1 (Scrum Teams)
Roles
• Product Backlog
• Requirement List Pertaining To The Product
• The Product Owner / Product Manager Owns This Artifact
• Priority on requirements can be set only by the Product owner / Product Manager
• Product Owner / Product Manager Can Add Requirement To This List
• Release Backlog
• Requirements Selected For A Specific Release
• Product Owner / Product Manager Owns This Artifact
• Sprint Backlog
• Sprint Goals, Selected Features, Tasks, Work Effort, Team Details, Issues & Risks
• Scrum Owns This Artifact
• Product Increment
• The Most Weighted Artifact & This Is The Output Of The Sprints
• This Is A Version Of The Product
• It Contains Shippable Functionality Adequately Tested & Documented
SCRUM Usage In Industry
• Ken Schwaber
• Mike Beedle
Thank you