The Change Request is examined and the Project Manager decides, based on its type, priority and severity, in which iteration it should be fixed. If the Change Request is to be held until a later iteration, the Project Manager simply re-plans the future iterations (in the Software Development Plan), so that the impact of the Change Request is understood now, and resource acquisition tasks can be initiated as early as possible, to avoid unpleasant surprises later.

The Project Manager decides which organizational position(s) should be responsible for implementing the change.

The Change Request should already contain a description in outline of the required change (because the Change Request has already been analyzed and approved). This step refines that description into an unambiguous statement of what is to be done and produced.

The Project Manager, in consultation with those responsible for the Change Request, refines the effort and other resource estimates in the Change Request into firm planning estimates, to which the responsible staff are expected to commit.

If the Change Request is to be implemented in the current iteration, the Project Manager, in consultation with those assigned responsibility, will set a start date and expected duration for the work.

If necessary, the current Iteration Plan is revised, and any impact on future iterations should be reflected in the Software Development Plan. As a result of the re-planning, the Project Manager may have to invoke the Task: Handle Exceptions and Problems, to bring the project state into line with the new plans, particularly if the current iteration is affected by a resource shortfall or slippage of planned capability to later iterations.

The Work Order(s) defining the work to be done, schedule, responsibility, and so on, are issued by the Project Manager. The activity (in the work breakdown structure) against which the effort is budgeted, is identified in the Work Order.