Provide a summary of this practice.
The Release Charter sets the basic parameters for a release, ensuring agreement and alignment between stakeholders and the Agile team.
Click here for details of the Release Charter.
What is the overall goal or intention of this practice?
Creating a Release Charter is used to define the release’s foundations and overall structure:
What are the schedule, cost, quality, frequency, performance or other expectations for completing this practice?
Creating a Release Charter should be carried out at the start of each release.
The Charter should also be maintained to reflect on-going changes.
What must have happened or been delivered for this practice to be considered complete?
Creating a Release Charter is complete when the Release Charter has been agreed.
What pre-conditions must be met before this practice is used?
Creating a Release Charter should not begin until:
This view shows a simplified version of this process. For full details, explanation and advice, click on the ‘Detailed process’ tab. For background such as entry and exit conditions, click on the ‘Context’ tab.
|2||Review Product Plan|
|3||Identify release goals & backlog|
|4||Draft Release Charter|
|5||Validate Release Charter|
|6||Review Release Charter|
|7||Approve Release Charter|
|8||Publish Release Charter|
|1||Confirm readiness||Product Owner.||Check that:|
|2||Review Product Plan||Product Owner.|
|3||Identify release goals & backlog||Product Owner.|
|4||Draft Release Charter||Product Owner.|
|Draft Release Charter.||Like every Agile product, a Release Charter should contain the least that is needed to get the job done.|
|5||Validate Release Charter||Product Owner.||The Charter should be checked against:|
|6||Review Release Charter||Product Owner.|
The release team leads & members.
|7||Approve Release Charter||Product Owner.|
|Approved Release Charter.|
|8||Publish Release Charter||Product Owner.|
Issues & risks
What are the key concerns in making a success of this practice?
- A basic definition of a Release Charter can be found here.
- During the transition to Agile (or where parts of the organisation remain non-Agile), stakeholders may want the Release Charter to perform a similar role to Prince2’s Project Initiation Documentation (PID). That is, they may want of detail about ‘the project’, the deliverables and the delivery process, and they may expect it to be relatively fixed. This can be remedied by ensuring that they are fully briefed on Agile before the Charter is reviewed by them.
- To be effective (e.g., actually read by the stakeholders and the team), the Release Charter should be very brief, ideally no more than one page. Note that this makes it harder, not easier, to write & agree.
- The Release Charter is not a one-off document. It can be revised and updated at any time during the release.
- However, if it is changed, the full cycle of review & approval needs to be repeated.
- Iteration Leads should walk their teams through the Release Charter again as part of the Iteration Planning process.
- Users should also be familiarised with the Release Charter as part of their induction to the Agile team.