In planning, unstable requirements typically lead to which effect on the program?

In planning, unstable requirements typically lead to which effect on the program?

• A. Shorter development cycles.
• B. Negative impact on cost and schedule.
• C. Immediate cost reductions.
• D. No change in risk profile.

Answer: (B)

Unstable requirements introduce frequent change and ambiguity into planning. When the scope keeps shifting, the team must continually rework design, code, and tests, which drives extra labor and delays. Estimates become less reliable, so the schedule becomes longer and costs rise, while risk grows because of increased chances of rework, bugs, and integration issues. Shorter development cycles require a stable understanding of what’s being built, so instability tends to lengthen cycles rather than shorten them. Immediate cost reductions aren’t expected; changes and rework add expense rather than cut it. The overall effect is a negative impact on both cost and schedule, with higher uncertainty and risk.

Unstable requirements introduce frequent change and ambiguity into planning. When the scope keeps shifting, the team must continually rework design, code, and tests, which drives extra labor and delays. Estimates become less reliable, so the schedule becomes longer and costs rise, while risk grows because of increased chances of rework, bugs, and integration issues. Shorter development cycles require a stable understanding of what’s being built, so instability tends to lengthen cycles rather than shorten them. Immediate cost reductions aren’t expected; changes and rework add expense rather than cut it. The overall effect is a negative impact on both cost and schedule, with higher uncertainty and risk.