Sprints

​

Feature overview

Sprints let your team organize work into focused, time-boxed periods within a project. By enabling Sprints on a project, you can create named sprints with defined start and end dates, track their progress through a lifecycle of statuses, and run multiple sprints in parallel when your team works across separate tracks or workstreams. Sprints are enabled per project. Any team member can turn Sprints on for a project; turning Sprints off requires team admin access. A project can hold any number of sprints at any time.

​

When to use

When your team works in iteration cycles. If your team plans and delivers work in regular time-boxed cycles — weekly, biweekly, or monthly — Sprints give each cycle a defined name and date boundary so you can track what belongs to each period. When you manage parallel workstreams. Teams running separate tracks (for example, one for frontend and one for backend) can maintain simultaneous active sprints to keep each workstream’s scope distinct. When you want to close out a period of work. Completing a sprint signals that the planned period has ended, creating a clear record of past cycles.

​

How to use

​

Enabling Sprints on a project

1. Open the project in Tasket.
2. Navigate to the project settings.
3. Turn on the Sprints toggle.

Any team member can enable Sprints. To disable Sprints, you must be a team admin.

​

Creating a sprint

Once Sprints is enabled for a project:

1. Go to the Sprints section of your project.
2. Create a new sprint.
3. Give it a name (for example, “Sprint 1” or “Oct 5 – Oct 16”).
4. Set a start date and end date.

Sprints do not have a required naming format. Teams commonly use sequential numbering (“Sprint 1”, “Sprint 2”) or date ranges to make sprint periods easy to identify at a glance.

​

Sprint statuses

Each sprint moves through the following statuses: A project can have multiple Active sprints at the same time.

​

Completing a sprint

When the sprint period ends, complete the sprint to mark it as closed. Completed sprints remain visible as a record of past work cycles.

​

FAQ

Can I have more than one active sprint at a time? Yes. A project can have multiple active sprints simultaneously. This is useful for teams running parallel workstreams or separate tracks within the same project. Who can enable or disable Sprints? Any team member can enable Sprints on a project. Disabling Sprints requires team admin access. Can I rename a sprint after creating it? Sprints can be given any name when created. Renaming behavior after creation is not confirmed and is not covered here. Is there a limit on how many sprints a project can have? No confirmed limit. Projects in use have accumulated eight or more sprints across active and completed states. Are Sprints available on all projects? Sprints must be enabled per project. They are independent of other project features such as Stages and Custom Fields.

​

Troubleshooting

I don’t see the option to disable Sprints. Disabling Sprints requires team admin access. If you are not a team admin, ask a team admin to disable it. I can’t find the Sprints section in my project. Sprints must be enabled in project settings before the Sprints section appears. Check whether Sprints has been turned on for that project.