Configuration Audit Checklist

Version 1.1 Date of Release

Author(s) Reviewer

Classification Internal Approved By

Document Change History

Rev Date Editor Section Nature of Change
1.1 Pulkit Kumar NA First Version
dit Checklist

f Change
 Configuration Audit Checklist

Project

Auditee

Internal Auditor

Audit Date Time Taken (HH.MM)

n Audit Checklist
 FODE
Configuration Audit Checklist
Project Name :
Project Manager:
Business Unit

S. No.
1

4
5

9
10

11

12
13
14
15
16

17

18

19
 FODE
Configuration Audit Checklist
Audit Date:
Audited by:
Audit effort:

Checkpoints Status
Are all project related documents reviewed, approved and available under appropriate folder in
configuration library, if prepared?
Are all the test results passed and defects closed, for all delivered work requests?
Are Release Notes and Run Books prepared and committed in SVN? Verify all appropriate
details are filled and are correct.
Verify last audit action points have been closed, If Applicable.
Is the Configuration Management plan reviewed and approved by relevant stakeholders?
Are all CI's & Non-CI's identified in accordance of project scope, receivables and deliverables?

Is SVN access matrix sheet up-to-date and implemented correctly against current project
resource list.
Are revision history maintained for all changes made to the documents in SVN? Verify proper
check-in comments are provided.
Are CI's Linked to proper JIRA Id in Comments?
Is everyone using PL/SQL IDE for all SCM activities?
Are relevant work-products baselined/Tagged? Verify the baseline processes for SDLC
artifacts.
Is Branching Strategy as per process?
Is Merging followed religiously?
Are all Scripts re-executable?
Are folders in SVN created as per process?
Is Pre/Post Wrapper Script updated as per process?
Are updated artifacts checked-in back to the configuration library, once any defect(s) are fixed?
Check the artifact, version, check-in date and comments appropriately.
Are backup/ restoration activities carried out on a monthly basis? Check and verify the logs.
Is Configuration Status Report prepared and shared with relevant stakeholders on monthly
basis? Verify all sections are duly filled.
Comments
 Configuration Audit Report
Product Name :  FODE

Project Manager/Architect: Ritu Sharma/Sanjeet Bose

Audit Team members :

Audit Date :

Objective of the Audit : 

Release# SVN Repository Issues/Deviations Owner

Process conformance / deviations : (Adherence to the process - checklist output)

Additional comments : 
 Remarks

klist output)
 FODE
Configuration Audit Checklist
Purpose

Physical Configuration Audit (PCA)

Intended use of PCA check list

 FODE
Configuration Audit Checklist
This is the Configuration Audit check list for PCA which will help in auditing the Physical as well as Functional Configuration
audit

Configuration Management (CM) verifies that what ever you have built conforms to the technical documentation that defines the
build. It means CM must compare the configuration of the as-built product to the design documentation of the product. For
example, CM looks at the list of all the configuration items (versions etc.) in the as-built product and compares that list to the lis
of what is supposed to be in the project.

To be used when conducting a Physical configuration audit for a project build or release, or for auditing a product under
maintenance or CR's and Development Projects