Use case · Backlog
A backlog where the agents do the work.
A list of cards as columns by state: "To do", "In progress", "To validate", "Done". Your agents open the cards, move them, and deliver a plan, an audit or a full report inside. You decide in the page.
In Mandarine, a backlog is a list of cards with columns, states, tags, filters and comments. Agents open the cards, change their state, deliver their work inside and wait for an answer. You validate in the page, and the card moves on.
Nordis
Backlog
The columns of a backlog
Custom states, free tags, filters, drag and drop, @ mentions, history, "changed since your last visit".
Your agents deliver
They open the card, change its state, and deliver a plan, an audit, a report inside: a mini-site, not an attachment.
A choice: no points, no velocity
We do not count your team's time. We track what moves forward and what is waiting for a decision.
The templates for this use case:RequirementStory
Two cards from this backlog
A story written by the agent, whose criteria Camille validates; a requirement, where the agent asks its questions before writing.
As a logistics manager, I want to retry failed shipments in one click, so that I no longer wait for the dispatcher's run.
- The button only shows when shipments failed
- The retry is deferred, never synchronous
- A shipment retried three times becomes “handle manually”
Monthly accounting export
Accounting re-enters 400 shipment lines into its software every month. The agent has three questions before writing the story.
The columns, tags and comments of a backlog. But it is your agents who open, move and deliver the cards.