In traditional solution development, change management ensures that newly identified or changed requirements are identified, assessed, and decided upon.

It further ensures that changes to all projects , regardless of approach, are documented.

Change management makes it possible to maintain control over development of the solution in the event of changes to objectives, scope, requirements, framework conditions, etc., and to recognize the impact on subsequent use and operation. The project manager ensures that the change process is followed and documented consistently.

In traditional solution development, execution planning and outcomes are adjusted based on approved changes.

In agile solution development, only the changes are documented in the change status list.

There is no formal change management in the initiation phase because the organization and solution requirements and the solution objectives have not yet been defined. If there are changes in relation to the project initiation order, for example, the project sponsor decides on these changes.

The changes are managed within the scope of solution development according to the project management plan.

Under the traditional approach, approved changes are updated in the solution requirements.

Under the agile approach, documentation of the most significant changes is drawn up based on the updated solution requirements.

The change status list keeps track of all the changes dealt with and provides an overview of their status.

1. Solution requirements
2. Change request

1. Change request
2. Change status list
3. Project management plan
4. Solution requirements