Previous
¶ Change Control & Management
¶ What it is
Change control is managing the necessary changes to a project/product over time. All changes must be recorded and accessed before they get implemented. Once approved, the change should be put into the Scrum process and tracked as a routine task.
¶ Why it is useful
As the resources are usually limited, one must assess and prioritise all the change requests to ensure the most critical tasks that match the business values are completed in time, especially when SLA resolution time is pressing.
¶ When to use it
In project management, change control is needed from the very beginning of a project until the project's closure. When receiving change requests, the persons in charge should strictly follow the predefined.
¶ How is it done
- Define the changing scope: Project scope, timelines, and team responsibilities are the factors to consider when a change needs to be assessed. The change type and size are also to be primarily evaluated before submission.
- Evaluate the potential impact: Elements to evaluate include a timeline, teams, tools, etc.
- Submit the change request to the CCC: The CCC (Change Control Committee) is a group of stakeholders with a say on the project/product. They are the ones to discuss and assess if the change should be approved and put into the project plan.
- Adjust the project plan: When the change request is approved, the project manager should reflect the change on the project plan.
- Communicate and implement the approved changes: The project manager should communicate the change to the affected team members, and this process must be transparent enough to avoid miscommunication.
¶ Do's & Don't
Do's
- Establish a Change Control Committee that governs change. This might feel like overhead, but it will save time and rework.
- Document change religiously - with a trace, new team members will be able to onboard.
¶ Tools needed
¶ Example
