Sprint phase: | Sprint 5 - Release eng: Robin
| Next Sprint |
|---|
sprint planning preparation - product owner picks focus, features, and bugs for next sprint, moves to a new sprint bucket in JIRA
- all: may nominate candidate bugs and features for sprint
| | |
sprint planning meeting - all: look at sprint bucket in JIRA and make estimates for their tasksall: may nominate candidate bugs and features for sprint
- release engineer chosen
| 2/11 | |
sprint begins - dev: starts coding
- qa: starts testplans
- scrum master: produces burndown chart
- ongoing releases to test environment as needed, to be negotiated between dev and QA
| 2/12 | |
new features/planned work completed - release engineer or dev: releases to QA machine
- dev: starts bugfixes from backlog
- QA: test plans complete, testing of planned work begins
| 3/11
|
|
bugfixes from backlog completed - dev: start bugfixes for planned work
- qa: verifies backlog fixes
- customer relations: sends an early notification to thalia-info
| 3/18 | |
final bugfixes completed - dev: all new development occurs in a new branch
- qa: verifies final bugfixes
| 3/?? | |
QA gives green light to release - qa: all fixes verified, no blockers
- customer relations: sends an immanent release announcement to thalia-info 24-48 hours before release
- release engineer: 24 hours before release, notify server ops of service outage
| 3/24
| |
release to production - release engineer and ops: release code
- release engineer: send confirmation to server ops that release was successful
- customer relations: send confirmation to thalia-info that release was successful
| 3/25 or 3/26
| |