Manage changes to the requirements as they evolve during the project.

Refer to the Configuration Management process area for more information about maintaining and controlling the requirements baseline and on making the requirements and change data available to the project.

During the project, requirements change for a variety of reasons. As needs change and as work proceeds, additional requirements are derived and changes may have to be made to the existing requirements. It is essential to manage these additions and changes efficiently and effectively. To effectively analyze the impact of the changes, it is necessary that the source of each requirement is known and the rationale for any change is documented. The project manager may, however, want to track appropriate measures of requirements volatility to judge whether new or revised controls are necessary.

Typical Work Products

1.    Requirements status

2.    Requirements database

3.    Requirements decision database

Subpractices

1.    Document all requirements and requirements changes that are given to or generated by the project.

2.    Maintain the requirements change history with the rationale for the changes.

Maintaining the change history helps track requirements volatility.

3.    Evaluate the impact of requirement changes from the standpoint of relevant stakeholders.

4.    Make the requirements and change data available to the project.