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¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. The single citation of this work carries no recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:506afdecd0ee · see in the full table