Change Management
This practice manages ad-hoc requests for change to the product being developed or to the scope of the project that occur during the development lifecycle.
Relationships
Contents
Main Description

The Change Management practice is very central in projects because it will minimize rework. [***.......TO BE COMPLETED ***]

The Essence of Change Management

 Often when a project is ongoing, you think: "I wish I could have known that before I did this". Change management is about knowing things before you do something. You need to have a consistent set of requirements that are agreed upon by all stakeholders before you start coding (a baseline).

 

 [***.......TO BE COMPLETED ***]


Why Adopt this Practice?

[*** Include some content here that describes the business value of this practice -- what do you get when you adopt it?  This section is essentially the value proposition for the practice.  You may want to describe some common problems and how this practice solves those problems.   ***]   

How to Read this Practice

The best way to read this practice is to first familiarize yourself with its overall structure -- what it is in it and how it is organized. 

[*** To be completed.... ***]

For step-by-step instructions on how to adopt this practice, see How to Adopt This Practice.

Additional Resources

For more information on the whole team approach, see the following:

  • [*** Add more, as needed ***]