How to Set Up an Agile Board in ClickUp

Create a ClickUp Space for your team (e.g., 'Product Engineering') with Lists that represent your work streams. For most teams, start with three Lists: 'Product Backlog' (groomed items not yet in a sprint), 'Current Sprint' (active sprint work), and 'Done' (completed items archived by sprint). This structure separates planning from execution — the backlog is the PM's domain; the sprint board is the team's domain.

• Enable the Sprint feature in your Space settings to use ClickUp's native sprint management
• Create a 'Tech Debt' list for non-feature work that needs separate tracking and prioritization

Replace ClickUp's default statuses with a workflow that matches how your team actually works. A solid starting set: To Do, In Design, In Development, Code Review, QA, Done. Add 'Blocked' as an additional status available at any stage. Keep the total number of statuses under eight — too many creates confusion about which status to use, and items get stuck in ambiguous states.

• Assign colors to each status that create a visual gradient from cool (To Do) to warm (Done) for intuitive scanning
• Add 'Blocked' as a distinct color (red) so blocked items are immediately visible on the board

Create a Board view of your Current Sprint list grouped by Status. This is the view your team uses in daily standups. Configure it to show: assignee avatar, priority flag, story point estimate, and due date on each card. Enable WIP (Work in Progress) limits on the 'In Development' and 'Code Review' columns to prevent overload — a typical limit is two items per developer in progress at once.

• Enable card subtask counts so the board shows completion progress for larger items
• Add a 'Group by Assignee' toggle so individual team members can quickly see their own workload

Use ClickUp's Sprints feature to create time-boxed iterations (typically two weeks). During sprint planning, drag items from the Product Backlog into the sprint until you reach your team's capacity. ClickUp tracks sprint velocity automatically — after three sprints, you'll see an average that helps predict future capacity. At sprint end, any incomplete items automatically roll over to the next sprint.

• Add custom fields for Story Points (number) and Sprint Goal (text) to track estimates and sprint objectives
• Use ClickUp's Workload view during planning to ensure no team member is over-allocated

Create additional views beyond the sprint board to support different needs. A Table view of the backlog sorted by priority helps PMs groom and prioritize. A Calendar view shows items with due dates to spot scheduling conflicts. A Box view (grouped by assignee) helps managers check workload distribution. A Gantt view of the backlog shows dependency chains and timeline estimates. Each view serves a specific meeting or decision context.

• Create a 'Sprint Metrics' dashboard with widgets for velocity trend, burndown chart, and status distribution
• Add a filtered view for 'Blocked Items' across all lists so blockers are visible without scanning the entire board

Set up ClickUp automations to reduce manual board hygiene. Useful automations include: when status changes to 'Code Review,' assign the reviewer automatically; when a subtask is completed, update the parent task's progress; when an item is marked 'Blocked,' send a Slack notification to the team channel; when priority is set to 'Urgent,' move the item to the top of the list. Start with three to five automations and add more as you identify repeated manual steps.

• Create an automation that assigns a 'Stale' tag to items that haven't been updated in 3 days during an active sprint
• Set up an end-of-day automation that posts a sprint progress summary to your team's Slack channel