A software development team has just completed the planning phase of a project when management...

When new requirements are recommended after planning, the correct response is to perform an impact analysis before deciding how to proceed. Impact analysis evaluates effects on scope, schedule, cost, staffing, design, risks, quality objectives, test plans, documentation, and contractual commitments. Automatically moving the requirements to a future release may ignore business priority or urgency. Outsourcing the work does not remove the need to understand impacts and may introduce supplier risks. Simply adding resources and budget to preserve the original date may be unrealistic and can create quality problems. Software quality engineering requires controlled requirement changes based on evidence. Therefore, the team should analyze the impact and then adjust the plan appropriately.

================