Change Management
Also Known As
- Change Administration
- Change Control
- Change Handling
Related
Addresses / Mitigates
- Operational Risk: Ensures changes are implemented smoothly and systematically.
- Implementation Risk: Avoid bugs from creeping into the system.
- Coordination Risk: Controls the impact of changes on other project activities.
Attendant Risks
- Schedule Risk: Managing changes systematically can introduce delays.
- Process Risk: Change management can increase dependency on approval processes and stakeholders.
Used By
- Lean Software Development: Lean emphasizes managing changes effectively to ensure continuous improvement and adaptability.
- Scrum: Changes are managed through the product backlog and sprint planning.
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.
See Also
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.
Scrum
An Agile framework for managing and completing complex projects.