PMI-SP Exam Prep Course

Username: Index | Next

In Time: 10/9/2014

Establish project schedule configuration Management policies and

procedures

Introduction:

A Configuration management system with integrated change control provides a

standardized, effective, and efficient way to centrally manage approved changes
and baselines within a project. Configuration control is focused on the specification
of both the deliverables and the processes while change control is focused on
identifying, documenting and controlling changes to the project and the product
Logout is baselines. Customer or sponsor approval may be required for certain change

study Session. Improper requests after Change Control Board approval, unless they are part of the CCB.
logouts are not counted
towards contact hours.
Some of the configuration management activities included in the integrated
change control process are as follows:

Configuration Identification - Selection and identification of a configuration

item provides the basis for which product configuration is defined and verified,
products and documents are labeled, changes are managed, and accountability is
maintained.

Configuration Status Accounting - Information is recorded and reported as to

when appropriate data about the configuration item should be provided. This
information includes a listing of approved configuration identification, status of
Ads by alnaddy
proposed changes to the configuration, and the implementation status of approved
changes.

Configuration Verification and Audit - Configuration verification and

configuration audits ensure the composition of a project's configuration items is
correct and that corresponding changes are registered, assessed, approved,
tracked, and correctly implemented. This ensures the functional requirements
defined in the configuration documentation have been met.

Factors influencing Schedule Configuration Management:

Project Schedule Configuration is driven by the Organizational Policies,

Organizational Process assets and the environmental factors which can enhance
the management of Schedule configuration.
1. Enterprise Environmental Factors

The following enterprise environmental factor can influence the Schedule

Configuration Policies:
Project management information system -- an automated tool which could include

Scheduling software tool,

Configuration management system To systematically track the

configurable items.

Information collection and distribution system for Storage and retrieval.

Web interfaces to other online automated systems to leverage existing

capabilities of the organization.

2. Organizational Process Assets

The organizational process assets that can influence the Configuration

Management includes, but are not limited to:

Schedule Change control procedures, including the steps by which official

company standards, policies, plans, and other project documents will be
modified, and how any changes will be approved, validated, and
implemented;

Procedures for approving and issuing Schedule change authorizations;

Process measurement database used to collect and make available Schedule

measurement data on processes and products;

Project files (e.g., scope, cost, schedule and, performance measurement

baselines, project calendars, project schedule network diagrams, risk
registers, planned response actions, and defined risk impact); and

Schedule Configuration management knowledge base containing the

versions and baselines of all official company standards, policies, procedures,
and any project documents.

3. Expert Inputs

In addition to the project management team's expert judgment, stakeholders may

be asked to provide their expertise and may be asked to sit on the change control
board. Such judgment and expertise is applied to any technical and management
details during this process and may be provided by various sources, for example:

Consultants,
Stakeholders, including customers or sponsors,
Professional and technical associations,
 Industry groups,
Subject matter experts, and
Project management office (PMO).

Establishing Configuration Management Policies and Procedures:

The Strategy provides direction to management of the project to support the

business and technical objectives which are constrained by Time.

The schedule Configuration management Policy and procedures are part of overall
Configuration Management policy consisting of processes and procedures for
identification, assessment, approval, implementation, test and release status
accounting and auditing are set forth in the policy document.

1) Configuration definition standard:

Configuration definition standard: The standard defines the configurations on this

project and how configuration items will be identified and managed. This standard
will be updated as needed during the project to keep it current. It will be used to
provide the information needed by the Configuration Manager when coordinating
the content and status of the Configuration management repository with the rest
of the project team.

2) Documenting the control procedure:

This procedure specifies how documents related to schedule of the Project will be
created, distributed, and revised. This procedure applies to all documents which
are produced or received by the project.

1. Create Draft of Controlled Document

2. Review, Revise, and Issue Document
3. Maintain Controlled Documents
4. Distribute Updated Documents
5. Create and Distribute Uncontrolled Documents

3) Documenting the control standard:

The purpose of this standard is to define how to identify, store, and maintain
documents for the Project.

This standard applies to each member of the project and will be followed when
creating, revising, and using project documentation.

A. Project Library
All documentation prepared in reference to this project will be stored in the Project
Library. The Project Library is intended to achieve the following objectives:
Ensure that all project documents are readily available to all project staff

log and store copies of changes to deliverable documents, and provide

 current and previous versions of documents on demand

hold reference materials, including quality and standards documents

maintain administrative information needed by the project such as logistical,

reporting, and orientation materials

store working papers produced in the day to day operation of the project

B. Controlled Documents

Controlled documents are any documents on the project which represent project
deliverables or are subject to review and revision. The standard front matter for a
controlled document includes a cover page, change record, reviewer list, and
distribution list.

C. Uncontrolled Documents
Uncontrolled documents not requiring review or revision, such as meeting minutes
or memos, require fewer components and do not require formal distribution.
However, a copy will always be retained in the Project Library. The standard front
matter for an uncontrolled document includes a cover page.

4) Configuration control procedure

The purpose of this procedure is to specify how configuration items on the Project
will be created, tracked, revised, and referenced.

This procedure applies to all items, including software components, documentation,

data files, and records, which represent or are themselves products of the project
which contribute to project deliverables. In addition, this procedure applies to all
items received by the project which are used to produce project deliverables or
manage project tasks.

1. Create New Configuration Items

Configuration items are created by tasks in the project

work plan which produce deliverables, or from receivables
provided to the project. Item types which are to be
controlled and their inter-relationships will be defined in
the Configuration Definition prior to invoking this
procedure.

2. Control Versions
3. Provide Versions for Reference
4. Promote Versions
5. Manage Configurations

5) Release management procedure:

The purpose of this procedure is to provide general instructions on how releases

 will be constructed and delivered to designated project locations, or to the client,
in an arranged format or medium.

Over the course of this project, a variety of types of releases will be produced and
delivered. The various types of releases and their purposes are described in the
project Configuration Definition standard. Detailed instructions for producing
specific types of releases will be documented as attachments to this procedure.

1. Plan Release
2. Construct Release
3. Deliver Release
4. Secure Client Receipt

Index | Next

PMI-SP, PMBOK are registered marks of the Project Management Institute, Inc.
2014 International Institute of Project Management, Chennai, India
All rights reserved
This page is best viewed in MSIE 5.0 and above