Kodavara Guide
ClickUp Sprint Setup: Run Agile Sprints Without the Spreadsheet
ClickUp Sprints is a ClickApp that an Admin switches on. It groups sprints in a Sprint Folder with shared settings, supports sprint points, shows burndown and burnup charts and lets you move unfinished work to the next sprint. Sprint Cards and Sprint Automations need Business or above. This guide shows what you get and the configuration we build.
Last reviewed October 2026. ClickUp changes often, so check ClickUp's help center for the latest. Written by Kodavara, an independent ClickUp Partner. Not published or endorsed by ClickUp.
What ClickUp Does Today
What You Can Do Natively
Start with the features available on your ClickUp plan.
Sprint Folders
Sprints live in a Sprint Folder that shares settings. You can customise settings per Folder or per sprint, and sprint length is customisable.
Sprint Points
Points roll up from subtasks and can be broken out by assignee. Usage of Sprint Points is capped on lower plans and unlimited on Business and above.
Charts
Burndown and burnup charts show progress. Sprint Cards for Dashboards need Business or above.
Spillover
Unfinished tasks appear in a banner at the end of a sprint, and you can move them to the next sprint. Sprint Automations, on higher plans, can also move work.
Where It Falls Short
The Gaps People Run Into
If these are your problem, keep reading.
- Only Admins can enable Sprints and set the Workspace defaults, so set aside time with your admin.
- Guests cannot create sprints, but they can add tasks to sprints and work on them.
- Sprint Automations and Sprint Cards are not on the lowest plans, so check yours before designing around them.
- Rollover is something to configure and test, not something to assume.
- Backlog hygiene and a definition of done matter more than any setting, so the build includes working agreements.
Worked Example
Example: A Sprint Folder
A typical product team. Values are illustrative.
| Setting | Choice | Why |
|---|---|---|
| Sprint length | Two weeks | Matches release rhythm |
| Points field | Sprint points on parent tasks | Estimate at the story level |
| Statuses | Backlog, Ready, In Progress, In Review, Done | One shared board |
| Spillover | Reviewed in the sprint review, then moved | Nothing rolls over unnoticed |
| Backlog | A separate List sorted by priority | Planning starts from one place |
Sample data for illustration.
The Configuration
The Configuration: What We Build and Monitor
Built around your release process and team size.
| Layer | What We Build | What We Watch |
|---|---|---|
| Sprint Folder | Defaults for length, statuses, points and spillover that every sprint inherits | Sprints that diverge from the defaults |
| Backlog | A refinement flow with Ready criteria, priorities and an intake route for bugs and requests | A backlog nobody trusts |
| Estimation | A points scale and who estimates, with subtasks rolling up | Unestimated work in sprints |
| Statuses and Automations | Statuses matched to your workflow, with automations on your plan to move and notify | Automation allowance and failures |
| Dev Tool Links | GitHub or GitLab linking by task ID so pull requests move tasks | Work without IDs |
| Reporting | A sprint dashboard with burndown, completed points and carryover | Carryover that grows each sprint |
How Kodavara Consulting Does It
Set It Up Once
We set up the Sprint Folder and the working agreements around it.
Agree How You Work
We capture your cadence, ceremonies and definition of done.
Enable and Configure Sprints
We switch on the ClickApp and set the Folder defaults.
Build Backlog and Intake
We build the backlog flow and the route for bugs and requests.
Connect Dev Tools and Dashboards
We link repositories and build the sprint dashboard.
Run a Pilot Sprint
We support the first sprint and adjust.
FAQ
Common Questions
Not here? Ask us.
How do I turn on Sprints in ClickUp?
An Admin enables the Sprints ClickApp. Members can then create sprints in a Sprint Folder.
Does ClickUp have burndown charts?
Yes, burndown and burnup charts. Sprint Cards for Dashboards need Business or above.
What happens to unfinished tasks?
They appear in a spillover banner and can be moved to the next sprint. Sprint Automations can also move them on higher plans.
Are there plan limits?
Yes. Sprint Points usage is capped on lower plans, and Sprint Cards and Automations need Business or above.
Can developers link pull requests?
Yes, through the GitHub and GitLab integrations using task IDs. See our GitHub and GitLab guide.
Can you set this up for our team?
Yes, including a supported pilot sprint.
Keep Reading
Related Guides
GitHub and GitLab
ClickUp has native GitHub, GitLab and Bitbucket integrations.
Read the Guide →GuideJira
ClickUp has a one-time Jira import, not a native ongoing sync.
Read the Guide →GuideMigrate From Jira
How to migrate from Jira to ClickUp: the native importer, the field and status mapping, what is lost, such as sprints, and a plan for a clean switch.
Read the Guide →ServiceKodavara Consulting
The Kodavara service behind this guide: what we assess, configure and hand over.
Learn More →Want Help Setting This Up?
Tell us what you are trying to get done and we will point you at the fastest route.