Page History

 sprint planning preparation

 sprint planning meeting

•  product 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

• all: look at sprint bucket in JIRA and make estimates for their tasks
• release engineer chosen

2/11

• all: separate design and implementation for new features when entering issues in jira
• Product Owner prioritizes items for planned work.
• sprint planning meeting:
  • Choices for planned work are reviewed by team
  • Release engineer chosen
  • Required design meetings are identified and planned/scheduled

3/21 - 3/27
planning meeting: 3/27

3/21 - 3/27
(one planning for all of sprint 6)

development and design cycle sprint begins

• dev: starts coding on clearly defined features
• dev: facilitates required design meetings, and documents final design choices so QA can prepare test plans, know what to expect with new features
• 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 first;
• Last week of cycle is for bug backlog

3/31 - 4/11

4/11 - 5/23
* will overlap with bug fixing for sprint 6a

first release to qa  new features/planned work completed

• release engineer or dev: releases to QA machine
• dev: code is branched, and all new development occurs in a that sprint's branch
• dev: if there is time before issues related to immediate build come in, start starts bugfixes from backlog
• QA: test plans complete, testing  of planned work begins
  

3/11

4/22

5/26

iterative qa phase bugfixes from backlog completed

• dev:  start work on bugfixes for planned work
• qa: verifies backlog fixes, and fixes as specified in each version's release notes
• 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/??

4/22 - 5/1

5/26 - 6/13

QA makes recommendation about release -- team decides go/no go for proposed production release date QA gives green light to release

• qa: all fixes verified, no blockers
• customer relations: sends an immanent imminent release announcement to thalia-info 24-48 hours before release
• release engineer: 24 hours before release, notify server ops of service outage

3 5/24 1

  6/13

release to production

• release engineer and ops: release code - release window is a Tuesday or Wednesday, 6PM-9PM
• 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

5/6

6/17