Use iterative process Requirements (1.1) The requirements 2 2 4 2 with project have not been clearly stakeholders to provide specified clarification of requirements as they fit into overall business (1.2) The requirements 2 3 6 2 objectives specified do not match Use detailed design the customer's needs documents with Agency sign-off Risk Significance Risk Mitigation Actions Level Area Risk Event Description Risk of Factor Probability Impact Control ( P x I ) Communicate status Schedule (2.1) The schedule 2 3 6 2 reports on a regular provide enough doesn’t basis time to complete the project Put aggressive project tracking and monitoring in place (2.2)The schedule 1 2 2 1 Increase allotted all of the resource allocation doesn’t list activities and tasks Re-baseline project required schedule to accurately account for task and (2.3) The schedule 2 2 4 2 activity dependencies provide accurate doesn’t Re-baseline project dependencies schedule to include activities and tasks required Follow established Budget (3.1) The project change management exceeds the budget 1 3 3 3 procedures allocated Follow 1.1 and 1.2 (Requirements Risk Mitigation) Use a deliverable based contract Ensure the project Deliverables (4.1) The deliverables 2 3 6 2 specifications are required by the project formally approved and are not clearly defined signed off on Distribute scope statements to all (4.2) Clear quality 2 2 4 2 stakeholders for criteria for each confirmation deliverable have not Create clearly defined been defined
Requirements (1.1) The requirements have not been clearly specified 2 2 4 2 Use iterative process with project stakeholders to provide clarification of requirements as they fit into overall business objectives Use detailed design documents with Agency sign-off (1.2) The requirements specified do not match the customer's needs 2 3 6 2 Area Risk Event Description Risk Significance Risk Mitigation Actions Probability Impact Risk Factor ( P x I ) Level of Control Schedule (2.1) The schedule doesn’t provide enough time to complete the project 2 3 6 2 Communicate status reports on a regular basis Put aggressive project tracking and monitoring in place Increase allotted resource allocation Re-baseline project schedule to accurately account for task and activity dependencies Re-baseline project schedule to include activities and tasks required (2.2)The schedule doesn’t list all of the activities and tasks required 1 2 2 1 (2.3) The schedule doesn’t provide accurate dependencies 2 2 4 2 Budget (3.1) The project exceeds the budget allocated 1 3 3 3 Follow established change management procedures Follow 1.1 and 1.2 (Requirements Risk Mitigation) Use a deliverable based contract Deliverables (4.1) The deliverables required by the project are not clearly defined 2 3 6 2 Ensure the project specifications are formally approved and signed off on Distribute scope statements to all stakeholders for confirmation Create clearly defined (4.2) Clear quality criteria for each deliverable have not been defined 2 2 4 2
PMPLLLP2009.docx