value-cost-risk-analysis

Installation
SKILL.md

Purpose

Guide requirements engineers through the Wiegers value/cost/risk priority model to produce a defensible, quantitative prioritization of requirements. This model replaces subjective "high/medium/low" rankings with a multi-factor scoring system that makes trade-offs explicit and traceable.

This is not a popularity contest or a voting exercise. It is a structured analysis that forces stakeholders to consider both the value of having a feature and the cost and risk of building it.

Key Concepts

The Four Scoring Dimensions

Each requirement is scored on four dimensions using a 1-9 relative scale:

  • Relative Benefit (1-9) -- How much the customer or business benefits if this requirement is included. Score 9 for maximum benefit; score 1 for minimal benefit.
  • Relative Penalty (1-9) -- How much the customer or business suffers if this requirement is not included. Score 9 for severe penalty (regulatory violation, competitive loss); score 1 for negligible impact.
  • Relative Cost (1-9) -- How expensive this requirement is to implement relative to other requirements. Score 9 for most expensive; score 1 for least expensive.
  • Relative Risk (1-9) -- How much technical risk or uncertainty this requirement carries. Score 9 for highest risk (new technology, unclear feasibility); score 1 for well-understood implementation.

The Priority Formula

Installs
2
GitHub Stars
22
First Seen
2 days ago
value-cost-risk-analysis — jdm4pku/re-skills