Delivery & Engineering Ops glossary

56 terms on scaled agile delivery, engineering performance and reliability.

Go deeper

See how this work connects to strategy and spend.

Explore the EOM

Frequently asked questions

What is the Delivery & Engineering Ops glossary?

It is a reference of more than 50 terms used to plan, deliver and run software at scale, from SAFe, PI planning and Kanban to DORA metrics, flow metrics, platform engineering and SLOs. Each entry gives a short definition first, then explains what the term means in practice.

Who is the Delivery & Engineering Ops glossary for?

Engineering and delivery leaders, release train engineers and Scrum Masters, platform and site reliability teams, agile coaches, PMOs and portfolio teams, and anyone responsible for how quickly and reliably software reaches customers.

How are the terms organized?

Terms are listed A to Z and tagged by category: agile and scaled delivery; flow and agile metrics; DevOps and engineering performance; and reliability and release. Use the search box or the category filters to narrow the list, or jump straight to a letter.

What is the difference between DORA metrics and flow metrics?

DORA metrics measure the delivery pipeline: how often teams deploy, how long changes take to reach production, how often they fail and how quickly service is restored. Flow metrics measure the whole value stream, from when work is accepted to when it is delivered, including time spent waiting. Most organizations use both. See flow metrics.

How do delivery and engineering operations fit into the Enterprise Operating Model?

Delivery and engineering operations sit in the Govern & Deliver part of the Enterprise Operating Model. They connect what teams ship, and how quickly and reliably they ship it, to the funded initiatives and strategy behind the work. Explore flow and DORA metrics.