How to Perform the Sprint Release

 

Introduction The Sprint Release is performed at the end of a successful Sprint. Not all Sprints need to end with a Sprint Release, the work of a number of Sprint can be accumulated and released in an simultaneously release, sometimes called an increment.
Who will participate? The participants has the following responsibilities:

Release Manager Product Owner Development Team Sales & Marketing Operation & Maintenance
Release plan A/R C C
Conduct release A/R C C
Verify release A/R C C
Legend: R=Responsible; A=Accountable; C=Consulted; I=Informed

What is the input? The input to the release is the deliverables from one or more Sprints.
Which tasks is expected? The following tasks are expected:

Task Description
Plan the release The planning of the release start with making a list of all the solutions which shall be part of the release and  verifying that they are in the ‘Done’ state.
The next steps in the planning will to a high degree depend on the environment the release shall take place in. If the release is in an IT system there may be a number of tools to support the releae planning. If the release is to a market this might involve the Sales and Marketing team.
Conduct the release The …
Verify the release Verify that all deliverables for the release is actually in the configuration item list for the release and that no other items are introduced during the release.
The verification can be either manual or automatic.

How shall the result be controlled? The result of the release is controlled by verifying that all deliverables for the release is actually in the configuration item list for the release. The verification can be either manual or automatic.
What is the output? The release creates a new version of the product
When can we exit? The process terminate when the configuration item list for the release is verified to include all the deliverables planned for the release
Hints and Examples The …