| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:PracticeDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-WOrmi0u1gYsdoetUWXbIEg" name="production_release,_IAG5wOB-EeC1y_NExchKwQ" guid="-WOrmi0u1gYsdoetUWXbIEg" changeDate="2011-10-15T12:04:55.657-0700" version="7.5.1"> |
| <mainDescription><p>
 |
| Mike Cohn, noted author on Scrum, states:
 |
| </p>
 |
| <blockquote style="MARGIN-RIGHT: 0px" dir="ltr">
 |
| <p class="quote">
 |
| ..."Some large or complex projects will require the use of "release Sprint/Iteration" or "hardening
 |
| Sprint/Iteration" at the end of a release cycle (say 6 two-week Sprint/Iterations then a 2-week release
 |
| Sprint/Iteration). The release Sprint/Iteration is not a dumping ground for sloppy work; rather it is a place where
 |
| some hardening of the system can occur."
 |
| </p>
 |
| </blockquote>
 |
| <p dir="ltr">
 |
| There are two components of the Production Release practice: 1) Release Preparation, and 2) Deployment. Release
 |
| preparation establishes a release baseline and produces all the necessary supporting material necessary to deploy (and
 |
| back out, if necessary) the release.
 |
| </p>
 |
| <p>
 |
| Deployment involves the act of delivering the release into the production environment, verifying that the integration
 |
| of the release package into the existing environment was successful, and notifying all relevant stakeholders that the
 |
| features of the release are available for use.
 |
| </p>
 |
| <p>
 |
| Unfortunately, there is little guidance available today regarding the practice of releasing to production. Although
 |
| there is wealth of information documented in the Information Technology Infrastructure Library (ITIL) set of process
 |
| books on this topic, those reference materials are used primarily by members of Production Support and IT Operations
 |
| organizations and not application development groups.
 |
| </p>
 |
| <p>
 |
| This practice is designed to fill some of the void in this area for product development teams.
 |
| </p></mainDescription> |
| <additionalInfo><p>
 |
| For additional information about Production Release, see:
 |
| </p>
 |
| <p>
 |
| Dean Leffingwell. <em>Agile Software Requirements: Lean Requirements Practices for Team, Programs, and the
 |
| Enterprise</em>. Addison Wesley, 2011.
 |
| </p>
 |
| <blockquote style="MARGIN-RIGHT: 0px" dir="ltr">
 |
| <p>
 |
| Introduces the "Big Picture" of Scaled Agile and describes various aspects of that model, some in more detail than
 |
| are covered in this method. Overall, a refinement of his previous works with the addition of Lean IT practices
 |
| adopted from Lean Manufacturing.
 |
| </p>
 |
| </blockquote>
 |
| <p>
 |
| Dean Leffingwell. <em>Scaling Software Agility: Best Practices for Large Enterprises</em>. Addison Wesley, 2007.
 |
| </p>
 |
| <blockquote style="MARGIN-RIGHT: 0px" dir="ltr">
 |
| <p>
 |
| The first major work on scaling Agile that was based on key implementation experiences at several international
 |
| companies.
 |
| </p>
 |
| </blockquote></additionalInfo> |
| <problem><p>
 |
| Releasing a finished or emerging product into production is no trivial matter. Sometimes, business operations are
 |
| interrupted or shut down because a release has somehow corrupted the production environment. Because the release
 |
| activity can have such a dramatic impact on the business, the purpose of the Production Release practice is to ensure
 |
| that the application developed is properly prepared to be released into production without any unintended consequences.
 |
| </p></problem> |
| <application><p>
 |
| The best way to read this practice is to become familiar with its overall structure, what is in it, and how it is
 |
| organized.
 |
| </p>
 |
| <p>
 |
| Start with the tasks for preparing the release for production, then review the work products that result from those
 |
| tasks. Next, review the tasks of the deployment activity. Although these tasks sound straightforward, there is much
 |
| skill and effort that goes into them. That is why a seasoned Deployment Engineer should execute these tasks.
 |
| </p></application> |
| </org.eclipse.epf.uma:PracticeDescription> |
