Change & Issue Management

2. Change & Issue Management during Project Definition Stage
3. Change & Issue Management during Project Management & Control Stage

Frequently Asked Questions

What does the business expect and how is that expectation supported by this technique?

The business expects that issues and changes are properly managed during the life of a project. Effective change and issue management is a key element of project management.

Uncontrolled changes and issues can lead to escalation of project costs, dissatisfaction among users, lower quality end products, and/or significant delays in the project schedule. The most significant impact of uncontrolled change requests is an alteration of project scope without a thorough analysis of the related impacts.

An increased project scope will generally increase project duration and/or lower the overall quality levels as project team members attempt to meet pre-established target dates. A decrease in project scope may result in dissatisfied users as the full functionality and potential benefits they anticipate may not be realised.

This Execution Plan provides instructions for creating and implementing a change and issue resolution process.

How will this technique support the business objectives and realise the anticipated potential business benefits?    

When change requests and issues are properly managed, changes to scope are reduced. Effective change and issue management can reduce the risk of project cost and time overruns thereby meeting client delivery expectations.

What will the proposed deliverable(s) do and look like?

  • Detailed change control procedures tailored for the specific project size, characteristics and environment.
  • Detailed issue resolution procedures tailored for the specific project size, characteristics and environment.
  • Clearly defined roles and responsibilities for all areas of change control and issue resolution.
  • Hard copy and/or electronic copies of the approved detailed-level procedures for change control and issue resolution.
  • Hard copy and/or electronic forms for submission of change requests and issues.
  • Hard copy and/or electronic logs for recording, tracking and communication information pertaining to change requests and project issues.
  • Databases, or other appropriate means, for storing information pertaining to change requests and project issues.
  • Plan for communicating change control and issue resolution procedures to the project team.
  • Training/presentation material.

How long does this technique generally take?          

The time required to produce the deliverables depends on the size, scope and complexity of the project.

It may take 2-5 days to produce the deliverables in Phase 1, Project Definition.

Who should participate in this technique?

The Project Manager and the core team are responsible for developing the change and issue management processes and procedures during the Project Definition Phase.

The Project Manager or the Project Office will be responsible for managing the process through the life of the project. If it is delegated to the Project Office, the ultimate responsibility still remains with the Project Manager.

What materials are required to employ this technique?

  • Sample change control procedures, forms and reports.
  • Sample issue resolution procedures, forms and reports.

What are the potential technique-related issues / financial risks?

If issue and change control processes are not implemented, project costs can escalate, users may become dissatisfied, the quality of the deliverables may be jeopardized and the project schedule will be impacted.

Processing...