Agile fixed-price-slide share
-
Upload
kurush-wadia -
Category
Technology
-
view
265 -
download
0
description
Transcript of Agile fixed-price-slide share
Agile in Fixed Price Projects
Kurush P. Wadia
12th November, 2010
Contracts are about protection
2
Agile is about trust
3
• Individuals and interactions over processes and
tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan
While there is value in items on the right, we value the items on
the left more.
Agile Manifesto
4
… want to know what their
total costs are
Customers usually…
… are conscious of
both, schedule and
cost
… want measurable business
value using the developed
software
5
Excellent relationships and successful projects…
6
But when things go wrong…
• For customer
• Loss of business value
• Scope changes
• For seller
• Extra effort
• Unhappy customer
7
Prerequisites for Fixed Price
Inputs and requirements have to be clear
8
Prerequisites for Fixed Price
Risks and dependencies have to be minimal
9
Feasibility & Assumptions
10
Business
Requirements
Technical
Feasibility
User Friendly
Design
Feature list in Scope Statement drives the
estimates for:
– Scope in terms of Story Points
– Project duration in terms of Months/Weeks
– Cost in terms of €
Planning for the Project
11
Principles Of Agile Not To Be Compromised
12
Put the right people on the team
(customer and development)
Agile teams therefore need to…
Determine and communicate
business value upfront
Set a project completion date
13
… goals rather than targets based on
money and time available
Contracts could be framed around…
14
15
Time
Fixed Price Time &
Material
Profits
Contracts could be framed around…
Possibility to switch to T&M
in case assumptions in the
contract turn invalid
Spirit of the Contract…
16
We'll collaborate together
to define the best set of
detailed features to go live
with, on that date, for that
price.
Thank you! This will help
us do justice to your
business needs and be
open to any changes that
might come in the future.
• Dynamic Systems Development Method
• Some key tenets
– There will always be business change
– You can move forward as soon as enough is known
– Timeboxed iterations help us meet an unmovable
deadline
– Prioritize using MoSCoW principle
Introducing DSDM
17
DSDM Philosophy
Fixed
Variable
Traditional DSDM
Quality
Features
Time Cost Features
TimeCost
Quality
18
DSDM Lifecycle
19
DSDM Organization
• MoSCoW Principle
– Must – has to be done (60-
75%)
– Should – important but may
be worked around short-term
(20%)
– Could – may be left out if
necessary (20%)
– Won’t – add to the list to be
done next time
Technique in DSDM – MoSCoWPrinciple
Won’t
Must
Should
Could
Out of scope
21
• Quality is planned from the start
– Product Quality Criteria
• Facilitated Workshops
• Continuous focused user involvement
• Reviews
– Prototypes
– Supporting documents
• Testing through the lifecycle
• Base-lined requirements
• Configuration management
Quality in DSDM
22
• Several extra roles
• Existing roles need additional tasks
• Additional risks
• Additions to phases
Risks in DSDM
23
• Weigh pros and cons of Agile in fixed price so as
not to lead to scope changes
• Feasibility study is vital
• DSDM can provide flexibility with control but has
additional roles, phases, and tasks to it
• Quality should never be compromised
Summary
24
Questions?
25