Artifact: Release Plan

The purpose of the Release Plan is to gain alignment between the Program Manager and the other teams to a common, committed, set of features for the release.

Features are added, evaluated, approved, and committed for release.

The following table explains the more complex state transitions:

From State	To State	Transition	Explanation
Proposed	Committed	All Features Approved	All features have been approved by all teams.
Proposed	At Risk	Team-Level Work Issue	Work related to the Feature has changed. Size Exceeds Capacity: At least one team does not have the projected capacity to address all the features planned for the release. Date Changed: At least one team changes the delivery date of work on the Feature. State Change: At least one team changes the state of the Feature from Approved (see diagram).
At Risk	Proposed	Issue Resolved	The issue related to the work for each team is resolved. Size Fits Capacity: The work for each team fits within their projected capacity to deliver. Date Approved: The delivery date of the work on the Feature is approved. State Change: The state of the Feature is Approved.
Committed	At Risk	Feature Changed	Work related to the Feature has changed, causing the Release to be at risk.

Contained Artifacts	Release plan - at risk Release Plan - Committed
Roles	Responsible:	Modified By: Program Manager
Tasks	Input To:	Output From: Steer Release Scope