PROCESS PRODUCT PROJECT

• Defect Turnaround • Mean time between • Requirements

Time failures (MTBF) without Test
Coverage
• Time to Test • Mean time to
recover (MTTR) • Requirement
• Defect Backlog Stability Index
• Defect Injection • Test Coverage • Requirement
Rate • Endpoint incidents Defect Density
• Effect of testing • Net Promoter Score • Budget variance
changes (NPS) • Schedule Variance
• MTTR (mean time • Defects found by • Test Effectiveness
to repair) Customer Using Team
Assessment
Stakeholder Reporting Requirements Report/Metric

Sponsor/H.A. Monthly Project Summary,

Budget,
Earned Value
H.A. Monthly Earned Value,
Project Implications,
Documentation
Project Manager Weekly Project Summary, Budget
Earned Value, Critical Tasks,
Slippage, Milestones,
Budget Overflow
Project Team Weekly Task Assignment List,
Project Timelines
 PI
Probability Impact
Phase Risks Justification Score
All stakeholders not considered This risk can occur due to
at the time of stakeholder incomplete or improper 20% 9 1.8
Conceptualize & Initialize analysis stakeholder analysis
This risk can occur due to
Develop Project Charter Miscellaneous Activities eg: incomplete planning where 50% 4 2
& Plan Travel buffer time is not kept
No buffer considered for
development 65% 6 3.9
Execute and Control and testing activities Incomplete planning
Documentation and transition
not completed as per This risk can occur due to 70% 6 4.2
Close Project expectations improper project management
Stakeholders not happy with Incomplete cost benefit
20% 9 1.8
Evaluate Project success MOV's analysis
Application quality affected
due to This risk can occur due poor 80% 7 5.6
known reduction in estimated efforts planning
Employees availing christmas This is seasonal and can 15% 8 1.2
unknown-known leaves happen each year
unknown-unknown Unexpected production bugs Poor project execution 60% 8 4.8
 Resources
Phases Risk Trigger Owner Response
Required
Known Application quality affected Too many bugs in the PM,Tester Strategy is NA
due to reduction in estimated application during UT Mitigation: Proper
efforts phase Traceability Matrix
and stringent code
review

Scope Scope changes may not be Too many scope changes PM Strategy is NA
processed through change Mitigation: Proper
management change management
process
Unknown - Unexpected production bugs Incident tickets getting PM,BUSINE Strategy is UAT : NA
Unknown raised SS USER Thorough UAT
Close Project Documentation and Users finding difficulties Transition Strategy is Mitigation NA
transition not completed as in using the application Manager : Version control
per expectations documentation

Execute and No buffer considered for Delay in development Project Strategy is Mitigation Additional
Control development and testing Manager : Timeline/Budget developers
and testing activities Negotiation and testers