Agile concepts: the Scrum Task Board

The Scrum Task Board

In Scrum the task board is a visual display of the progress of the Scrum team during a sprint. It presents a snapshot of the current sprint backlog allowing everyone to see which tasks remain to be started, which are in progress and which are done.

Other flavours of Agile like XP and Kanban also use task boards but here I’ll present the Scrum version.

The layout of a task board

Simply put, the task board is a physical board on which the user stories which make up the current sprint backlog, along with their constituent tasks, are displayed. Usually this is done with index cards or post-it notes.

The task board is usually divided into columns. An example that some teams use is:

  • Stories – this column contains a list of all the user stories in the current sprint backlog
  • Not started  – this column contains sub tasks of the stories that work has not started on
  • In progress – all the tasks on which work has already begun
  • Done – all the tasks which have been completed

As the sprint progresses the cards on which individual tasks are written will move from left to right. Once all the tasks for a particular user story are done, the user story itself should meet the definition of done and can be moved to the ‘Done’ column.


Often the sprint goal will also be displayed on or near the task board. Depending on the nature of your team and whether you’re working at a story or task level there may also be columns for testing and possible Product Owner review.

In general though the Scrum view would be that the team is doing whatever it needs to do as a team to take a user story from Ready to Done and therefore splitting up team subdiciplines is unnecessary.

Using the Scrum task board

The task board is a useful visual tool which provides an at-a-glance reference for both the Scrum team and stakeholders. It provides a daily reminder of the sprint goal and the work to which the Scrum team has committed.

The daily Scrum meeting should be held at the task board so that as members update the team on their progress tasks can be physically moved across the board. This not only helps the team maintain a sense of momentum but also provides a neat visualisation of where the team is at in the sprint, which tasks are still outstanding and which have been completed.

The task board also allows for variation in the format of the daily Scrum e.g. updating on a task-by-task basis rather than going around the team one member at a time. Variations like this should be used sparingly  and where a benefit has been identified.

Digital task boards

The ScrumMaster will usually take responsibility for setting up and maintaining a physical task board but shouldn’t act as a gatekeeper – all team members should be able to access and update the board.

There are many digital alternatives to an analogue board, e.g. those created by tools like JIRA and VersionOne, which allow the collaborative management of the task board with tracked changes, copious notes, attachments etc.

Such boards can be incredibly useful – especially for the ScrumMaster and Product Owner during sprint planning, backlog refinement, tracking velocity over time – and sometimes, in the case of teams which are located on multiple sites, even essential.

But I’d still recommend the use of physical boards alongside digital boards. They’re a useful collaborative and visual tool for a team, facilitate better daily Scrums and offer much more transparency to stakeholders.

Leave a reply

You can use these tags:

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

  1. Agile values individuals and interaction over tools and process to try to co-locate the team in a dedicated war room with a big white board and a half dozen dry-erase markers. Keep it simple, light and agile.

    • ozzy85 says:

      Easy to say agile values individuals and interactions over tools. Try co-locating a geographically distributed team working across multiple time zones into a war room with a white board. Not gonna happen. This is where tools come in handy. Anybody can do agile with a 5 member team – the challenge is in scaling it.

  2. sibusiso says:

    Hi. Thanks for the great information. I got here trying to find the available options for updating the scrum board. e.g.: once a day during stand up, or during the day when progress is made. what are the options called.

  3. […] from agile project management, a pipeline can be set up as a Scrum board with a few more stages. It follows the To-do > In Progress > Done linear progression. To […]

  4. Dim says:

    In our company, the board looks a little different: Backlog, In sprint, In progress, Done, Testing, Production. BTW, it is very convenient to use this board for daily stand-ups. Just looking at and write a brief report in Standuply. It is quite convenient. The main thing is not to create too many cards, otherwise moving them around the board can take half a day. Lol. Standuply is an application in Slack for project management. Highly recommended for review, guys. https://standuply.com

  5. Thank you very much for this insightful article.
    We’ve developed Draft.io as a visual and highly flexible support, inherently collaborative. Let’s have a look at the following example if you’re wondering how to build a Scrum Board in digital: https://draft.io/example/scrum-board

    Hope it will be useful for some of you!

  6. Fatollah Youssefifar says:

    when is the task board updated – during the standup meeting or before?

    • Gemma Reeve says:

      Hi Fatollah, the task board is updated frequently, but most commonly during the daily meeting (based on the team’s progress since the last update).

  7. […] qué no disponer en la sala de algo parecido a un scrum board? Desde luego, las ventajas de la gestión visual de estos tableros han sido demostradas. Cada ítem […]

  8. Dovile says:

    If you are looking for a visual and flexible Scrum tool, we have just launched one. Teamhood is an Agile inspired project management solution that supports Scrum application. See more .

  9. […] 圖片來源:Agile concepts: the Scrum Task Board […]

  10. Myles McHugh says:

    “But I’d still recommend the use of physical boards alongside digital boards.” – Double accounting doing the same thing twice where one board will not get updated causing mass confusion. Wasted effort – NOT Agile.

  11. Sharad says:

    Can someone please tell me what each color represents?

Sign up for the Manifesto newsletter and exclusive event invites