A task board is a powerful information radiator that transparently radiates the Sprint Backlog.  It represents a visual depiction of tasks grouped by backlog item. Teams use the task board during the daily Scrum to discuss their day’s plan.

tb.png

Standing in front of the task board for doing a daily Scrum helps teams adhere to the time-box. It is updated by team members periodically. The task board is a simple but powerful way to communicate Sprint progress at a glance. Formally, the task board shows the evolving state of the Sprint Backlog over time.

tb.png

Tips for maintaining an effective task board.

  • Use different color sticky notes for different types of tasks like development, testing, code review so that the board radiates the information in a meaningful way.
  • Have a separate color for working on unplanned items so that at the end of the Sprint, one can make out the amount of unplanned work done by just looking at the board
  • Have a separate column for impediments and make all impediments visible, assign an owner for each impediment and tag it with the user story ID.
  • Have meaningful swim lanes that make their flow visible.
  • Have the planned leaves, violations, working agreements, DOD, DOR, Retrospective action items visible and updated in the team space near the task board.
  • Order the backlog items on the task board with respect to the priority from top to bottom.
  • Have burndown chart drawn physically beside the task board.

Listed below are some of the anti-patterns of the task boards:

tb1.png

Advertisements