• Home
  • BVSSH
  • Engineering Enablement
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Standard : Business value is defined, measured, and shared for all work

Purpose and Strategic Importance

This standard ensures every piece of work has clearly defined, measured, and shared business value-aligning delivery with tangible outcomes. It creates transparency on why the work matters and how success is tracked.

Aligned to our "Measure & Validate Value" policy, this standard enables informed prioritisation, continuous feedback, and evidence-based improvement. Without it, teams risk building the wrong things and missing opportunities to maximise impact.

Strategic Impact

Clearly defined impacts of meeting this standard include improved delivery flow, reduced risk, higher system resilience, and better alignment to business needs. Over time, teams will see reduced rework, faster time to value, and stronger system integrity.

Risks of Not Having This Standard

  • Reduced ability to respond to change or failure
  • Accumulation of technical debt or friction
  • Poor developer experience and morale
  • Decreased confidence in releases and features
  • Misalignment between technical implementation and business priorities

CMMI Maturity Model

  • Level 1 – Initial: Value is assumed but not explicitly defined or tracked.

  • Level 2 – Managed: Some teams define value post hoc, without consistent measures.

  • Level 3 – Defined: Value definitions and metrics are established upfront for all work.

  • Level 4 – Quantitatively Managed: Value outcomes are tracked, benchmarked, and shared transparently.

  • Level 5 – Optimising: Value measurement is integrated into prioritisation and delivery, continuously improving alignment to impact.


Key Measures

  • Adoption metrics relevant to the standard (to be defined)
  • Quality, throughput, and system health metrics aligned to capability
  • Maturity scores based on structured assessment
Associated Policies
  • Measure & Validate Value
Associated Practices
  • Synthetic Monitoring
  • Automated Incident Response
  • Contract Testing

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering