Scrum

A ready-to-run Scrum board with ceremonies, sprint tracking, WIP limits, and engineering task categories.

About this template

This template maps the Scrum rhythm into a board you can run immediately. It includes a Ceremonies lane (planning, standups, review, retro) plus a Sprint Results area to keep outcomes and learnings visible across cycles.

Active workflow columns have WIP limits to prevent overload and keep the team focused on finishing work before pulling more in.

Use Sprint Number plus Estimated/Logged time fields to track capacity and spot gaps between planning and reality — without overengineering your process.

What's inside

Columns included

NotesCeremoniesBacklogTodoIn progressReviewTestingDoneSprint results

Task types

UrgentBugBlockedInfoFrontendBackendAPIDatabaseDevOpsUI/UX

Custom fields

Sprint number⏱️ Estimated time⏳ Logged time

Key features

  • Scrum-ready columns (incl. Ceremonies + Sprint Results)
  • WIP limits on active stages to reduce overload
  • Sprint number + Estimated vs Logged time fields
  • Engineering task categories (Frontend/Backend/API/DevOps, etc.)
  • Great for sprint planning and execution

Who is this template for?

  • Scrum teams
  • Agile software teams
  • Product development teams
  • Teams running sprints with reviews/retros
  • Engineering squads needing better flow control

How to use this template

Use this board as your sprint operating system: plan the sprint, keep active work constrained, and review estimation accuracy at the end of each cycle.

Step 1

Sprint planning

Start in the Notes and Ceremonies columns. Use Notes for backlog prep, scope assumptions, and sprint goals. Use Ceremonies to create cards for Sprint Planning, Daily Scrum, Sprint Review, and Retrospective so the team can see the full rhythm of the sprint in one place.

Step 2

Execution and flow control

Move committed work through Todo, In progress, Review, Testing, and Done. Keep WIP limits visible on In progress and Review to prevent multitasking and half-finished work from piling up. This is what makes the board operational, not just visual: the team finishes work before pulling more.

Step 3

Tracking velocity

Use Sprint number together with Estimated time and Logged time to compare planned effort against actual effort. Review the gaps at the end of each sprint to improve forecasting, rebalance future commitments, and spot work that repeatedly takes longer than expected.

Compare this template

Explore how this scrum workflow compares with other tools across real use cases.

Ready to get started?
Learn how to create a board from this template in just a few steps.
Read the step-by-step guide

Frequently asked questions

What columns are included?

A Scrum-friendly flow plus Ceremonies and Sprint Results to keep rituals and outcomes visible.

What are WIP limits for?

They cap the amount of work allowed in active stages like In progress and Review, which reduces multitasking, exposes bottlenecks faster, and helps the team finish work before starting more.

Can I track sprint velocity?

Yes. Sprint Number plus Estimated time and Logged time gives a practical baseline for comparing planned effort with actual effort across sprints.

How do I handle unplanned work?

Use a dedicated Urgent task type and make scope trade-offs explicit: every urgent item should displace or re-prioritize something else so the sprint stays honest.

How do I run retros here?

Create Retro items in Ceremonies and move action items into the main flow so learnings become work.

Related templates