Question 500
A retailer approves many individually inexpensive new data fields until their combined effort threatens the next release date. Which ongoing control would best prevent this failure from recurring?
Explanation
Correct Answer
Use change trends in forecasts and regularly reconsider whether requests still support the business case and agreed products. It is appropriate because small changes can collectively undermine cost, schedule or scope; isolated item approval does not remove the need for aggregate control. The recurring failure risk is illustrated by: A retailer approves many individually inexpensive new data fields until their combined effort threatens the next release date.
Incorrect Answers
This repeating check is mainly concerned with keep the issue register and report aligned, not with the recurring weakness described here: A retailer approves many individually inexpensive new data fields until their combined effort threatens the next release date. The useful ongoing safeguard in this situation is to use change trends in forecasts and regularly reconsider whether requests still support the business case and agreed products.
This repeating check is mainly concerned with apply delegated change authority, not with the recurring weakness described here: A retailer approves many individually inexpensive new data fields until their combined effort threatens the next release date. The useful ongoing safeguard in this situation is to use change trends in forecasts and regularly reconsider whether requests still support the business case and agreed products.
This repeating check is mainly concerned with control an off-specification, not with the recurring weakness described here: A retailer approves many individually inexpensive new data fields until their combined effort threatens the next release date. The useful ongoing safeguard in this situation is to use change trends in forecasts and regularly reconsider whether requests still support the business case and agreed products.