AI-assisted delivery intelligence · Jira / Rovo

Kanban Board Steward

When a team changes the way it works, the board should make the change visible. Kanban Board Steward reads the evidence in Jira and turns it into a short, decision-ready account of flow, health and planning readiness.

Agent designEvidence rulesFlow healthAdoption

The problem

The board was changing. The conversation was not.

A team was moving to Kanban and changing the way it worked. The theory was sound. The transition was not frictionless: transparency was patchy, new routines had teething problems and the Product Manager and Engineering Manager were often looking at different versions of the work.

The board contained the clues, but not the shared account. People were spending time interpreting Jira rather than deciding what to do about the flow it described.

I designed Kanban Board Steward as an Atlassian Rovo agent that could interrogate a project on a reliable cadence, distinguish what the board proves from what it merely suggests and return a short report the team could use in its flow conversations.

Pilot adoptedThe first team made the agent part of its new workflow
Further testsAdditional teams are now using it
Wider groupThe work has been presented beyond the pilot

The intelligence

An agent that knows the difference between a signal and a story.

Kanban Board Steward is not a chatbot bolted onto a board. It is a small evidence system: defined inputs, explicit rules, working-day logic and guardrails against turning a plausible guess into a fact.

01

Gather

Read the project, its active work, recent completions, blocked items, comments and movement between columns.

02

Normalise

Use the team’s actual statuses and columns, exclude weekends and keep the scope clear enough to compare week to week.

03

Challenge

Test evidence against WIP limits, ageing thresholds, comment freshness, readiness and blocked-work rules.

04

Report

Return a compact account of what changed, what needs attention and what is ready to pull next.

The output

Useful in the room, not impressive on a dashboard.

The report is deliberately short. It gives people enough evidence to have a better conversation without pretending that a Jira sweep can replace judgement.

Kanban Board Steward
Illustrative data / Thursday flow check

Flow

Throughput is holding.

Six items closed this week. WIP is flat, but two items have crossed the team’s ageing threshold.

Attention

One dependency is doing the hiding.

The blocked item has no update for three working days. It sits behind work that cannot complete without it.

Planning

Ready to pull, with a caveat.

Four items meet the lightweight readiness check. Two have an owner but still need a clear acceptance signal.

Guardrail

Facts are reported as facts. Interpretation is labelled as interpretation. The team decides what happens next.

Designed for the transition

Make the new way of working visible while it is still becoming normal.

Monday / full sweep

Start the week with a shared picture.

Active work, recent completions, WIP pressure, ageing, stale comments, blocked items and planning readiness. Enough detail to shape the week, not enough to become another meeting.

Thursday / flow check

Catch drift before it becomes a story.

A lighter check on movement, bottlenecks and anything that has gone quiet. It keeps the board in the conversation without tying the team to a ceremony.

What happened next

The pilot did what a pilot should do: earn the next test.

The pilot team adopted the agent-supported workflow successfully. Further test teams are now using it, and the work has been presented to the wider group.

The significant result is not that Rovo produced a report. It is that the report became useful enough for other teams to try.

Back to selected work