PracticeLeadersManagement&Communication18042012YuriyKudin-Fixed cost projects presentation
description
Transcript of PracticeLeadersManagement&Communication18042012YuriyKudin-Fixed cost projects presentation
www.ciklum.net
Fixed costs projects
Practical experience
Agenda
Pre-sale Planning Implementation Finishing SCRUM
www.ciklum.net 2
On which phase a project manager is starting a fixed-cost project?
www.ciklum.net 3
Pre sale
www.ciklum.net 4
1. Pre-sale Needs Estimation Tips
Understand needs
www.ciklum.net 5
Learn Ask Draw Concept
Learning of customer needs
The best way – face to face meeting Or video conference
www.ciklum.net 6
Ask as much as possible!
Ask as much as possible Show examples
www.ciklum.net 7
Make and present mock-up’s
www.ciklum.net 8
Project concept
Looking for existed solutions (Goal: cost reducing). Prepare a few options. Prototype
www.ciklum.net 9
Estimation
Do not forget Gaps in specification Risks
www.ciklum.net 10
Estimation: Do not forget
www.ciklum.net 11
Warranty effort
www.ciklum.net 12
Buffer for small changes
www.ciklum.net 13
Effort for meeting and ongoing issues
www.ciklum.net 14
Effort for documentation
www.ciklum.net 15
Pre sale effort
www.ciklum.net 16
Example
www.ciklum.net 17
Gaps in the specification
Assumptions “Will be implemented like …” Implement as T&M part. Notice:
Bug fixing is also part of T&M! Additional management for managing T&M part
www.ciklum.net 18
How to handle gaps in the specification ?
Example of assumptions: We assume that workflow module should contain about 10
screens with complexity like “email configuration screen” Integration with python will implemented using simple
interface: each python script should be presented like a function with hardcoded input and output parameters. Through admin part it is only possible change body of the script but not the interface. In the price is included integration of 2 scripts
Will be implemented 2 reports with complexity like “Insured persons report”
www.ciklum.net 19
Risks
List of risks: Description Probability Influence Mitigation plan Trigger Migration plan
www.ciklum.net 20
Risk handling
Share with the customer Include in price
www.ciklum.net 21
How to include risk in the price
www.ciklum.net 22
Calculated risk cost (Rc) Probability (P. From 0 to 1) Risk reserve (Rr) Rr=Rc*P
Tips& tricks
Team/duration People involving Fixed cost magic Commercial correction
www.ciklum.net 23
Project duration/team
Split project on sub projects (as well sub-contracts) Build small teams
www.ciklum.net 24
People involving
Involve on pre-sale stage people who will take a part in the project implementation
www.ciklum.net 25
Magic multiplier
Magic multiplied based on experience For example:
Effort=Estimated effort(dev)*2,2 0,3 – Estimation error 0,4 – Testing 0,3 – Management 0,2 – Communications etc.
www.ciklum.net 26
Commercial correction
Effort -> $ Stomach feeling Consulting with sales department Is it possible with final amount to finish the project?
www.ciklum.net 27
Project planning
2. Planning
www.ciklum.net 28
Communication plan
www.ciklum.net 29
Time buffer before milestones
www.ciklum.net 30
Reaction time of the customer
www.ciklum.net 31
Acceptance criteria
www.ciklum.net 32
Invoicing plan
Lineal distribution Payment after milestone delivery Payment after project delivery
www.ciklum.net 33
On implementation
3. Implementation Risk review “Small changes” Change requests Reporting
www.ciklum.net 34
Risks
Plan of risks analyzing Update involved people (customer, sales, supervisor etc)
www.ciklum.net 35
Small changes
You have a buffer for them Efforts of small changes must be controlled Customer always needs much more Use batching strategy
www.ciklum.net 36
Change requests
Definition of CR must be created and agreed Don’t show real spent effort for CR (common JIRA) Strategies:
Include Postpone
www.ciklum.net 37
Including strategy
The customer will be noticed concerning duration and budget changes before implementation
www.ciklum.net 38
Important notice
Effort spent for CR clarification will be included in final estimation
www.ciklum.net 39
Postpone
CR’s cold be collected and realized as a minor release It is bad idea to implement CR’s separately
www.ciklum.net 40
Important notice
Estimated scope of work must be described in CR
www.ciklum.net 41
Notice
Use the similar approaches as on pre-sale stage: Assumptions T&M Like example
www.ciklum.net 42
Reporting
Should be introduced impact report You will be sure that the customer understands real
deadline of the project
www.ciklum.net 43
Project finishing
4. Finishing Acceptance Maintenance Experience sharing
www.ciklum.net 44
Acceptance
Should be defined acceptance criteria The customer should have restricted time for acceptance Should be defined responsible persons from customer
side
www.ciklum.net 45
Maintenance
Right time for a maintenance proposal Do you want additional benefit? Organize resources in the
most effective way! Propose a few options of reaction time and level of
responsibility Jira
www.ciklum.net 46
Save knowledge
The risks will be reviewed (what happened/what not) Update internal knowledge base Will be defined and shared the best practices What components of the project could be reused in
another projects
www.ciklum.net 47
Bonus
SCRUM+Fixed cost=own experience
www.ciklum.net 48
What works?
Sprint Daily scrum Sprint planning Sprint review Retrospective Product Owner Should be introduced proxy
PO ScrumMaster Product backlog
www.ciklum.net 49
What works?
Sprint backlog Burn down Planning Poker Story points Definition of Done Velocity
www.ciklum.net 50
More information here…
www.ciklum.net 51
We would be happy toanswer any of yourQuestions?