Sprint planning
Sprint planning with capacity, rollover and burndown
Plan sprints on a regular cadence with a capacity in points. Unfinished work moves into the next sprint on its own, and burndown and velocity show how the team is doing.
How does sprint planning work in Shaire?
In Shaire, sprints are called cycles in the navigation. Each one has a start, an end and a capacity in points when you set one, and a cadence keeps the next sprints ready, from one to four weeks long. You plan by setting the sprint on tasks in any list or view. When a sprint ends, unfinished work rolls into the next one unless you turn that off. Burndown, velocity and cycle time reports show how the team is doing. It is included in every plan.
What you can do
A sprint cadence
Choose a length of one to four weeks and a start date. Shaire keeps the next sprints ready and names them for you.
Capacity in points
Give a sprint the number of points the team expects to take on, and see the committed work against it.
Rollover you control
When a sprint ends, unfinished work moves into the next one. Turn rollover off for a sprint that should close as it is.
Plan from any view
Set the sprint from the list, the board or the bulk edit bar, filter by sprint and group the board or the timeline by it.
Burndown and velocity
Follow remaining work against the ideal line in tasks or points, and compare completed and unfinished work across past sprints.
Cycle time
See the median and 85th percentile time from start to done, and how long work waits in each status.
Plan from the specs your team writes
Turn the checklist in a planning doc into tasks, then set their sprint from the list or the board. A burndown can also follow a dated milestone, and every milestone has a written brief next to its tasks. Sprints have no page of their own, so the plan lives in your docs and the progress lives in the sprint.
Sprints without the ceremony
Shaire gives a team sprints that work from the first day. Create a cycle with a start and an end, or set a cadence and let Shaire keep the next sprints ready. A sprint is a field on each task rather than a separate backlog to maintain, so you plan in the list you already use.
Set a cadence once
Open the cadence on a folder or on the Cycles page. Choose a length of one to four weeks, the day the first sprint starts and how many sprints to keep ahead. Shaire names them from a pattern and creates the next one as each sprint ends. If sprints keep ending with nothing planned, the cadence pauses and shows a banner so you can resume it.
Plan with capacity
Give a sprint a capacity in points: the amount of work the team expects to take on. Then plan from any view. Set the sprint on tasks in the list, drag cards between sprint columns on the board or select a batch and set the sprint in one step. The Cycles page shows each sprint’s progress and its committed work against capacity.
Let unfinished work roll over
When a sprint ends, its unfinished tasks move into the next sprint on their own, so nothing is left behind in a closed sprint. If a sprint should close exactly as it is, turn rollover off for it. When you are done with old sprints, archive them: finished tasks are archived with the sprint and unfinished ones go back to planning.
See how the team is doing
The reports show the burndown of a sprint in tasks or points, with the ideal line beside it. Velocity compares completed and unfinished work across finished sprints, with the average per sprint. Cycle time shows how long work takes from start to done and where it waits. Workload shows how many open tasks and points each person holds.
Keep the plan in a doc
Sprints do not have pages of their own. Write the goal and the scope in a page, turn its checklist into tasks and set their sprint. If you need agile reporting across many teams, Jira goes further, and our comparison with Jira explains where.
Limits to know about
Sprints have no page of their own
A sprint has no description, comments or linked docs. Write the sprint goal in a page and link the tasks to it.
No warning over capacity
Shaire shows committed work against capacity but does not warn you when a sprint is overloaded, and capacity is not set per person.
Fixed reports
Burndown, velocity and cycle time are fixed panels. There are no custom dashboards, no forecasts and no report exports.
Cadences in whole weeks
A cadence runs from one to four weeks. Sprints created by a cadence start without a capacity until you set one.
Rollover runs every hour
Unfinished work moves to the next sprint within the hour after a sprint ends, not at the exact minute.
Velocity counts at the boundary
Work finished after a sprint has ended does not count toward that sprint's velocity.
Common questions
Are sprints and cycles the same thing?
Yes. The navigation calls them cycles, and the list, filters and bulk edit call the field sprint. Both mean a fixed span of time with a start, an end and the work planned into it.
What happens to unfinished tasks when a sprint ends?
They move into the next sprint within the hour. If there is no next sprint yet, Shaire creates one. Turn rollover off for a sprint and its unfinished work stays where it is.
Can I measure velocity in points?
Yes. Velocity compares the completed and unfinished work of each finished sprint against its capacity and shows the average per sprint. The burndown switches between tasks and points.
Can I archive old sprints?
Yes. Archiving a sprint archives its finished tasks and sends unfinished ones back to planning. You can archive every ended sprint at once and show archived sprints again when you need them.
Related features
Compare Shaire
Try it with your own work
Two people, every feature, no card. Invite the rest of the team when it earns its place.