If you tackle everything at once every week, it's easy to lose track. A sprint gives you a frame: your team picks what it wants to finish within a fixed period and works through it. Afterwards you look at what got done and plan the next one. The term comes from agile software development.
In CIRO NOISE, sprints belong to a board in the Tasks feature. Each sprint has a number, an optional name, a start and an end. CIRO NOISE suggests new sprints that fit: they start after the last sprint, no earlier than next Monday, and last as long as the previous one, or two weeks otherwise.
How a sprint works in CIRO NOISE
You estimate tasks in points, using 1, 2, 3, 5, 8 or 13, and drag them into the sprint in the planning view. Open tasks without a sprint are on the left, the sprint on the right. CIRO NOISE works out how much fits from the points your team completed in the last three finished sprints and shows whether there is room, a good fit or too much.
While the sprint runs, a chart shows every day how many points are still open, next to the line your team would ideally follow. The board pulse adds pace and a forecast of whether a goal with a deadline is on track or at risk.
Completing a sprint
With “Complete sprint” you close it, even before the planned end. Open tasks move into the sprint you choose, and finished ones stay in the old sprint as its result. If you delete a sprint, the tasks remain; only their scheduling is removed.
An everyday example
On Monday at 9:00, Kira's team accepts the new tasks from triage, pulls the tasks for sprint 14 into the sprint, assigns owners and estimates the effort. The planning view shows 34 of 38 points, a good fit. On Wednesday of the second week the chart sits above the ideal line, and Kira sees on the board which task is stuck, without calling a status meeting.