Overview
Delivery governance is how Scrums.com ensures that every engagement runs to a consistent standard and that clients have the visibility and control to hold teams accountable. Governance is not bureaucracy — it is the system that makes predictable delivery possible. SEOP applies governance at three levels: process standards, performance measurement, and escalation management. The depth of governance available scales with your subscription tier.Governance by tier
| Governance feature | Standard | Recommended | Enterprise |
|---|---|---|---|
| Sprint rituals (standup, planning, retro) | ✓ | ✓ | ✓ |
| Delivery dashboards | Basic | Advanced | Custom |
| Monthly delivery reports | — | ✓ | ✓ |
| Quarterly Business Reviews (QBRs) | — | ✓ | Executive QBRs |
| Role-based access control | — | ✓ | ✓ |
| Audit logs | — | — | ✓ |
| SSO/SAML | — | — | ✓ |
| Custom dashboards | — | — | ✓ |
| Dedicated Enablement Team | — | Partner | Full team |
| Support SLA | 24h response | 8h response | 4h response |
Sprint governance
All Scrums.com teams operate within a structured sprint framework regardless of tier:- Sprint planning — Backlog items are reviewed, estimated, and committed at the start of each sprint
- Daily stand-up — Team members report progress, blockers, and plans daily (async or live)
- Sprint review — Completed work is demonstrated to stakeholders at the end of each sprint
- Retrospective — The team reflects on process improvements after each sprint
Performance measurement
SEOP continuously tracks delivery performance across four dimensions: Throughput — How much work is completed per sprint, measured in story points and ticket counts. Tracked against team commitments and compared to baseline velocity. Quality — Defect escape rates, PR rejection rates, and code quality gate scores from SonarCloud. Trends are visible in the Analytics dashboard. Speed — Cycle time, lead time for changes, and PR cycle time. These indicators show how efficiently work moves through the delivery pipeline. Reliability — Deployment frequency, change failure rate, and mean time to recovery (MTTR). Available on Recommended and Enterprise plans where CI/CD integration is in place.Escalation process
If delivery issues arise that cannot be resolved within the team, the escalation path is:Raise with your Enablement Partner
Contact your dedicated Enablement Partner as soon as a risk or issue is identified. Do not wait until sprint end.
Delivery Lead engagement
Your Enablement Partner engages the relevant Delivery Lead within 24 hours of the issue being raised.
Client Success escalation
If unresolved within 48 hours, the issue is escalated to Scrums.com’s Client Success leadership.
Quarterly Business Reviews
On Recommended and Enterprise plans, Scrums.com conducts formal Quarterly Business Reviews (QBRs):- Review delivery performance against agreed benchmarks
- Assess team composition and capacity for the next quarter
- Align roadmap priorities with your Enablement Partner
- Review cost, utilisation, and billing
Governance controls in settings
Workspace Admins can configure delivery governance controls in Administration → Governance:- Minimum Definition of Done criteria per project type
- Required reviewer roles before ticket status advancement
- Automated escalation rules for blocked tickets exceeding a configurable threshold
- Full audit log of policy changes and enforcement events (Enterprise)