Release Workflow

The following figure shows a high-level Release process workflow in the default system.

Note: CSM uses several features to manage the Release workflow (ex: The Release Form helps create and manage Releases, One-Steps help move the Release through its workflow, Automation Processes notify stakeholders via e-mails).

Contributors

A Release typically has several contributors. Depending on your workflow and the size of your company, many of these contributors might be combined into one person:

• Requestor: Person who initiates the Release. This is typically a technician or owner of the associated Change Request.
• Creator: User who first creates the Release. This is typically a technician; the level varies on the depending on tiered support.
• Owner: User who manages the Release. This is typically a technician; the level varies depending on tiered support.
• Task Owner: User to whom Tasks are assigned in order to help deploy the Release.
• Testing Manager: User who manages the Test phase of the Release.
• Documentation Manager: User who creates the Release Notes or other documentation for the Release.
• Approver: User who ensures that the Release is ready for deployment. This is typically a member of the Knowledge Team.
• Deployment Manager: User who manages the deployment of the Release.
• Stakeholder: User/Customer with an interest in the outcome of the Release.

Phases

The Release workflow is broken down into the following phases:

1. Plan: Creator records the Requestor and initial details, and then assigns an owner. Owner defines the Release Package, Service Schedule, and Release Plans. Owner adds members to the Release Team, and then assigns Tasks to Release Team members.
2. Build: Owner creates one or more builds of the Release Package.
3. Test: Test Manager tests the Release build(s) in a test environment that duplicates the live environment.
4. Document: Documentation Manager creates Release Notes, and then the owner requests approval.
5. Approve: Approver makes a decision (approves, denies, abstains) regarding the deployment of the Release build(s) to the live environment.
6. Deploy: Deployment Manager deploys the Release to the live environment.
7. Review: Owner records the final details, and then closes the Release.

Statuses

A Release progressing through the workflow encounters the following statuses:

Note: Release statuses do not align with Release phases.

1. New: Release is being created, recorded (initial details), and assigned to an owner.
2. Planning: Release Package, Service Schedule, and Release Plan are being planned. Release team is assigned. Tasks are assigned.
3. Building: Release build is being defined.
4. Testing: Release build is being tested.
5. Documenting: Release Notes are being defined.
6. Approving: Release is being approved.
7. Deploying: Release is being deployed.
8. Reviewing: Release is being reviewed.
9. Cancelled: Release is cancelled.
10. Closed: Release is closed.