| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="-JGaSKq8Cd3WrAqkPLTUUGg" |
| name="new_artifact,_rU4H4F8fEd22Gu98eFOlrQ" guid="-JGaSKq8Cd3WrAqkPLTUUGg" changeDate="2008-07-31T12:44:26.578-0400"> |
| <mainDescription><p>
 |
| The task board shows all the work the team is&nbsp;doing during a sprint. It is updated&nbsp;continuously throughout
 |
| the sprint–if someone thinks of a new task they&nbsp;write a new card and puts it on the board. Either during or
 |
| before&nbsp;<a class="elementLink" href="./../../Scrum/tasks/the_daily_scrum_C8FB7908.html"
 |
| guid="_oSM0AOF-Edyp34pwdTOSVQ">The Daily Scrum</a>, estimates are changed (up or down) and cards are moved around the
 |
| board.
 |
| </p>
 |
| <p>
 |
| The task board might look like this:
 |
| </p>
 |
| <p>
 |
| <span class="articleImage"><img style="WIDTH: 461px; HEIGHT: 336px" height="447" alt=""
 |
| src="resources/MockedTaskBoard.jpg" width="600" /><a
 |
| href="http://www.mountaingoatsoftware.com/system/hidden_asset/file/29/MockedTaskBoard.jpg"><u><font
 |
| color="#0000ff">&nbsp;</font></u></a></span>
 |
| </p>
 |
| <p>
 |
| <span class="articleImage"><br />
 |
| &nbsp;</span>
 |
| </p>
 |
| <p>
 |
| Each row on the task board is a product backlog item (in this&nbsp; particular example stories). During the <a
 |
| class="elementLinkWithUserText" href="./../../Scrum/tasks/sprint_planning_meeting_9F0B8F28.html"
 |
| guid="_4gCKAOF9Edyp34pwdTOSVQ">sprint planning meeting</a> the team selects the product backlog items they can complete
 |
| during the coming sprint. Each product backlog item is turned into multiple <a class="elementLinkWithUserText"
 |
| href="./../../Scrum/workproducts/sprint_backlog_7A5B8A37.html" guid="_Q5Ki8OF8Edyp34pwdTOSVQ">sprint backlog</a> items.
 |
| Each of these is represented by one task card that is placed on the task board. Each task card starts on the task board
 |
| in the “To Do” column. The columns are:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <b>Story</b>–The story description (“As a user I want to…”) shown on that row.
 |
| </li>
 |
| <li>
 |
| <b>To Do</b>–This holds all the cards that are not done or in process.
 |
| </li>
 |
| <li>
 |
| <b>Work In Process</b>–Any card being worked on goes here. The programmer who chooses to work on it moves it over
 |
| when she’s ready to start the task. Often this happens during the Daily Scrum when someone says, “I’m going to work
 |
| on the boojum today.”
 |
| </li>
 |
| <li>
 |
| <b>To Verify</b>–A lot of tasks have corresponding test task cards. 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. Some task cards don’t often get corresponding test cards
 |
| (“Fix Bug #321 in Bugzilla”) so those are placed in the “To Verify” column.
 |
| </li>
 |
| <li>
 |
| <b>Done</b>–Cards pile up over here when they’re done. They’re removed at the end of the sprint.
 |
| </li>
 |
| </ul></mainDescription> |
| <purpose>Tangibly communicates progress&nbsp;across team members and stakeholders.</purpose> |
| <representationOptions>There are many different ways to implement a task board.&nbsp; Co-located teams may use a wall.&nbsp; Distributed teams
 |
| will use some kind of tool.</representationOptions> |
| </org.eclipse.epf.uma:ArtifactDescription> |