Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Sprint Duration: 30 days (from 30/Jan/20 - 02/Mar/20) - hours worked: 6 - developers: 4
Full report @ https://openhospital.atlassian.net/secure/RapidBoard.jspa?rapidView=3&projectKey=OP&view=reporting&chart=sprintRetrospective&sprint=4

Page Properties


Date

Team

OpenHospital Core Team

Participants

Alessandro Domanico Vito Romano Niccolò Pasquetto Antonio Verni GIUSEPPE SORGE

Background

This is the second Sprint we plan on this platform, and the first one () has showed a working capacity of 1.15days/week, so we planned it for an amount of issues of 3d 6h (Estimated Time) considering 3 weeks = 3.55days.

Retrospective

The present retrospective is about the 2nd Sprint we had, starting January 2020, which aim was ”To have a full implementation of REST API while keeping the "gui" up and running, plus some enhancements coming from unplanned issues and tickets (bugs)”.

...

The focus factor this time has been 0 (if counting the closed issues, less than 0.025 if we count worked hours) so the average with the previous one is (0 + 0.058) / 2 = 0.029 => 0,575 d/week, means that for the next Sprint we cannot plan more than that amount of work for the team per week (next Sprint of 3 weeks = 1d 6h)

We should then:

  • Step1: to finish bugfixing on 1.9.1-pre and release 1.9.1

  • Step2: to merge 1.9.1 fixes on ‘default/master/develop’ branches and repeat the Sprint for the 1.9.2-pre

...

  • :

    • to approve or change OP-178

    • to approve or change OP-127

    • to define a pattern for OP-6

    • to solve small big yet unresolved issues for 1.9.1

Also: for each new releases, we should branch and create a new branch X.Y.Z so both release and bugfixing can go at their own pace.

...

...

Start doing

...

Stop doing

...

Keep doing

...

Start doing

...

Stop doing

...

Keep doing

Action items

  •  

  • To fully document the new issues

  • To foster the discussions under the Jira issues by comment them with temporary findings

  • Starting pull-request without comments about everything the PR is doing

  • Commenting in languages other than English

  • Starting pull-request with more changes than the PR’s title is stating

  • Taking charge of tasks

  • Worklogs

Action items