Standard : Delivery Commitment Confidence Score

Description

Delivery Commitment Confidence Score captures the team’s subjective confidence in delivering their planned sprint or iteration scope at the time of planning. This forward-looking metric encourages shared understanding, honest assessment of risk, and alignment on what’s achievable.

By tracking confidence over time and comparing it to actual delivery results, teams can improve their ability to make realistic commitments and adapt their planning practices accordingly.

How to Use

What to Measure

  • At the end of sprint or iteration planning, ask the team to rate their confidence in meeting the delivery commitment (scope and sprint goal).

  • Use a simple scale such as:

    • 1 = Low Confidence
    • 2 = Somewhat Confident
    • 3 = Confident
    • 4 = Very Confident
    • 5 = Extremely Confident

  • Capture an average or consensus score, and record it alongside the sprint commitment.

Formula

There is no strict formula, but teams can track:

  • Average Confidence Score per Sprint
  • % of Sprints with High Confidence (e.g. 4 or 5)
  • Correlation with Actual Delivery Success (e.g. did planned vs. completed match?)

Instrumentation Tips

  • Use digital planning boards (e.g. Jira, Miro, Mural) to capture votes or confidence scores anonymously.
  • Visualise trends over time alongside delivery metrics.
  • Discuss discrepancies between high confidence and poor delivery (or vice versa) in retrospectives.

Benchmarks

This metric is subjective, so benchmarking is team-specific. However:

Score Range Interpretation
4–5 Team feels highly capable of delivering plan
3 Team is uncertain about risk or capacity
1–2 Team lacks confidence in the plan

Consistency between confidence and outcomes is more valuable than aiming for high confidence alone.

Why It Matters

  • Creates psychological safety
    Encourages open discussion of risks, doubts, and constraints.

  • Surfaces hidden delivery risks
    Misalignment or unspoken uncertainty can derail a sprint — this metric helps uncover it early.

  • Improves planning practices
    Confidence trends over time help refine estimation and planning realism.

  • Supports stakeholder trust
    Teams that express and meet realistic commitments build credibility.

Best Practices

  • Discuss confidence as a team — it’s not just a number, it’s a conversation starter.
  • Use the metric to inform mid-sprint reviews and plan adjustments.
  • Track confidence alongside delivery performance to calibrate future commitments.
  • Explore and resolve sources of low confidence during planning or refinement.
  • Ensure confidence scores reflect team belief in delivery, not management pressure.

Common Pitfalls

  • Treating confidence scores as performance metrics, creating pressure to overstate.
  • Ignoring low confidence indicators and proceeding with overambitious plans.
  • Collecting scores without follow-up discussion or analysis.
  • Confusing individual confidence with team-wide shared understanding.

Signals of Success

  • Confidence scores are stable and reflect the team’s experience of delivery.
  • Teams are transparent about concerns and able to adjust scope accordingly.
  • Correlation improves between high confidence and actual successful delivery.
  • Stakeholders respect confidence as a meaningful input to planning conversations.
  • [[Sprint Goal Success Rate]]
  • [[Planned vs. Completed Work Ratio]]
  • [[Forecast Accuracy (Story Points or Item Count)]]
  • [[Work Replanning Rate]]

Aligned Industry Research

  • Agile Estimating and Planning (Mike Cohn)
    Recommends incorporating team confidence into forecasting and scope decisions.

  • Psychological Safety (Amy Edmondson)
    Highlights the importance of environments where people feel safe to speak candidly about risks and uncertainties.

  • Evidence-Based Management (Scrum.org)
    Encourages the use of forecast ranges and confidence levels to better support empirical planning.