First things first¶
Wiegers, K. E. (1999). First things first: Prioritizing requirements. Software Development, 7(9), 48-53.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Prioritization
- When stakeholders disagree (marketing says reach is low, customers say impact is high), the metric makes disagreement visible and resolvable, echoing Wiegers's (1999) prescription that explicit numerical scoring forces customers and developers to surface and reconcile their differing valuations.
This sourceProposes a numeric value-cost-risk scoring scheme for software requirements; argues that explicit prioritization makes customer-developer disagreement visible and resolvable through shared metric rather than item-by-item debate.
- When stakeholders disagree (marketing says reach is low, customers say impact is high), the metric makes disagreement visible and resolvable, echoing Wiegers's (1999) prescription that explicit numerical scoring forces customers and developers to surface and reconcile their differing valuations.
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Registry ID ref:506afdecd0ee · see in the full table