Practice scorecard and governance vocabulary: production readiness scorecards, service maturity models, compliance gates, ownership requirements, and runbook mandates.
0 / 5 completed
1 / 5
A platform team says 'the service has a score of 7/10 on the production readiness scorecard.' What does this mean?
A production readiness scorecard evaluates services against defined criteria. A score of 7/10 means the service meets most requirements but has gaps. Teams use scorecards to systematically improve service quality before and after going to production.
2 / 5
What are 'compliance gates' in a software delivery context?
Compliance gates are checkpoints in the delivery pipeline that enforce governance requirements — such as security scans, license checks, or mandatory reviews. Services that fail a gate cannot proceed until the issue is resolved.
3 / 5
A platform engineer says 'ownership is required for production.' What does this mean?
'Ownership is required for production' is a governance policy meaning every production service must have a registered owner — typically a team — who is accountable for on-call, incidents, and maintaining the service. Unowned services cannot go to production.
4 / 5
What is a 'maturity model' in the context of service or platform governance?
A maturity model describes levels of practice quality — from ad hoc (Level 1) through managed and optimized (Level 4/5). Platform teams use maturity models to help service teams improve practices incrementally rather than requiring perfection immediately.
5 / 5
A governance policy states 'this service needs a runbook.' What is a runbook?
A runbook is operational documentation: step-by-step procedures for common operational tasks and incident response scenarios. A service without a runbook makes on-call work much harder and is a common production readiness requirement.