Release Objectives are set (Project Director)
Release press release created (Project Director/Marketing)
Release Assignments Made and Resources Allocated (Project Director)
- Lead Campus/Project Director:
- Lead Product Owner:
- Technical Lead:
- Scrum Master:
- Lead UI Designer:
- Customer Liaison:
- Sys Admin Support:
- System Architect:
- Subject Matter Expert:
- Developers:
  - UI/UX:
  - Middleware:
  - Application:
  - QA
Release Prep Meeting Scheduled
Targeted Customers Identified
Follow-up scheduled with Customers
Release Schedule Set (e.g. Sample 10 week cycle below)
- Sprint 1, Dates:
- Sprint 2:
- Off Week:
- Sprint 3:
- Sprint 4:
- Release Week (Release on Thursday):
- Off Week:
QA Environment and update process in place
Continuous Integration Environment in place
QA Requirements Defined
Release Implementation Plan Created
Test Plan Created
Sprint Milestones Set
Sprint Started
- Sprint 1 Pre-Planning, date:
- Stories defined
- QA Requirements Defined
- Targeted Customers Identified
- Follow-up scheduled with Customers
- Sprint Demo/Wrap-up, date/time:
- Invitations sent for demo to internal external stakeholders
- Sprint Retrospective, date/time:
Release Deployment Plan Created
Regression Testing Complete
Deployed to Sandbox for UAT
Deployed to Pre-production
Deployed to Production
Have a Party

Browser not supported