Beeswax - Sprint process

Events

Bug fixing (SPR N-1)

01/05/2015 - 01/06/2015

Whole Sigma Software team is involved

Preplanning (SPR N)

01/05/2015

QA, PM from Sigma Software and Product owner from Beeswax are involved.

The goal of this activity is to finalize User Stories for the next sprint and agree them with Beeswax team.

SPR N could be started

01/06/2015 23:59

Sprint could be started when on the following conditions:

  • All user stories, planned for the Sprint are described in Confluence
  • All user stories, planned for this Sprint are added to JIRA into corresponding Sprint
  • Usage scenario is agreed with Beeswax team

Demo (SPR N-1)

01/06/2015 23:59

The whole team and Product Owner participate.

Functionality for SPR N-1 is ready according to definition of done.

Planning (SPR N)

01/07/2015

The whole team participates in this.

User stories (SPR N+1)

Jan 8, 2015 - 01/09/2015

QA and PM are involved

By the end of Friday draft user stories for SPR N+1 (the next one, not the one dev team is working on), should be ready.

Development (SPR N)

Jan 8, 2015 - 01/16/2015

Developers participate in this event

Auto-test preparation (SPR N)

Jan 8, 2015 - 01/16/2015

QA participates in this

SPR N is developed

01/16/2015 23:59

By the end of Friday all items included into Sprint are developed, ready for testing. They are move to testing and assigned to QA in JIRA.

Preplanning (SPR N+1)

01/19/2015

QA, PM from Sigma Software and Product owner from Beeswax are involved.

The goal of this activity is to finalize User Stories for the next sprint and agree them with Beeswax team.

Bug fixing (SPR N)

01/19/2015 - 01/20/2015

Whole Sigma Software team is involved

Demo (SPR N)

01/21/2015

The whole team and Product Owner participate.

Functionality of SPR N is ready according to definition of done.