Perform Configuration Audits

(Activity) for Tier: Release

PURPOSE

Conducting physical configuration audits confirms the completeness, correctness, and consistency of our baselines (I.e. approved versions of work products). The objective is to increase customer satisfaction and stakeholder acceptance, by ensuring that we deliver the agreed-on and correct versions of the work products (E.g. code, data files, plans, documentation, server software/hardware, equipment, etc.)

WHEN

When a build is ready for deployment to target customer environments.

PARTICIPATING ROLES

• ACCOUNTABLE

  • Release Manager

• RESPONSIBLE

  • Release Manager

INPUTS

• Build
• Release Plan
• Test Results
• Deployment Plan
• Code Review Results
• Test Analysis Results

ENTRY CRITERIA

Baselines are configured and available to support the Deployment Plan.

SUB-ACTIVITIES

1. Ensure Integrity of all Work Products being deployed

   • Ensure that all code was checked for relevance prior to being committed, results have been documented (per the Code Review activity), and any concerns or issues were remediated for the version of the Build.
   • Ensure build has been functionally verified, and test results have been documented (per the Analyze Test Results activity), and any concerns or issues were remediated for the version of the Build.
   • Ensure documented deployment or installation instructions are ready for use (per the Plan Deployment activity), and any concerns or issues were remediated to successfully deploy the version of the Build.
   • Ensure Contract deliverable documentation has been reviewed and approved for this deployment (per the Prepare Contract Deliverable Documentation activity), and any concerns or issues were remediated for the version of the Build.
   • Ensure Environments, as identified in the projects Product Integration Plan (PIP), are configured and available to support deployment (per the Verify Product Integration Plan and Environments activity) for the version of the Build.

2. Triage any concerns or issues and decide on the corrective action.

   • Consult with relevant stakeholders from the following list:

     • Project Manager: For actions needed regarding the Release Plan.
     • Lead Developer or Development Manager: For action items regarding Architecture, technology, data and code reviews.
     • Operations Manager: For actions items regarding Environments.
     • Test Manager: For action items regarding the Functional Verification Results.
     • User Education Specialist: For action items regarding Contract Deliverable Documentation.
     • Release Manager: For action items regarding the Deployment or Installation instructions.

   • Capture action items and create ADO work items as necessary.

3. Document results within the deployment plan

   • Record configuration audit results or concerns within the plan.

Note

Azure DevOps work item discussion field notes, and links (including hyperlinks) may constitute documentation of results.

OUTPUTS

• Configuration Audit Results

EXIT CRITERIA

Configuration Audit Results have been documented and recommended actions, if any, have been captured.

NEXT ACTIVITY

• Deploy Product
• Deliver Contract Deliverable Documentation

SEE ALSO

Process Guidance Version: 10.4