Workflow Sobek 3.1 sprints

Decisions made:

• there will be a daily standup meeting at 9.30am. Before the start of every sprint a moderator ('stand up moderator') will be assigned to keep the session focused and short, check the schedule below.
• 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, and this will be reflected in the rapid board. Product owners can not bypass this agreement on an ad-hoc basis.
• it is the responsibility of the product owners to monitor all new issues in Jira that which have the field 'Affects Version(s)' set to 'SOBEK 3.1', and to assign a fix version to those issues.
• Bernhard Becker is chief product owner. In case of doubt get in touch with him.
• developer will pick the top issue from the rapid board, taking into consideration that the issue is fit for her/him (based on experience).
• when prioritizing issues the product owners will apply a 50/50 division between bugs and user stories.
• if a user story is unclear the developer will get in touch with the product owner and request her/him to clarify the issue further in Jira.
• if a user story is too big to be considered as one task, the developer will notify the product owner after the first upcoming standup meeting, and organize for it to be split up into multiple tasks (in cooperation with colleague developers).
• for the review task we will use crucible. Currently this is not working for all developers, so until that time we will use the current method of reviewing (formal review or review during pair programming, including an update to the peer review-excel sheet).
• a retrospective will be planned at the end of every sprint.
• Mischa will be kanban master for the entire period of development for Sobek 3.1.
• all developers are expected to take on the role of moderator / fail master, see below.

Setup Jira

• Add Sobek 3.1 Dashboard
  • 'Dashboards' menu item -> 'Manage Dashboards' -> 'Popular' tab -> select 'SOBEK 3.1'
• Sobek 3.1 Rapid Board
  • 'Agile' menu item -> 'Rapid Board' -> in upper left selection box select 'SOBEK 3.1'

table: Stand up moderator / fail master

One person takes on both roles on one day. It is her/his responsibility to transfer responsibility to the next person in the list. (S)he is recognisable by the (double secumate protected) candy box which sits on her/his desk. If the next person is not available during the standup meeting the current moderator will keep that role. (S)he will however be fail master for the day. In case the next person is absent altogether the next available person is assigned both roles, and we will continue from thereon.

Responsibilities:

• Focus on fixing 'knipperlicht' and work in progress-tests. This link describes some known issues with the buildserver/reasons for tests failing.
• Moderate the standup meetings.
• Address the developer that caused a failing test, and making sure the revert is executed when necessary (either by doing it himself or by delegating).

A page has been created to help work as efficient as possible.

table: Tester -> Justen is now full-time tester, together with David. No more testing efforts required from team members.

It was decided that each of us will also do some testing. Days on which to test and the duration of each session can be chosen by each developer based on her/his preference. So it is possible to do testing for an entire week or spread it out over multiple days, see the table above. Each developer is requested to sign up for some days. In the end the time spent testing should be more or less equal for each developer. (S)he is recognisable by the (double secumate protected) candy box which sits on her/his desk. 

The tester has multiple responsibilities:

1. Test issues on the rapid board that are in column 'Test Functionality' so that David can focus more on finding new issues. Exception: if field 'Tester' is already set to David he will deal with this issue.
2. The tester will also focus on fixing 'knipperlicht' and work in progress-tests. This link describes some known issues with the buildserver/reasons for tests failing.
3. Also, this person will moderate the standup meetings.
4. Address the developer that caused a failing test, and also for making sure the revert is executed when necessary (either by doing it himself or by delegating).

A page has been created to help the current tester work as efficiently as possible.

table: Release planning

Sobek 3.1 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. OpenDA-Calibration and Kalman-filtering
7. FEWS-adapter
8. OpenMI(2.0)-compliancy

Notes:

• OpenDA-calibration, FEWS-adapter are not in msi but in a separate installer/exe/zip.
• OpenMI will not be a part of Sobek 3.1 release.
• Plugins Habitat, Morphan, WFDExplorer are not a part of Sobek release
• DeltaShell.Plugins.Data.Xml is not a part of Sobek release (currently only used by Habitat)
• DeltaShell.Plugins.Data.Toolbox is not a part of Sobek release (was meant for Habitat, does not work, can be used in future of other models too)
• DeltaShell.Plugins.Data.UdUnits is not a part of Sobek release (currently not used, it will be used in the future)

You can unload Habitat, Morphan and WFDExplorer and their tests without any problem
You can unload Fews, OpenDA, OpenMI and OpenMI2 and their tests, but you have to unload Sobek.IntegrationTests as well
You can unload Data.Xml, Data.Toolbox and Data.UdUnits and their tests, but you have to unload DeltaShell.IntegrationTest as well

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