This board is the Sprint Board framework: the standard single-team Scrum setup, ready to run. The five columns map the flow every Scrum team knows, from Backlog through To Do, In Progress, and Review to Done. What makes it more than a blank board is what is wired in: sprint boundaries, WIP limits, and an automatic burndown that most teams have to assemble by hand.<\/p>\n
It lives in ClickUp because a Scrum board is only useful if it reflects real work in real time. Cards are actual tasks with assignees, story points, and statuses, so moving a card is the same act as updating the work. There is no separate tracker to keep in sync and no end-of-day reconciliation between the board and reality.<\/p>\n
The Sprints feature gives the board its time boxes. You set a two-week range, pull ranked backlog items in until the point total matches your velocity, and the board keeps that sprint’s work distinct from the open backlog. WIP limits on each column are the discipline most teams skip: when In Progress hits its cap and turns red, it is a prompt to finish something before starting something new, which is the entire mechanism behind flow and the reason cycle times drop when teams actually honor it.<\/p>\n
The burndown widget plots remaining story points against the ideal line and updates the moment a card hits Done. Halfway through the sprint, it answers the only question that matters at that point: are we going to make it. Because it reads live task data, nobody has to rebuild a chart before standup, and the team has an honest signal to act on rather than a gut feeling.<\/p>\n
Plan by pulling ranked backlog cards into the sprint up to your velocity, then work the board left to right through the two weeks, respecting the WIP caps. Use the burndown at standup to decide whether to pull in more work or flag a risk early. At sprint end, the completed points feed your velocity for the next planning session, so each sprint makes the next one more accurate.<\/p>\n
Rename columns if your flow has a separate QA or staging step. Adjust WIP limits to your team size, since smaller teams run tighter caps. If you size in hours rather than points, relabel the Story Points field and the burndown follows. Keep the board to one team, though, because the moment you are coordinating several teams, the portfolio version is the right tool and this one starts to creak.<\/p>\n
This board is built for a single team of roughly five to nine people. If you run a Scrum of Scrums across three to five teams, with program epics and cross-team dependencies, the Portfolio Scrum Board variant rolls all of that up without cramming multiple teams onto one board that was never designed to hold them.<\/p>\n","protected":false},"excerpt":{"rendered":"