LEARN. PRACTICE. GROW.Concept and mechanism
Comparing options requires common criteria and enough information for a decision. Distinguish mandatory conditions from weighted preferences and make uncertainty in effort, cost, and benefit explicit. The most desired option may depend on an interface unavailable for the release. Analyze dependencies before promising a feature set. A baseline records what was accepted, in which version, and under which conditions; it does not mean needs can never change. Rejected or deferred requests retain their rationale and, where relevant, a condition for reassessment. The approval process should identify who can accept the commitment, including operational impacts. Voting can help explore preferences but does not remove previously defined responsibilities.
Guided application
In an exercise, a release has capacity for ten days. Feature A needs six days and an additional four-day interface; B needs five and is independent. Promising A and B as eleven days ignores that A needs ten in total and the combination needs fifteen when efforts are additive and no work is shared. Compare feasible options and value instead of silently removing the dependency. After selection, use prototypes, examples, and review to validate understanding and complete criteria. If a prototype was accepted by day-shift users, do not assume it covers on-call exceptions. Record the evidence limit and arrange the missing review. Baseline approval should reflect what was actually agreed, not what the team hopes others will accept later.
A with its dependency costs ten days; A plus B costs fifteen under the exercise conditions.
Common pitfalls
Omitted dependency; voting treated as universal authority; partial approval treated as full coverage.
Related topics: From need to solution scope · Value, stakeholders, and business case · Requirements plan and responsibilities
Accept or defer requirements with explicit value, feasibility, and authority.
Reference: Requirements management planning and benefits evaluation · Five-domain ECO / verified 2026-10-01