4 Reviewing Have the various meetings, the purpose, context, frequency, and 4.1 participants been defined and communicated? 4.2 What are the defined meeting materials? Are the meetings set up to have assigned note-takers that will 4.3 add actions/issues to the issue list? 5 Issue Management 5.1 Is an issues-management process documented and filed? Is this process communicated to the customer and team 5.2 members? 5.3 Will an issue form be in use? Will all project issues be unconditionally tracked through the 5.4 issue-resolution process? Will all tasks resulting from issues be entered into the Issues Log 5.5 and tracked? Are there processes for unresolved issues to be escalated and 5.6 resolved within a reasonable timeframe? 6 Change Control 6.1 Will there be a change control process in place? 6.2 Is the change control process documented and on file? Will this process be communicated to the customer and Project 6.3 Team? 6.4 Will there be a change request form in use? Will all project deliverables and software configuration 6.5 management be changed only through the change control process? Will all change requests be unconditionally tracked through this 6.6 process? 6.7 Will all change requests and current status be logged? Will all tasks resulting from approved changes be entered into the 6.8 Project Plan and tracked through the plan? 6.9 Will new change requests be acknowledged in a timely manner? 7 Risk Management Will all project risks be managed according to the project’s risk 7.1 management process? Will the Risk Response Plan be updated on a regular and frequent 7.2 basis? Will the risk status be reported to management on a regular and 7.3 frequent basis? 7.4 Will the risk documents be filed? Will there be documented contingency plans for the top five to 7.5 10 risks? Will the preventive plans for the top five risks be identified, 7.6 included in the Project Plan, and implemented?
4 Reviewing 4.1 Have the various meetings, the purpose, context, frequency, and participants been defined and communicated? 4.2 What are the defined meeting materials? 4.3 Are the meetings set up to have assigned note-takers that will add actions/issues to the issue list? 5 Issue Management 5.1 Is an issues-management process documented and filed? 5.2 Is this process communicated to the customer and team members? 5.3 Will an issue form be in use? 5.4 Will all project issues be unconditionally tracked through the issue-resolution process? 5.5 Will all tasks resulting from issues be entered into the Issues Log and tracked? 5.6 Are there processes for unresolved issues to be escalated and resolved within a reasonable timeframe? 6 Change Control 6.1 Will there be a change control process in place? 6.2 Is the change control process documented and on file? 6.3 Will this process be communicated to the customer and Project Team? 6.4 Will there be a change request form in use? 6.5 Will all project deliverables and software configuration management be changed only through the change control process? 6.6 Will all change requests be unconditionally tracked through this process? 6.7 Will all change requests and current status be logged? 6.8 Will all tasks resulting from approved changes be entered into the Project Plan and tracked through the plan? 6.9 Will new change requests be acknowledged in a timely manner? 7 Risk Management 7.1 Will all project risks be managed according to the project’s risk management process? 7.2 Will the Risk Response Plan be updated on a regular and frequent basis? 7.3 Will the risk status be reported to management on a regular and frequent basis? 7.4 Will the risk documents be filed? 7.5 Will there be documented contingency plans for the top five to 10 risks? 7.6 Will the preventive plans for the top five risks be identified, included in the Project Plan, and implemented?
FM-PC-20%20%20Planning%20Risk%20Evaluation%20Checklist%20Template.docx