Decisions made:

  • each sprint will start with a kick-off, in which the projectleader explains to all team members the goal of that sprint.
  • there will be a daily standup meeting at 9.30am.
  • we aim to keep all tests green. If a check-in results in a failing build or test(s) the developer is expected to fix this with highest priority. If necessary a revert will be done at the end of the day (if developer is not able to fix before that time).
  • the full releaseplanning can be found below. This includes all special dates like: when do we stop developing, when do we branch...
  • it is the responsibility of the product owners to prioritize jira-issues before the start of the sprint, and this will be reflected in the sprint-specific rapid board. Product owners can not bypass this agreement on an ad-hoc basis.
  • for the review task we will use crucible.
  • a retrospective will be planned at the end of every sprint.
  • a demo will be plannend at the end of every sprint.
  • Mischa will be scrum master for the entire period of development for Sobek 3.2.
  • For instructions on creating issues see item 'working with labels'

Setup Jira

  • Add Sobek 3.x Dashboard
    • 'Dashboards' menu item -> 'Manage Dashboards' -> 'Popular' tab -> select 'SOBEK 3.x'
  • Sobek 3.x Rapid Board
    • 'Agile' menu item -> 'Rapid Board' -> in upper left selection box select 'SOBEK 3.x'
working with labels

Issues that are part of a user story will no longer be created as sub-task of a main issue, but rather will be created as separate issues that all have the same label. These issues must also link to their main issue. So, when creating an issue take the following steps:

  1. set fix versions to 'SOBEK 3.x' and 'NGHS Sprint y'
  2. when applicable, set label
  3. if issue is part of user story, also add the link to the main issue

table: Release planning

begindatum

einddatum

week

 

11-02-2013

01-03-2013

7, 8, 9

Sprint 1

04-03-2013

22-03-2013

10, 11, 12

Sprint 2

25-03-2013

12-04-2013

13, 14, 15

Sprint 3

15-04-2013

03-05-2013

16, 17, 18

Sprint 4

06-05-2013

24-05-2013

19, 20, 21

Sprint 5

27-05-2013

14-06-2013

22, 23, 24

Sprint 6 (eind: feature & DB freeze Sobek 3.2 & branching)

17-06-2013

05-07-2013

25, 26, 27

Sprint 7 (bugfixing Sobek 3.2 branch, pure 2D ontwikkeling)

 

 

 


14-06-2013

 

24

Feature and DB freeze.

17-06-2013

05-07-2013

25, 26, 27

Bugfixing

14-06-2013

 

24

Create branch

05-07-2013

 

27

Release to SSD

17-06-2013

05-07-2013

25, 26, 27

Testing

Sobek 3.2 release contents

1. Delta Shell framework (including the generic plug-ins)
2. D-Flow 1D
3. D-RTC
4. D-WAQ 1D
5. D-RR
6. D-FM

TODO: finish

Check this page for details on the workflow used in Jira.

  • No labels