Overview
During a software project, it may be necessary to deviate from the organization’s standard software process. When this occurs, a Request for Deviation/Waiver (see Appendix C) is submitted to the software engineering process group (SEPG) describing the requested deviation/waiver and rationale. The SEPG determines the request’s merit based on project documentation, and accepts or rejects the request.
Roles and Responsibilities
The SEPG members disposition the Request for Deviation/Waiver.
The project software manager requesting the deviation presents the SEPG with sufficient information and documentation to allow the members to properly disposition the request.
Controls
See parent activity 4.1 Identify And Test Process Improvements.
Inputs
Request for Deviation/Waiver submitted by the software project requesting a deviation from the organization’s standard software process.
Project documentation submitted by the software project to support the deviation request (e.g., software project schedules, funding documentation).
The organization’s standard software process from which the project is requesting a deviation.
Procedures
The following steps are sequentially performed:
1) The SEPG chairperson receives a Request for Deviation/Waiver, and sends a copy to each SEPG member.
2) The SEPG chairperson assigns one or more reviewers (i.e., other SEPG members) to analyze the request and establish a date for completing it.
3) The reviewer(s) analyzes the request against the organization’s standard software process, determining the request’s impact on any on-going improvement studies, baselining, and reuse efforts, as well as the expected effect on the system and software products developed by the project. The project software manager or other project personnel should be consulted, and any related documentation from project personnel should be reviewed. During this analysis, the reviewer(s) should identify what project metrics, if any, will be impacted by the requested deviation.
4) The reviewer(s) documents the findings on the Request for Deviation/Waiver in accordance with the organizational-level Configuration Management (CM) Plan (CMP), and notifies the SEPG chairperson that the review is complete.
5) The SEPG chairperson reviews the analysis to determine the reasons for and validity of the request, and its impact on the organizational and project products (e.g., quality, schedule, cost), on-going process studies, and baselining efforts. The request and accompanying analysis then is submitted to the SEPG for a vote to accept or reject. It is recommended that the analysis and request be electronically routed because the SEPG may be loosely organized with members working on other projects. The SEPG members should base their votes on what is best for the project. The project software manager and SEPG chairperson then are notified of the SEPG’s decision. If the request is granted, the SEPG completes a Metric Variance Notification form (see Appendix C) stating which software project metrics will by impacted by the change. The completed form is placed in the organization’s asset library (see activity 4.2.1 Maintain Asset Library).
6) If the SEPG chairperson believes the requested deviation may have merit for several current or future projects, the SEPG chairperson identifies the requested deviation as a potential modification to the organization’s standard software process (see activity 4.1.3 Determine Improvement Goals And Potential Changes).
Outputs
The dispositioned deviation(s)/waiver(s) returned to the project software manager.
The Metric Variance Notification form submitted to the SEPG member(s) maintaining the organization’s software baseline.