Change
Change
The Change theme tests controlled handling of issues and changes, plus configuration management. An issue is a concern, problem, or off-specification; a request for change is a proposed modification to baselined products. The change control approach defines how issues are captured, assessed, decided, and implemented. The issue register records issues, owners, impact assessment, decisions, and status. A change authority decides changes within delegated limits; a change budget funds approved changes. Configuration management identifies configuration items, controls changes to them, records status, and verifies integrity. Baselines are frozen versions; a product status account reports the state of products.
Worked example
A request asks for an extra dashboard report after the requirements baseline is approved. The Project Manager logs it in the issue register and assesses cost, time, quality, and risk. The report adds two days and 3,000 pounds, within the Project Manager's delegated change authority and the change budget. The Project Manager approves it, updates the product description and configuration item record, and records the new baseline version. The change is included in the next highlight report. Reasoning: impact assessment and delegated authority prevent uncontrolled scope creep.
Traps
Do not let changes be implemented informally because they are small. Do not confuse an off-specification with a request for change. Do not treat configuration management as mere filing; it controls baselines and status. Do not exceed delegated change authority without escalation. Do not forget to update the issue register after a decision.