Overview
Throughout the course of the project, the project software manager will be asked to participate in project-level reviews. These reviews will vary between projects. In this activity, the general review process is outlined. For information on the various reviews, see Attachment II of this volume.
Roles and Responsibilities
The permanent secretary is responsible for scheduling in-house reviews, distributing all review notifications, documenting the reviews, and distributing review minutes.
The permanent chairperson serves as the chairperson for the review, appoints the panel members and permanent secretary, coordinates the agenda with the project manager, and manages the review.
Panel members are responsible for reviewing preparation material, and committing time for the full review period.
The project manager is responsible for requesting reviews or review waivers; ensuring that proper subsystem peer reviews are being held; scheduling contractor reviews; preparing and distributing review material; notifying NASA Headquarters personnel; developing agendas with the review chairperson; preparing and distributing panel preparation material; leading the project team in preparing for the review; ensuring the suitability of allotted times; ensuring timely responses to requests for action (RFA); and keeping the minutes, material, and RFAs from the reviews on file.
The project software manager is responsible for providing material to the project manager and may be asked to present this material at the review.
Controls
Management of Major System Programs and Projects [NHB 7120.5], NASA Headquarters, Washington, D.C., November 8, 1993. This handbook "establishes the detailed policies and processes for implementing NMI 7120.4, ‘Management of Major System Programs and Projects.’ " NHB 7120.5 specifies the following six major project review for major system programs and projects:
- System Requirements Review (SRR).
- Preliminary Design Review (PDR).
- Critical Design Review (CDR).
- System Acceptance Review (SAR).
- Flight Readiness Review (FRR).
- Operational Readiness Review (ORR).
Langley Management Instruction (LMI) 7120.1 establishes the LaRC (Langley Research Center) Flight Projects and Experiments Review Program. LMI 7120.1 specifies the following eight major project reviews for the LaRC Flight Projects and Experiments:
1. Spaceflight Experiments Initiatives Review (SEIR).
2. System Requirements Review (SRR).
3. Preliminary Design Review (PDR).
4. Critical Design Review (CDR).
5. System Acceptance Review (SAR).
6. Flight Readiness Review (FRR).
7. Mission Operations Review (MOR) (which may be a subreview of the FRR).
8. Lessons Learned Review (LLR).
Inputs
Managerial and technical slides and project documentation for review.
Procedures
1) The project manager contacts the permanent chairperson to request a desired review date at least two months in advance. A tentative agenda with allotted times should accompany this request.
2) The permanent chairperson notifies participants of a review by a letter that is distributed by the permanent secretary. The letter includes the: review objective; date, time, place of the review; panel members for the review; and the tentative agenda with allotted times.
3) The project manager distributes advance review materials to all panel members at least 10 working days prior to the scheduled review date.
4) The project manager (supported by the project software manager and managers from other disciplines) presents the materials at the review. The panel members review the materials and participate in the review by asking pertinent questions. For a summary of the purpose and materials covered in the project reviews, see Attachment II, LMI 7120.1, and NHB 7120.5. During the review, RFAs are documented by attendees to request further information and/or document issues not adequately addressed at the review. Due dates are assigned to the RFAs. The project manager receives and responds to the RFAs. The project manager is responsible for ensuring that RFAs are closed by their due dates. The closures of the RFAs are normally covered at the next review.
5) The permanent secretary distributes the minutes and RFAs to the panel members, appropriate management officials, review attendees, and the Institutional Support Branch, Logistics Management Division, within 10 working days after the review is complete.
6) The project manager, together with the appropriate discipline managers (including software), work to resolve the RFAs. The resolution of these may result in writing Configuration Change Requests (CCR) (see Appendix C) to change system-level products.
Outputs
CCRs which request changes in system-level products.