After a project team has almost completed the development on the project's original requirements, the users identify functionality that is necessary but was not in the original requirements. The proje

Updating the risk register would be appropriate if the new functionality introduced new uncertainties, but the primary action for incorporating new requirements is a change request, not just a risk update.

Implementing the change directly without a formal change request process leads to scope creep and lack of control over project resources and schedule.

Canceling the project is an extreme and usually unwarranted action in response to new functionality requests; proper change management is the appropriate response.

When new requirements are identified after the project's scope is defined and development is underway, a formal change request must be generated to evaluate, approve, and incorporate the new functionality into the project plan. This ensures proper scope control and prevents unmanaged additions.