Agile delivery assessment: telling ceremonies from results

How to assess an agile team: backlog, velocity, definition of done, technical debt, impediments. The questions by role, the evidence and how to recognise an adoption that is only a facade.

Processagileassessmentdeliveryscrum19 November 2026 · 3 min read

A team can hold the daily every morning, the retrospective every two weeks and still deliver late, with quality getting worse. The ceremonies are there, the results are not. An agile delivery assessment is for understanding whether the agility is real or a facade, and where the time is lost.

The scope

It applies to development teams working with Scrum, Kanban, SAFe or LeSS, and to any project where the health of delivery is the main concern. Before judging, you establish which framework is really in use: often it is a hybrid adapted over time, and it must be assessed for what it is.

The areas

  1. Framework and ceremonies. Is the declared framework followed consistently or adapted informally?
  2. Backlog. Who curates it, who decides the priorities, how old the items are, how often it is refined.
  3. Speed and predictability. The trend of velocity over the last sprints, the cadence of releases, how predictable they are.
  4. Quality. Peer review, automated tests, coverage thresholds, definition of done.
  5. Impediments and technical debt. How blockers are tracked, how long they take to close, whether technical debt appears in the backlog.
  6. Feedback from production. How incidents flow back into the backlog.

The questions by role

Delivery lead and scrum master. Which framework and how closely is it followed? What is the velocity trend over the last six sprints? Who curates the backlog and who sets the priorities? How are impediments tracked and resolved and how long does it take on average to close a blocker? How is technical debt handled?

Product owner and business leads. Is the product roadmap visible and updated at least every quarter? How are acceptance criteria defined and checked? What is the release cadence and how predictable is it?

Developers. How is code quality ensured (reviews, automated tests, coverage thresholds)? What is the definition of done and is it always applied? How do production incidents come back into the backlog?

The evidence

  • a velocity chart for the last eight to ten sprints;
  • backlog health indicators (age of items, frequency of refinement);
  • a release burn-down or cumulative flow diagram;
  • the definition-of-done document;
  • the impediment log with resolution times.

The warning signs

  • Velocity falling continuously over several consecutive sprints with no explanation.
  • Backlog items months old and never refined.
  • No definition of done, or one not applied in reviews.
  • Technical debt entirely absent from the backlog.
  • The product owner does not take part in sprint reviews.

How to read the result

The first criterion: separate problems of process maturity from those of team capability. The same symptom (late deliveries) can have opposite causes: a competent team with a chaotic backlog, or an orderly process with insufficient skills. The corrective actions are different and confusing them wastes months.

The second: understand whether adoption is real or a facade (cargo cult). The ceremonies are there, but what about the principles? A typical sign: the retrospective produces actions that nobody picks up in the next sprint.

An example

A team delivers everything it planned every sprint, but velocity is stable only because the stories are split so that they "close" in two weeks, while defects come back as unplanned work. The assessment does not see a slow team, it sees a team measuring the wrong thing. The metric to watch is the work that comes back, not velocity.

How to use the skill

The skill brings areas, questions, evidence and reading criteria in a form an agent can use, with or without interviews.

This article is an OIAR skill

What you have just read is the content of a skill from the OIAR catalogue, written for people. Knowledge like this, but richer and deeper, written for the agents, drives the interviews, the analysis and the report inside the platform. Skills are used in OIAR: to try this one on a project of yours you need an account.

agile-deliveryKnowledge for assessing the delivery of agile teams (Scrum, Kanban, SAFe, LeSS): backlog, velocity, definition of done, technical debt, impediments, feedback from production. Use it when the user asks for an assessment of a development team or the reading of delivery indicators, with or without interviews.