You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »

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
  • all: look at sprint bucket in JIRA and make estimates for their tasks
  • Product Owner prioritizes items for planned work.

 

3/20

 sprint planning meeting

  • Choices for planned work are reviewed by team.
  • release engineer chosen

2/11

3/24

development 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/7


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

design tasks

  • dev and qa: do any design-related tasks for next sprint's implementations.. Design and implementation to be separate JIRA tasks for any feature.
  • dev: documents final design choices so QA may prepare test plan in next sprint

3/24-3/28

 

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

 


---------------  

Post sprint organization...

Dev Freeze = no new feature development.  Developers shift to fixing bugs.

Code Freeze = current dev branch is completely frozen prior to deployment.  All new dev work goes on a new branch for the next iteration.

Release date - generally, we aim for deploying on a Tuesday morning, so that folks are actually around if something breaks. 

Sprint Number

Dev Freeze Date

Code Freeze

Release Date

Release Engineer

1

September 21, 2007

October 12

October 15/16

Robin

2

October 29, 2007

November 1

November 5

Janet

3

December 3, 2007

December 10

December 13/14

Qing

4

January 4, 2008 everything except access control
January 11, 2008 code freeze

Jan 25, 2008

Jan 29, 2008

Janet

5

March 11 2008 dev code freeze

March 18, 2008
Arnis sent out the customer announcement

March 25, 26, 2008
Arnis sent out the service outage note the day before the release
and reiterate the major features in this release

Qing


Pre-sprint organization

Oct 2 Usability test

Oct 19 code freeze

Nove 19 release

  • No labels