Queues and flow / Delivery leads, planning owners and acceptance reviewers

Retrospective desk

Inspect starvation in a queue rotation

Review which work class repeatedly misses service under a stated scheduling rule.

The artifact tests compliance with a declared recurring class-allocation rule, not simply age-based queue priority.

Request TeamBoostAI access Get the work brief Task table (.csv)

Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.

Original worked case · Manual planning resource

Inspect the decision, not just the summary.

Start with the invented evidence, follow the reasoning, and retain its limits when adapting the brief.

01 · Inspect the inputs

Every record stays visible

Inspect the invented case records
Two-slot cycle	Actual service	Declared B opportunity
1	A,A	1
2	A,A	1
3	A,A	1
4	A,A	1

Use horizontal scrolling for wide tables. These records are invented, not customer data.

Records · CSV Complete case · JSON Manual brief · Markdown

02 · Follow the reasoning

How the case leads to a decision

Four cycles×one declared B slot=4 opportunities; actual B service=0. Total service of eight says nothing about compliance with the work-class rotation.

The bounded result

Class B received zero of its four declared cycle opportunities. Inspect the repeated exception and restore an agreed service rule rather than calling eight completed A reviews proof that the rotation worked.

Definitions and method context

Records, decisions and policies are original synthetic examples. External references supply context; they do not validate these cases or TeamBoostAI capabilities.

The Kanban Guide ↗
Workflow and flow-measure context. Queue policies and staffing scenarios are explicitly local examples, not delivery guarantees.

External references checked 6 October 2026. Demand for these topics has not been measured.

Turn a retrospective into a follow-up

Illustrative retrospective desk

Synthetic planning case: A declared rotation should give one review slot to class B in each two-slot cycle. The actual log of eight slots is A,A,A,A,A,A,A,A.

B omitted in every cycle

Observed condition: Zero service across four opportunities
Next-cycle check: Check B eligibility and exception authority

A uses all eight slots

Observed condition: Total throughput hides class allocation
Next-cycle check: Review class outcomes beside the total

Next rotation under review

Observed condition: Cause and governing rule must be resolved
Next-cycle check: Inspect each of the next two cycles

Decision to make: Class B received zero of its four declared cycle opportunities. Inspect the repeated exception and restore an agreed service rule rather than calling eight completed A reviews proof that the rotation worked.

Check the governing rotation

Owner role · Queue owner

Evidence: One B slot per two-slot cycle is a real accepted policy for this example.

Inspect exceptions by cycle

Owner role · Coordinator

Evidence: All four omitted B opportunities remain visible with their actual cause unresolved.

Choose the service correction

Owner role · Decision owner

Evidence: The rotation or its authorized exceptions are explicitly changed and the next cycles are checked.

Filled manual planning note

Invented planning text. Adapt it to your evidence and confirmed owners.

Class B received zero of its four declared cycle opportunities. Inspect the repeated exception and restore an agreed service rule rather than calling eight completed A reviews proof that the rotation worked. Four cycles×one declared B slot=4 opportunities; actual B service=0. Total service of eight says nothing about compliance with the work-class rotation. The log does not record eligibility or exception reasons. Retain that gap rather than attributing motives or guaranteeing fairness.

Put the outline to work

Check the governing rotation. Check: One B slot per two-slot cycle is a real accepted policy for this example.
Inspect exceptions by cycle. Check: All four omitted B opportunities remain visible with their actual cause unresolved.
Choose the service correction. Check: The rotation or its authorized exceptions are explicitly changed and the next cycles are checked.

Questions about this workflow

Does zero B service prove deliberate neglect?

No. Missing eligible B work or another accepted exception may explain it; inspect the actual conditions.

Can eight completed items prove fairness?

No. Fairness and required class coverage are different from total throughput.

Does this create tasks in the product?

No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.

From a useful outline to team work

Explore TeamBoostAI for your team

Use the owned checks and downloaded brief to discuss this planning decision alongside your TeamBoostAI tasks. Confirm available fields, roles and account features separately. The example is manual; it does not calculate live analytics, create work or run an experiment in the product. Confirm the workflows available in your account before adopting this outline.

Request TeamBoostAI access