ClickUp gives you enough rope to build a beautiful sprint workflow or to strangle the team in configuration options nobody agreed on. Most ClickUp sprint setups fail not because the tool is bad but because teams over-architect the structure before they understand the tool. This tutorial covers the exact configuration we have run on three different companies - between 20 and 50 people - with strong, sustainable results across 12+ sprint cycles.
The pieces you actually need
One Space per organization. One List per team function (Engineering, Design, GTM) - not one List per project. Custom statuses: Backlog, Ready, In Progress, In Review, Done. Custom fields on every task: Sprint (dropdown), Effort (number, Fibonacci values 1/2/3/5/8), Owner (people picker), Type (Bug/Feature/Chore). That is it. Anything you add beyond this needs a specific reason.
Step 1: Create the Space correctly
Name the Space after the company, not the product or a team. Create it as a single shared Space, not one Space per department. This sounds counterintuitive but it matters: search, dashboards, and cross-team linking all degrade when you split into multiple Spaces. Inside the Space, create three Lists: Engineering, Design, and GTM. Give each List its own color and icon so the sidebar stays readable at a glance. Set default view to Board for Engineering and List for GTM.
Step 2: Enable and configure Sprints
Go to Space Settings - ClickApps - Sprints and enable the Sprints ClickApp. Configure 2-week cycles starting on a Monday. Enable auto-rollover for incomplete tasks - this saves you 20 minutes of manual dragging every other Friday. Name your first sprint by quarter and number: Q2-01, Q2-02, and so on. Avoid date-based sprint names - they look messy in reports after six months of accumulation.
Step 3: Build the Sprint Board view
Inside the Engineering List, add a Board view. Group by Status, filter by Sprint = current (use the dynamic filter, not a hardcoded sprint name). Pin this view as the default tab. This is the view the team checks daily. Add a second view called Backlog: List view, no sprint filter, sorted by Effort descending. This is what the PM uses to prioritize for the next sprint. Add a third view called My Tasks: List view, filtered by Owner = current user. People check this in the morning.
Step 4: Capacity planning with Effort fields
In the Sprint Board view, add the Effort field to the card layout so it shows on every card. Before sprint planning, sum the Effort scores on tasks marked Ready. A healthy 2-week sprint for one engineer is roughly 20-25 Effort points (assumes some overhead, unexpected issues, and time off). If you are planning 40+ points per engineer, you are setting yourself up for a miss. Use the Dashboard widget - add a Summary widget showing total Effort in the current sprint filtered by owner. Review this in planning, not after the sprint starts.
Step 5: Automations that save time every sprint
Set up three automations in ClickUp: First, when a task status changes to Done, automatically log a comment with the completion timestamp. Second, when a task is assigned to a Sprint and has no Effort score, send a comment asking the owner to add one. Third, when a sprint ends, move all tasks with status Backlog or Ready back to the sprint backlog list automatically. These three automations eliminate about 30 minutes of sprint admin per cycle. ClickUp allows 1,000+ automations per month on Business plans - use them freely.
Integrations worth setting up
Connect ClickUp to your GitHub or GitLab repository via the ClickUp native integration. This pulls commit messages and PR status into the task timeline so the team can see code progress without context switching. Connect Slack via the ClickUp Slack app and configure it to post to a sprint channel when any task moves to Done - gives the team a passive feed of what shipped without requiring anyone to update a status meeting. Both integrations take under 15 minutes to configure.
Retro cadence that actually works
Every other Friday at 4 PM for 30 minutes maximum. Open the Dashboard with the sprint summary visible: tasks completed, tasks rolled over, effort planned vs delivered. Run three prompts in order: what shipped (name specific tasks), what stalled and why (root cause, not blame), and what to kill from the backlog (ruthless prioritization). Record outcomes as tasks in the next sprint immediately - if an action item does not become a task in ClickUp before the retro ends, it will not happen. Keep retro notes in a Docs file linked to the sprint for reference.
Common pitfalls to avoid
Do not use ClickUp Goals for sprint tracking. Goals are a separate system and create confusion about whether sprint completion and Goal progress are the same thing. They are not. Do not let individual team members create sub-Lists inside the team List - this fragments views and breaks Dashboard aggregations. Do not import from Jira. The data model maps badly and you inherit Jira configuration debt. Start clean with the structure above and migrate only active in-progress items manually. See our ClickUp deal for current negotiated pricing on Business plans.
