Software Control Board (SCB) Candidate List Form

Instructions for Software Control Board (SCB) Candidate List Form

The Project Software Manager completes all sections of the SCB Candidate List Form. The Project Software Manager enters the following information for each Software Change Request (SCR) and Request for Deviation/Waiver to be considered by the SCB.

[1] Request: Assigned unique number.

[2] Criticality No.: Criticality Number from the SCR. If not an SCR, leave blank.

[3] Resp. Group: Team(s), work group(s), or individuals who will be impacted by the request.

[4] Products Impacted: Work Breakdown Structure (WBS) numbers of the software products that would be impacted.

[5] Impact: If the request is for an SCR, the impact as staff weeks or hours. If not an SCR, leave blank.

[6] Risk: The Risk of Implementation level from the SCR. If not an SCR, leave blank.

[7] Cost: If the request is for an SCR, the cost to implement the change is entered. If not an SCR, leave blank.

[8] Product Status: The Product Status (e.g., baselined, under development, planned) is entered for the software products that would be impacted.

[9] Action Taken: SCB decision (e.g., approved, disapproved, deferred). This corresponds to Item [6] on the SCR Form or Section C, Item [1] on the Request for Deviation/Waiver Form.

[10] Expected Completion Date: Filled in during the SCB meeting only if the request is approved. Date the approved SCR will be implemented in the software products. It corresponds to Section B, Item [1] on the SCR Form.

[11] Open/Close: Documents whether the SCR was implemented. If the request is for a deviation or waiver, and the request is sent to a higher board, the request should stay "open" until higher level approval is received. If not, leave blank.

Note: Prior to the SCB meeting, the Project Software Manger may wish to sort the requests by Resp. Group, and add the total additional workload, the expected available hours for that group, and the cost per group from approving the requests. This could be shown directly on the form as shown in the example in activity C2.6 Hold SCB Meeting in the Software Configuration Management Volume of this Guidebook.