Optionally, we sometimes use the following columns on a Scrum task board, depending on the team, the culture, the project and other considerations: Sometimes we remove some or all during a sprint if there are a lot of cards. They're removed at the end of the sprint. Done: Cards pile up over here when they're done.321 in Bugzilla”) so those are placed in the “To Verify” column. Some task cards don't get corresponding test cards (“Fix Bug No. So, if there's a “Code the boojum class” card, there is likely one or more task cards related to testing: “Test the boojum”, “Write FitNesse tests for the boojum,” “Write FitNesse fixture for the boojum,” etc. To verify: A lot of tasks have corresponding test task cards.Often, this happens during the daily scrum when someone says, “I'm going to work on the boojum today.” The programmer who chooses to work on it moves it over when she's ready to start the task. Work in process: Any card being worked on goes here.To do: Place for all cards that are not in the “Done” or “In Process” columns for the current sprint.Story: The story description (“As a user we want to…”) shown on that row.The columns we generally use on a taskboard are:
![taskboard tfs taskboard tfs](http://blog.qetza.net/wp-content/uploads/2011/05/taskboard.png)
Each task card starts on the Scrum taskboard in the “To Do” column.
![taskboard tfs taskboard tfs](https://i.stack.imgur.com/Zj99o.png)
Each of these is represented by one task card that is placed on the Scrumboard. Each product backlog item is turned into multiple sprint backlog items. During the sprint planning meeting, the team selects the product backlog items they can complete during the coming sprint. As an example, the Scrumboard looks like this:Įach row on the Scrum board is a user story, which is the unit of work we encourage teams to use for their product backlog.