Sprints

A Sprint is a time-boxed set of tasks owned by one Space. It helps a team plan a focused scope, track progress, and decide what happens to unfinished work when the time box ends.

Tasks remain the source of execution and discussion. A Sprint adds schedule, scope, and reporting.

Enable Sprints for a Space

Sprints are optional and configured per Space. When enabling them, choose one mode:

Automatic cadence: Sharkly maintains the schedule and future Sprints.

Manual: People create, start, and complete Sprints explicitly.

The selected mode changes lifecycle behavior, not task ownership. Every task in a Sprint still belongs to the Sprint's Space.

Automatic cadence

Automatic cadence can configure:

Sprint duration.

Cooldown duration between active Sprints.

Start weekday.

Number of future Sprints to maintain.

Timezone.

Rules that add tasks when they enter selected Unstarted, Started, or Completed status categories.

Sharkly creates future Sprints, starts and completes them on schedule, and carries unfinished work forward. During the active Sprint or cooldown window, tasks that enter a matching status category can be added according to the enabled rules. Enabling a rule immediately reconciles the current window, so tasks whose matching status change already occurred within that window can also be added; older changes are not backfilled.

Starting an upcoming Sprint early completes the current automatic Sprint first and rolls unfinished work into the Sprint being started.

Manual mode

Manual mode leaves lifecycle control to the team:

Create a planned Sprint when needed.

Start it without changing its configured dates.

Run more than one active Sprint in parallel.

Choose which active Sprint to complete.

Choose where unfinished tasks go when completing a Sprint.

For unfinished work, the completion flow can move tasks to no Sprint, another active or upcoming Sprint, or a newly created Sprint.

Automatic creation, rollover, cooldown, and status-based add rules remain inactive while the Space is in Manual mode.

Sprint states

Sprints use these display states:

Current: active now.

Upcoming: the next planned Sprint in automatic cadence.

Planned: a later or manually planned Sprint.

Completed: finished and retained for reporting.

Canceled: no longer active.

Completed and canceled Sprints appear in the Space archive rather than the active planning list.

Add tasks to a Sprint

Add or move a task through its Sprint field, a task list, or Sprint planning.

A task can also have no Sprint. This is useful for Backlog work or tasks that are not committed to a time box.

Only completed tasks can be added to a previous Sprint. This allows historical correction without placing unfinished work into a closed period.

Adding a task to a Sprint does not change its task status. Move a Backlog task to a status that is ready for work when execution should begin.

Scope, progress, and capacity

Sprint reporting includes task counts and, when Space estimates are enabled, estimate-point totals:

Scope.

Started work.

Completed work.

Completion rate.

Capacity.

Burnup history.

Capacity uses recent completed Sprint velocity when enough history exists and otherwise falls back to an estimate based on Space size. Treat it as planning input rather than a guarantee.

Change Sprint dates

A planned Sprint can have its start and end dates edited. An active Sprint's start date is fixed, but its end date can be changed.

In automatic cadence, moving a planned start can shift later planned Sprints to preserve ordering. Date changes are constrained by neighboring Sprint boundaries.

Switch modes or disable Sprints

Switching to Manual mode keeps existing Sprints but stops automatic creation, start, completion, and rescheduling.

Switching back to Automatic cadence resumes system scheduling without rewriting the existing planned sequence.

Disabling Sprints completes active Sprints, removes future Sprints, and keeps completed data available for reporting. Review unfinished work before disabling.

Sprints, Projects, and Views

Use a Sprint for a time box.

Use a Project for an outcome that may span several Sprints or Spaces.

Use a View for a saved way to inspect tasks.

A task can belong to a Project and a Sprint while appearing in multiple Views.

Enable Sprints for a Space#

Automatic cadence#

Manual mode#

Sprint states#

Add tasks to a Sprint#

Scope, progress, and capacity#

Change Sprint dates#

Switch modes or disable Sprints#

Sprints, Projects, and Views#