2. Objective of this Presentation
Current challenges with Waterfall Methodology,
Reasons for Fuzzy Requirements
The Agile Umbrella
Advantages of using Agile Methodologies
What is in it for me ?
VersionOne Survey Results
3. 3
Challenges in the Traditional Method
Unclear/Fuzzy
Requirements
Cannot
accommodate
changes quickly
Testing very late
in the project
User
involvement
only at the
beginning & end
Heavy
Documentation &
Sign offs
Working software
visible very late
4. Why software projects fail ?
Standish CHAOS Report, 2010
37%
21%
42%
Successful Failed Challenged
Reasons for failure:
• Incomplete requirements
• Lack of user involvement
• Lack of resources
• Unrealistic expectations
• Lack of executive support
• Changing requirements and
specifications
5. Sources of Fuzzy Requirements
• Changing Market Dynamics
• Evolving Technology & Tools
• Business Needs getting more complex
• Multiple Stakeholders
• Expectations of the products and service
qualities increasing
5
7. Delivering the “Right Value”
Rarely
19%
Never
45%
Always
7%
Often
13%
Sometimes
16%
Ref: Jim Johnson, Chairman of Standish Group, quoted in 2006 in:
http://www.infoq.com/articles/Interview-Johnson-Standish-CHAOS
Sample: government and commercial organizations, no vendors, suppliers or consultants
Focusing on customer needs
ensures:
the right features are built
not wasting effort (and
resources) on features that are
not needed
Main principle:
Only build the features
that the client/users need
7
9. What is Agile Development ?
• Agile software development is a group of
software development methods based on
iterative and incremental development, where
requirements and solutions evolve through
collaboration between self-organizing, cross-
functional teams.
• It promotes adaptive planning, evolutionary
development and delivery, a time-boxed iterative
approach, and encourages rapid and flexible
response to change.
9
10. The Agile Manifesto
Agile is a set of values:
– Individuals and interactions over processes and tools
– Working software (Products) 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.
10
11. Agile Umbrella
Agile
Crystal
XP
Scrum DSDM
FDD
Kanban RUP
RUP (120+)
XP (13)
Scrum (9)
Kanban (3)
Do Whatever!! (0)
More Prescriptive
More Adaptive
RUP has over 30 roles, over 20
activities, and over 70 artifacts
more rules to follow
fewer rules to follow11
12. 12
Agile = Early Value
Time
Analysis
Design
Coding
Testing
20% done
(100% usable!)
Time
Analysis
Design
Coding
Testing
Do we have half
a solution yet?
Traditional Process Agile Process
14. Characteristics of Agile Delivery
• Short cycles (1-4 weeks):
– At the beginning of each cycle, figure out what are the most important
things to do right now
– Demonstrate what was done at the end of each cycle (make it
available for use if appropriate)
• Welcome feedback (and act on it)
• The team focuses on one thing at a time, until it is done
• Defer requirements definition until just before you build them
• Create cross-functional teams that include both business and technical
people
• Promote adaptive planning and a people-centric approach
14
15. What is in it for me?
• Customer
Have Opportunity to provide feedback early
Go to market faster with Quality
Faster return on investment
• Leadership
To understand progress in terms of real progress made on
product .
Better engaged & accountable team
15
16. What is in it for me?
• Team Member
A sustainable pace
Satisfaction of quality product delivered
Clear Priority and less interruption during development
• Organization
Highly ROI based on Fixed Cost
Motivated working for a common goal
Vibrant culture with a high Customer Satisfaction
16
17. Benefits of Agile Approach
• Stakeholder Engagement
• Transparency
• Early and Predictable Delivery
• Predictable Costs and Schedule
• Allows for Change
• Focusing on Business Value
• Focusing on Customers
• Improving Quality
17
18. Survey – Agile Benefits
Source: VersionOne 2012 Annual State of Agile Development Survey