Date post: | 20-Jun-2015 |
Category: |
Business |
Upload: | manuel-pistner |
View: | 198 times |
Download: | 0 times |
1/16
DRUPAL Projects! Agile? Fixed – Price?
...and HOW to succeed!
WhatIs a project
2/16
● Does not end in itself
● (Hopefully!) Clear goal
● Unique
● Start AND END (!)
● Limited resources
HowTo make projects successfull?
3/16
● Know, what you want (SMART)
● Spread the goals in your team
● Plan! (The way to your goals)
=> Remember: A goal without a plan is just a wish!
WhatTo differentiate?
4/16
● Project management method
● Payment and delivery agreements
● Contract types
=> Each must be clear defined, all can be mixed with each other
WhichPM methods exist?
5/16
● Agil (Scrum)
● Waterfall
● (... other derived methods)
Agile PMcharacteristics
6/16
● Requirements always change
● Iteration ("mini-projects")
● High flexibility
● Increasing business value each iteration
Agile PMAdvanages
7/16
● Flexibility
● Product will adapt itself
● More value each iteration
● Quick first usable results
Agile PMDisadvantages
8/16
● Duration for the TOTAL project unknown
● TOTAL costs unknown
● Results are not clear from the beginning
Waterfall-modelCharacteristics
9/16
● Clear and specific requirements
● Project planed from the very beginning
● Step by step iterations
● V-Model derived
Waterfall-modelAdvantages
10/16
● Well known costs for clear requirements
● Predictable timeline
● Result is clear defined
● Highest possible project control
Waterfall-modelDisatavantages
11/16
● Less flexibility
● Long planning phase
● Result may be unusable due to changing requirements
Payment-modalitiesWhen you will get paid
12/16
● Payment method is not related to PM method
● Clear agreement what needs to be done to get paid!
WhichPrice models exist?
13/16
● Fixed price (mostly contract for work and labor)- Fixed price for fixed delivery or service
● Price per hour (T&M)- Fixed price for a service unit (time)
WhichContracts exist
14/16
● Fixed price contract (Result owed)
● Time & Material (Just the work is owed)
● NOTHING ELSE!
WhatAlways to clearify
15/16
● HOW the project will be managed
● WHO is responsible for WHAT
● WHAT is owed / needs to be delivered?
● WHEN you will be paid
Fixed-Price contractcharacteristics
16/16
● Clear and specific result is owed
● Extra costs because of flexibility
● Safety (result AND price are fixed)
● Conflicts because of change requests
Time & MaterialCharacteristics
17/16
● Only working time owed
● No result owed
● Customer buys a team
● Conflicts because of „quiet“ extra costs
WhichVariants exist?
18/16
NONE!
Only variation on project organisation
WhichVariants exist?
19/16
● Fixed price without agility
● Fixed price for single iterations
● Agile fixed price
● Fixed price „for everything" and agile management (!)
WhichGoals does each follow?
20/16
● Waterfall management and fixed price=> Develop a clear specified product with fixed time and budget
● Agile management and price per hour=> Develop an ideal (!) product respecting changes
Fixed price without agilityAdvantages
21/16
Customer● Safe budget, safe and fixed scope
Provider● Chance for profit● Clear goals to get paid● Planable for resources and finance
Fixed price without agileDisadvantages
22/16
Customer● High effort for conception and planning● Planning / calculation with buffer● No flexibility or more expenses
Provider● Increasing risk with less detailed specification
Fixed price for each iterationAdvantages
23/16
Customer● Budget safety for each iteration● Independency● Flexibility
Provider● Opportunity for profit and less risk
Fixed price for each iterationDisadvantages
24/16
Customer● No total price for complete project
Provider● Low planning safety for resources and budget
Agile fixed priceHow does it work?
25/16
Requirements with estimations can be changed by new requirements with the same estimation.
Agile fixed priceWhat do you need?
26/16
Well planned project requirements and estimations to make these requiremetns interchangable.
Agile fixed priceAdvantages
27/16
● Safety by fixed price for fixed feature set● Flexibility by priorisation● Transparency
=> Fair break down of risks and opportunities of project was set up the right way
Agile fixed priceDisadvantages
28/16
● Change requests only with agreement of both parties
● Detailed specification required
Fixed price AND agile
29/16
Fixed price for „all“ AND
Agile management
=> Does not match, will never work!=> Desaster for the project!
Fixed price and agileWhat does that mean?
30/16
Fixed price for „all“ AND
agile management
=> Changes are included in fixed price
Fixed price and agilWhat does that mean?
31/16
Fixed price and agileWhat will happen?
32/16
● When and why will you get paid?
● What needs to be done for the fixed price?
● When will the project end?
Fixed price and agileWhat will happen?
33/16
Conclusion: The PROVIDER agrees to do EVERYTHING the customer wants and as long the customer wants him to do this.
Fixed price AND agileHow will it end?
34/16
● More and more feature requests as changes cannot be avoid
● Budget overdue
● Quality will suffer
● Unsatisfied project partners
Fixed priceWhat to keep in mind
35/16
● Fixed price = clear requirements
● Clear agreement WHAT needs to be done for WHICH price
● Warranty
● Specify acceptance and approval tests
Fixed priceWhat to keep in mind
36/16
● Clear change request process● Document project process● RIGHTS and DUTIES for both project parties
Common mistakesTo avoid
37/16
● „We don't need a contract“● „Just trust me“● „We will pay by progress“● „We want a web page such as XYZ“● „Design will be delivered later“● „No clear responsibilities“● „More developers = quicker results“
Most mistakesIn any case
38/16
Have their origin in the planning, agreements and setup of the project!
● PLAN● MESSURE● COMMUNICATE
● Your goals well!