

Having a Task Board also helps give physical focus to software development which is inherently nonmaterial. The Burndown chart should be on or near the Task Board because the two will be closely correlated (hopefully!) and the ‘done’ conditions help remind everyone what it really means to move a task into the ‘done’ column. Figure 2 : A more sophisticated Task Boardįor an even greater benefit, two dedicated spaces can be allocated, one for the Burndown chart and one for the ‘done’ conditions.The information is displayed in a 2-dimensional matrix with rows representing User Stories and columns representing various status values, which should be, at a minimum: Any basic wall surface with removable, non - mark ing labels.Metal surfaces with paper and magnets, or.

White boards, windows, large pieces of paper or large plastic wall calendars, all with reusable sticky notes,.Almost all surfaces are suitable for some kind tape to create the lines, but the method of displaying notes or cards can vary by surface. The surface area doesn’t really matter provided it is relatively large, that horizontal and vertical lines can be placed on it, and that notes of some kind can be attached. It is important that the every team member feel they share ownership of the Task Board it is representative of the teamwork necessary to succeed and shows that each individual is responsible for that success (or even failure.) Creating a Task Board Manager’s offices and conference rooms are not good locations as they are not always accessible. It is important that the Task Board be somewhere visible to as many team members as possible and always accessible to all usually a large wall or window (be creative). There can be exceptions such as reminders, technical notes or other data that needs to be easily available and persists across iterations, although such information is not strictly part of the Task Board. Typically, a Task Board displays only information pertinent to the current sprint and will be cleared off before the next sprint begins. A Task Board is the focal point of any Agile project and serves as a good place at which to hold the stand-up meeting or Scrum. The Task Board is perhaps the single most useful, and arguably most important, device that can be used on Agile projects, often described as an ‘information radiator’ because it gives out the information to everyone from a central location.
