Overview
In this activity, the software project plans are updated based upon actual software project results, changes to the project plan, and risk mitigation activities. The plans are modified in accordance with the project’s Software Configuration Management (SCM) Plan (SCMP) (see Appendix E).
Roles and Responsibilities
The project software manger has overall responsibility for updating and maintaining all of the software project’s plans.
The software engineering manager is responsible for updating the Software Development Plan (SDP) (see Appendix E).
The software test manager is responsible for updating the Software Test Plan (STP) (see Appendix E).
The SCM manager is responsible for updating the SCMP.
Controls
The SCMP which documents what products will be kept under configuration control and the process to be followed when updating them.
Inputs
The software project plans to be updated.
The documented risks which have been identified and documented on the Risk Information Form(s) (see Appendix C).
Software metric reports from the software engineering process group (SEPG).
Procedures
When updating project plans, the project software manager, in coordination with the SCM manager, must determine what level of control should be kept on the software project plans. Normally, updates to software project schedule(s) showing work accomplished or minor plan changes do not need to go through the entire software change management process (i.e., writing Software Change Requests (SCR) (see Appendix C) (see 2.2.4 Request Software Product Change),and submitting these to the Software Control Board). This sort of minor update should be treated by the SCM manager as a product revision. Updates requiring changes in multiple plans (e.g., a change in the software engineering environment may cause changes in the software project training), the scope of the work to be performed (e.g, additional software to be developed) or impact the development or testing approach should go through the formal change process to verify all plan updates are coordinated and completed.
1) The project software manager should update the software project schedule (see activity 1.1.1.1.5 Develop Software Schedule) at least monthly, based upon the software project’s progress, completed milestones as documented in the software metric reports, and review of the cost estimates based upon the updated schedule and cost metric information (see activities 1.1.1.1.4 Perform Cost Estimating and 1.2.1.3 Analyze Software Project Metrics). Potential problems with meeting project-level cost or schedule constraints should be brought to the attention of the project manager as early as possible.
2) The project software manager, software test manager, software engineering manager, and SCM manager should jointly review the documented risks and the proposed risk mitigation strategies as documented on the Risk Information Form(s) (Appendix C). Risk mitigation approaches or risks that are realized should be addressed in the updated plans. These mitigation strategies and contingency plans often involve additional training, adding personnel or resources to the project, or using new methods or processes. In the case of additional training or resources, the relevant plans should be formally updated through the change control process as detailed in the Configuration Control section of the SCMP because these may impact the SDP (in terms of schedule and cost) as well as the Software Project Training Plan. In the case of trying new processes or methods that deviate from the organization’s standard software process to mitigate risks, the project software manager should submit a Request for Deviation/Waiver (see Appendix C to the SEPG for approval (see 2.2.1 Request Deviation/Waiver).
3) The updated plans are approved by the project software manager and submitted to be placed under software configuration control in accordance with the project’s SCMP.
Outputs
The updated software plans which have been placed under software configuration control.