Procurement prefers a predictive baseline for a contractor-built 311 mobile app, while product owners worry about discovering the wrong features late. Which statement best reflects that trade-off?
Select an answer to reveal the explanation.
Short Explanation
A predictive baseline is a sturdy contract fence for the 311 builder — clear enough to bid and schedule — but you might find the wrong ticket types only after most of the fence is up. That late-discovery risk is the classic trade-off. Skipping baselines or claiming perfect features without learning misreads predictive delivery.
Full Explanation
Predictive approaches provide stable baselines that support contracting and long-horizon planning, which procurement often values. A corresponding drawback is delayed discovery that features miss user needs when feedback arrives late, as with a 311 app. Predictive work still uses scope documents and does not guarantee perfect fit without validation.