| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription 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="-ViT5-mwkNqQP_VFaDwNqQQ" |
| name="category_artifacts,_xTvFAESFEdyiFM7u0Ics5g" guid="-ViT5-mwkNqQP_VFaDwNqQQ" |
| authors="Lyndon Washington" changeDate="2007-08-06T18:31:19.274-0700"> |
| <copyrightStatement href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_N8zs0AEGEduzRosbOajx7w"/> |
| <mainDescription>Within Scrum there are three main artifacts that are used by the roles to convey information about the product that is |
| being built, the tasks that are necessary to build the specified features and the increments of functionality.<br /> |
| <br /> |
| Clearly stipulating what these base artifacts are, and the owners of the artifacts will establish an understanding of the |
| roles and their responsibilites within the process for managing the product, project and process.<br /></mainDescription> |
| <keyConsiderations>The list of artifacts is not exhaustive, but does represent the key components to a Scrum process.<br /></keyConsiderations> |
| </org.eclipse.epf.uma:ContentDescription> |
