| <?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="-r4CP_1w3uk0ClgSnUrm80w" |
| name="new_artifact,__uNYkPVgEdyMdecrgpMbRg" guid="-r4CP_1w3uk0ClgSnUrm80w" changeDate="2008-07-30T14:57:59.796-0400"> |
| <copyrightStatement href="uma://_6Ab_EOF4Edyp34pwdTOSVQ#_4kVeYOGBEdyp34pwdTOSVQ"/> |
| <mainDescription><p>
 |
| Scrum requires that each sprint deliver a potentially shippable product increment.&nbsp; The increment must consist of
 |
| thoroughly tested code that has been built into an executable, and the user operation of the functionality is
 |
| documeneted&nbsp;either in Help files or user documentation.
 |
| </p></mainDescription> |
| <keyConsiderations><p>
 |
| There is much debate&nbsp;about the difference between "potentially shippable (done)" and&nbsp;"shippable".
 |
| </p>
 |
| <p>
 |
| Mike Cohn states:
 |
| </p>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p>
 |
| .. "potentially shippable" and "shippable" are not the same thing. Some large or complex projects will require the
 |
| use of "release sprint" or "hardening sprint" at the end of a release cycle (say 6 two-week sprints then a 2-week
 |
| release sprint). The release sprint is not a dumping ground for sloppy work; rather it is a place where some
 |
| hardening of the system can occur.
 |
| </p>
 |
| </blockquote>
 |
| <p>
 |
| One thing is clear Scrum teams&nbsp;need to agree&nbsp;on their definition of "potentially shippable"
 |
| and&nbsp;"shippable" and to&nbsp;come to a shared&nbsp;understanding with the Product Owner.
 |
| </p></keyConsiderations> |
| </org.eclipse.epf.uma:ArtifactDescription> |
