Change Management

Managing changes to systems and organisations in a systematic way.

Also Known As

• Buffer Management (in TameFlow)
• Change Administration
• Change Control
• Change Handling
• Enabler Stories (in Scaled Agile Framework (SAFe))
• Program Backlog (in Scaled Agile Framework (SAFe))

Related

• Coding
• Integration Testing
• Release Delivery

Addresses / Mitigates

• Operational Risk: Ensures changes are implemented smoothly and systematically.
• Implementation Risk: Avoid bugs from creeping into the system.
• Coordination Risk: Specifically addresses coordinating change in a structured way.

Attendant Risks

• Schedule Risk: Managing changes systematically can introduce delays.
• Process Risk: Change control is a process, and therefore is a source of process risk.

Used By

• Lean Software Development: Lean emphasizes managing changes effectively to ensure continuous improvement and adaptability.
• Scaled Agile Framework (SAFe): SAFe manages change through structured backlogs and regular planning cadences.
• Scrum: Changes are managed through the product backlog and sprint planning.
• TameFlow: Buffer Management detects issues early, enabling proactive change management before problems escalate.

Description

"Change management (sometimes abbreviated as CM) is a collective term for all approaches to prepare, support, and help individuals, teams, and organizations in making organizational change." - Change management, Wikipedia

Change Management in software development involves managing changes to the software in a systematic way. This includes planning, implementing, and monitoring changes to ensure they are executed smoothly and do not negatively impact the project's goals and timelines. Effective change management helps in minimizing disruptions and maintaining the quality and stability of the software.

Variations

Change Management Type	Description	Reference
Change Advisory Board	A formal body that reviews and approves significant changes.	Change Advisory Board, Wikipedia
Emergency Change	Expedited process for urgent changes that can't wait for normal approval cycles.	ITIL Change Management
Standard Change	Pre-approved, low-risk changes that follow a documented procedure.	ITIL, Wikipedia

Used By

Lean Software Development

An Agile software development methodology that emphasizes eliminating waste, building quality in, creating knowledge, deferring commitment, delivering fast, respecting people, and optimizing the whole.

Why: Lean emphasizes managing changes effectively to ensure continuous improvement and adaptability.

Scaled Agile Framework (SAFe)

A set of organization and workflow patterns for scaling lean and agile practices across large enterprises.

Why: SAFe manages change through structured backlogs and regular planning cadences.

Uses:

• Program Backlog
• Enabler Stories

Scrum

An Agile framework for managing and completing complex projects.

Why: Changes are managed through the product backlog and sprint planning.

TameFlow

A management approach for knowledge work that integrates Theory of Constraints, Kanban, and Agile principles to optimize the flow of work, information, and value.

Why: Buffer Management detects issues early, enabling proactive change management before problems escalate.

Uses:

• Buffer Management