Project Name IN-PROCESS REVIEW MEETING It is not necessary to generate new viewgraphs for each review. Use of “red-line” mark-ups is encouraged Project Name IN-PROCESS REVIEW MEETING Project Manager: __________________ Date: ___________________

In-Process Review Agenda TOPIC Action Items from Previous Review Project Performance versus Schedule Project Organization Technical Performance Schedule Performance Issues and Concerns Risk Analysis Lessons Learned Concluding Comments The agenda chart provides an overview of the project status along with relevant opinions and details. The basic thought process for this agenda organization is that the project plan has been discussed, evaluated, and approved at the kickoff meeting. The plan, once approved, is the presumed path to success. This review consists of four elements: PLAN, TRACK, ANALYSIS OF VARIANCE (including Issues and Concerns), and REPORT.

Action Items from Previous Review Include all open action items from previous reviews or the Kickoff Review and any closed action items from the last review.

Project Performance Status Trend Technical (Past/Present/Future) Schedule (Past/Present/Future) Cost (Past/Present/Future) Customer Satisfaction (Past/Present/Future) This chart is designed to capture project status in technical, schedule, cost, and customer satisfaction. In the actual report, “Status/Trend” are each replaced by colors: Red, Yellow, Green. “Status” reflects the current condition, “trend” is the expected status at the time of the next review. Color codes are: RED - signifies a significant issue, concern, problem, or failure to meet performance requirements. YELLOW - is a cautionary sign, a potential significant issue. GREEN - indicates things are proceeding according to the plan. Include comments supporting the bullet colors.

Project Organization (example) Project Manager _______________ Contracts _____________ Procurement _____________ QA & Test System Engineer _____________ _______________ Project Controls _____________ Chief System Engineer _______________ Software Engineer Hardware Engineer Integration Test Etc. _____________ _____________ _____________ _____________ _____________ The organization chart allows us to evaluate the experience, training, and responsibility levels of the project team. It also allows us to make some organizational common sense tests: Does QA report outside the project? Is the system engineering function represented? Is there a Project Controls function? Finance? Contracts? Procurement and subcontracts? Are there staffing issues? If so, be specific. What is the issue or the position to be filled? Who has the responsibility for completing the action, and what is the estimated completion date (ECD) for closure? Staffing Need Actionee ECD ACD

Project Schedule Gantt Chart Example A summary Gantt chart should be included in the presentation package showing actual performance against plan. Schedule slips from the plan must be clearly shown.

FOR EACH STEP INCLUDE: ACTION, ACTIONEE, ECD, ACD (WHAT, WHO, WHEN) Issues & Concerns Concern: (provide 2 sentence explanation): ____________________________________ ____________________________________ Resolution Plan: Concerns of the project team regarding the project’s success. These charts, Issues and Concerns, are designed to facilitate the free expression of any significant concerns. State the concern or issue in the top section and then state the resolution steps appropriate to resolve the concern. For each step, identify what the step is, who is responsible for the action, and when the step will be completed (the Estimated Completion Date, or ECD). When the step is completed add the Actual Completion Date (ACD). Leave the ECD so we can determine how close the ACD matches the ECD. For a typical project, the Project Manager might have two to four significant issues or concerns. Members of the project team who may also present (the Chief Engineer, the Software Manager, etc.) may have one or two issues and concerns. Each issue and concern must be listed on a separate page. FOR EACH STEP INCLUDE: ACTION, ACTIONEE, ECD, ACD (WHAT, WHO, WHEN)

Lessons Learned Since Last Review What did we do well? What did we do poorly? Where were we lucky? Where were we unlucky? If we were to do it again what would we do differently? Lessons Learned are an important part of the review and the final project report. Do not include the lessons learned from the previous report. The charts become the input for the lessons learned report required at project completion. Note: Do not include old/previous Lessons Learned on this sheet.

Concluding Comments This chart allows the project team to comment on any topic not already covered in the review.