18. 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
18
19. 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”
19
20. Risks
List of risks:
Description
Probability
Influence
Mitigation plan
Trigger
Migration plan
20
21. Risk handling
Share with the customer
Include in price
21
22. How to include risk in the price
Calculated risk cost (Rc)
Probability (P. From 0 to 1)
Risk reserve (Rr)
Rr=Rc*P
22
24. Project duration/team
Split project on sub projects (as well sub-contracts)
Build small teams
24
25. People involving
Involve on pre-sale stage people who will take a part in
the project implementation
25
26. 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.
26
27. Commercial correction
Effort -> $
Stomach feeling
Consulting with sales department
Is it possible with final amount to finish the project?
27
35. Risks
Plan of risks analyzing
Update involved people (customer, sales, supervisor etc)
35
36. Small changes
You have a buffer for them
Efforts of small changes must be controlled
Customer always needs much more
Use batching strategy
36
37. Change requests
Definition of CR must be created and agreed
Don’t show real spent effort for CR (common JIRA)
Strategies:
Include
Postpone
37
38. Including strategy
The customer will be noticed concerning duration and
budget changes before implementation
38
39. Important notice
Effort spent for CR clarification will be included in final
estimation
39
40. Postpone
CR’s cold be collected and realized as a minor release
It is bad idea to implement CR’s separately
40
45. Acceptance
Should be defined acceptance criteria
The customer should have restricted time for acceptance
Should be defined responsible persons from customer
side
45
46. 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
46
47. 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
47