Transcript Slide 1

Iterative Executive Overview
Agenda
• Iterative Methodology
–Basics
–Benefits
When to use it
Measuring Success
Executive Role
•
•
•
2
Iterative Executive Overview
The Iterative Methodology
3
Iterative Executive Overview
Imagproje Area
Iterative Methodology
• An approach somewhere between the traditional
Waterfall and the more recent Agile methods
• A hybrid approach which utilizes elements of both
methodologies
• The key word is “risk”
• The basic unit of the methodology
is the “the iteration”
4
Iterative Executive Overview
Iterative Fundamentals – the Iteration
• Identify AT A HIGH LEVEL the functional and
non-functional requirements of the project
Select the requirement that carries the most risk
Then…
•
•
Requirements
- Elaborate that requirement
Design
Planning
Test
Build
Implementation
(Internal or External)
5
Iterative Executive Overview
- Design, Build, and Test a
release that directly addresses
that requirement / risk
- Evaluate the release and what
was learned
- and then Repeat
Iterative Principles in Practice
• Address high-risk requirements first
• Address requirements in small batches
• Deliver frequent business value in the form of
releases
6
Iterative Executive Overview
Characteristics of an Iteration
• Every Iteration is a discrete time box (4 weeks),
ending on time
• Iterative work is defined by intended release
(produced every Iteration)
• The development team works only on current
Iteration work
• An evaluation is performed at the end of the
Iteration based upon the identified intention
• Every Iteration is aimed at reducing risk
7
Iterative Executive Overview
Iterations are Grouped by Phases
Requirement
s
Design
Planning
Test
Build
Implementation
(Internal or
External)
8
Iterative Executive Overview
Interpretation of Phases
Phase
Incorrect Interpretation
Correct Interpretation
Inception
High-Level
Requirements
Business and
Conceptual Risks
Elaboration
Detailed Requirements
and/or Design
Architectural/Technical
Risks
Construction
Implementation and
Development; Team
Testing
Logistical Risks (the risk
of not getting all the work
done)
Transition
Acceptance Testing
Solution roll-out
(delivery) Risks
Source: “Managing Iterative Software Development Projects” by Bittner and Spence
9
Iterative Executive Overview
Each Iteration Results in a Release
• Release Possibilities:
–Proof of concept
–Prototypes to demonstrate a particular
capability
–Internal releases for purposes of furthering the
project
–Product releases to the customer
“a stable, integrated and tested, partially complete system” – “Agile
and Iterative Development” by Craig Larman
10
Iterative Executive Overview
What are the benefits?
• Manage risk
– Increase the probability of a successful project by
proactively dealing with risks based on priority
• Manage rapidly changing priorities
– Since requirements are susceptible to rapid change,
save money and time by not attempting to capture all
detailed requirements up-front
• Manage scope
– Allows a cost-benefit approach to determining when
additional capabilities are not justified by their cost
• Eliminate unsuitable solutions early in the project
– Save time, money, and increase the probability of
project success
11
Iterative Executive Overview
When Would We Want to Use It?
• Iterative Methodology can be useful where there
are complex, interactive strategic/tactical solutions
–Requirements gathering is difficult because of
feedback loops
–Approach is difficult to know except through an
iterative approach
12
Iterative Executive Overview
Indications of a Successful Iterative Project
• The Project Manager is:
–Aggressively driving out risk
–Showing incremental increasing capability as
accepted by the customer
–Confirming increasing quality
–Displaying increasingly reliable estimates
–Providing the correct business solution
13
Iterative Executive Overview
The Necessity of Understanding and Engagement
• An Iterative approach provides many benefits but requires
the business understand how it participates in the project
– Iterative requires consistent business involvement to
ensure the development of the proper product and
features
– Management must maintain and communicate product
roadmap and the release strategy
– Ensure that Iterative projects utilize risk-driven
techniques
– Understand that documentation will evolve throughout
the project
14
Iterative Executive Overview
Questions?
15
Iterative Executive Overview
Image Area