| <?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.4/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmi:id="-v5-z0Dm_JF0P2xtKd0FDrA" |
| name="new_artifact,_OZIPIOF8Edyp34pwdTOSVQ" guid="-v5-z0Dm_JF0P2xtKd0FDrA" changeDate="2008-03-18T20:39:19.656-0400"> |
| <copyrightStatement href="uma://_6Ab_EOF4Edyp34pwdTOSVQ#_4kVeYOGBEdyp34pwdTOSVQ"/> |
| <mainDescription><p>
 |
| When a project is initiated there is no comprehensive, time-consuming effort to write down all foreseeable tasks or
 |
| requirements. Typically, a project writes down everything obvious, which is almost always more than enough for a first
 |
| sprint. The Product Backlog is then allowed to grow and change as more is learned about the product and its customers.
 |
| </p>
 |
| <p>
 |
| During the <a class="elementLink" href="./../../Scrum/tasks/sprint_planning_meeting_9F0B8F28.html"
 |
| guid="_4gCKAOF9Edyp34pwdTOSVQ">Sprint Planning Meeting</a> the <a class="elementLink"
 |
| href="./../../Scrum/roles/product_owner_10E7BD3.html" guid="_QcnRMOF5Edyp34pwdTOSVQ">Product Owner</a> prioritizes the
 |
| items in the Product Backlog and describes them to the team. The team then determines which items they can complete
 |
| during the coming Sprint. The team then moves items from the Product Backlog to the <a class="elementLink"
 |
| href="./../../Scrum/workproducts/sprint_backlog_7A5B8A37.html" guid="_Q5Ki8OF8Edyp34pwdTOSVQ">Sprint Backlog</a>. In
 |
| doing they expand each Product Backlog item into one or more Sprint Backlog tasks so they can more effectively share
 |
| work during the Sprint. Conceptually, the team starts at the top of the prioritized Product Backlog list and draws a
 |
| line after the lowest of the high priority items they feel they can complete. In practice it is not unusual to see a
 |
| team select, for example, the top five items and then two items from lower on the list but that are associated with the
 |
| initial five.
 |
| </p>
 |
| <p>
 |
| Product backlog items can be technical tasks ("Refactor the Login class to throw an exception") or more user-centric
 |
| ("Allow undo on the setup screen"). A very interesting prospect is expressing Scrum backlog items in the form of
 |
| Extreme Programming's User Stories.
 |
| </p>
 |
| <p>
 |
| The Product Backlog can be maintained in an Excel spreadsheet. An example from a real project is shown below. This
 |
| Excel spreadsheet shows each product backlog item assigned a general priority (Very High, High, etc.) by the Product
 |
| Owner. Estimates have been developed by the developers but it is understood that they are very imprecise and are useful
 |
| only for rough assignments of tasks into the various sprints.
 |
| </p><img height="482" alt="" src="resources/productbacklog.jpg" width="500" /></mainDescription> |
| </org.eclipse.epf.uma:ArtifactDescription> |
