• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Standard : Teams define and maintain a sustainable delivery pace

Purpose and Strategic Importance

This standard ensures that teams work at a delivery pace that is sustainable over time, balancing urgency with wellbeing. A sustainable pace enables consistent, high-quality output without burnout, protects innovation capacity, and supports long-term team health.

It supports our policy to “Make Delivery Sustainable for People” by embedding practices that prevent overcommitment, reduce stress, and foster rhythm and focus. Without this standard, short-term delivery pressure can undermine team cohesion, degrade quality, and lead to attrition or disengagement.

Strategic Impact

  • Preserves team wellbeing and morale over the long term
  • Enables consistent and predictable delivery outcomes
  • Builds psychological safety and reduces burnout risk
  • Protects time for learning, reflection, and innovation
  • Supports higher engagement, retention, and trust

Risks of Not Having This Standard

  • Teams work unsustainable hours or sprint from crisis to crisis
  • Burnout increases, reducing creativity, focus, and retention
  • Quality and reliability suffer due to pressure and fatigue
  • People leave the organisation or withdraw from ownership
  • Delivery timelines become less predictable or slip altogether

CMMI Maturity Model

Level 1 – Initial

Category Description
People & Culture - Pace is dictated by urgent deadlines or external demands.
- Exhaustion is normalised or rewarded.
Process & Governance - No explicit conversation about pace or capacity.
- Success is measured by output, not sustainability.
Technology & Tools - Tools reflect workload but not team load or pace indicators.
Measurement & Metrics - No indicators for workload sustainability or burnout risk.

Level 2 – Managed

Category Description
People & Culture - Teams raise concerns about unsustainable expectations.
- Managers start tracking effort and team stress informally.
Process & Governance - Planning begins to reflect realistic capacity.
- Retrospectives highlight signs of team overwork.
Technology & Tools - Basic workload tracking tools are used (e.g. burndown, velocity).
Measurement & Metrics - Simple metrics (e.g. overcommitment frequency) emerge.

Level 3 – Defined

Category Description
People & Culture - Sustainable pace is actively protected by teams and leaders.
- Work-in-progress limits and flow principles are embraced.
Process & Governance - Cadence-based planning reflects capacity and team health.
- Teams regularly reflect on workload balance and recovery.
Technology & Tools - Workload, lead time, and WIP metrics are used in planning.
Measurement & Metrics - Pace metrics such as average throughput, rework, and spillover tracked.

Level 4 – Quantitatively Managed

Category Description
People & Culture - Teams use data and feedback to calibrate and improve delivery pace.
- Psychological safety supports honest conversations about pace.
Process & Governance - Workload, holidays, and skill availability are factored into planning.
- Pacing is treated as a team-level health metric.
Technology & Tools - Integrated tools show real-time pace, work pressure, and focus time.
Measurement & Metrics - Predictability, recovery time, and wellbeing trends are monitored.

Level 5 – Optimising

Category Description
People & Culture - Sustainable pace is a cultural norm reinforced by leadership.
- Teams experiment with work patterns (e.g. focus time, no-meeting days).
Process & Governance - Delivery plans include rest, slack, and learning as standard components.
- Pacing data informs delivery strategy and team design.
Technology & Tools - Tooling suggests adjustments to support sustainable working.
Measurement & Metrics - Sustained pace is correlated with long-term outcomes like retention, quality, and innovation rate.

Key Measures

  • % of teams delivering within planned capacity consistently
  • Burnout or wellbeing survey scores
  • Number of overrun sprints or missed WIP limits
  • Rate of rework or delivery errors linked to rushed work
  • Team satisfaction with delivery pace and workload
Associated Policies

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

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