Sprints

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Scoped to a fixed window, so the question becomes will this fit rather than what is in progress.

Carry-over is shown rather than quietly renumbered, which is the only reason to timebox at all.

Points are optional; the count of carried cards is usually the more honest signal.

How it works

1
Work is committed to a named window, and the board is scoped to it.
2
An item not finished carries over, keeping the sprint label it was first committed to.
3
The count of carried items is the honest signal, more than the points total.
4
Closing a sprint leaves the record rather than clearing it.

Best for

Anything that moves through stages: leads, orders, applications.

Not the right choice for

Data with no natural stages — you get one very long column.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

Field	Type	Filled from
Itemrequired	text	Work committed to this window, usually named when the sprint is planned.
Columnrequired	choice	Its state within the sprint.
Points	text	Relative size, if the team uses them. Optional because many do not.
Sprintrequired	text	Which window it was committed to. Carry-over keeps its original label.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

No velocity calculation or forecasting. The carried count is the intended feedback.
One sprint at a time; there is no cross-sprint view of a long piece of work.
Points are text and are not summed, deliberately.
No capacity planning against who is available.

Before it works

What you have to provide, if anything.

Name the sprint before committing work to it, or carry-over cannot be tracked.
Pair with Task board if the team does not actually work in fixed windows.

In practice

A development team that had over-committed for four sprints running.

“Move the Firestore work into this sprint as well.”

What was said to the agent

What the agent built

The card carried over, still labelled with the sprint it was first committed to.

What changed

Three sprints later the pattern was undeniable in one screenshot. Commitments dropped by a third and started landing.

Better with

These do a different job on the same data. An agent can have all of them.

Task boardLive

Several pieces of work are in flight at once and the useful question is what stage each is at rather than when it is due.

RoadmapLive

You want to tell customers or a team where the product is heading without committing to dates you will have to correct.

Goals / OKRsLive

A quarter or a year has stated aims and progress against them needs checking more than once at the end.

Questions

What data does the Sprints page use?

It reads task records the agent has collected. Iterations with scoped tasks. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a kanban board the wrong choice?

Data with no natural stages — you get one very long column. It is best for: anything that moves through stages: leads, orders, applications.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.