Green Software PracticesAn open standard by GreenSeal.dev

GSP-ARC-06

Feature Necessity and Scope Assessment

Category
Software & Architecture Practices
Levels
Level 2
Priority
Supporting
ISO/IEC TS 20125-1
Requirements gathering phase

Requirement

The organisation shall assess the environmental justification of proposed features or functionality during requirements gathering, including consideration of whether features are necessary to deliver the intended user value relative to their resource cost.

Rationale

Features that are not needed generate unnecessary computation, data transfer, and maintenance burden throughout a service's life. Upstream scope discipline is one of the highest-leverage sustainability interventions available to a development team.

Evidence examples

Examples of evidence that can show the practice is in place. Other evidence may also be accepted.

  • Feature prioritization records referencing environmental cost
  • Scope review documentation with necessity assessment
  • Value-versus-environmental-impact analysis artefacts
  • Backlog refinement notes referencing sustainability criteria

Assessment scale

An assessor chooses one of these options, from best to worst.

  1. Implemented
  2. Partially Implemented
  3. Not Implemented