2020-01-23 Sprint 1 Retrospective

Sprint Duration: 52 days (from Dec 2, 2019 to Jan 20, 2020) - hours worked: 24 - developers: 4
Full report @ https://openhospital.atlassian.net/secure/RapidBoard.jspa?rapidView=3&projectKey=OP&view=reporting&chart=sprintRetrospective&sprint=3



Date

Jan 23, 2020

Team

OpenHospital Core Team

Participants

@Alessandro Domanico @Vito Romano

Background

First Sprint of the OpenHospital working group, with the aim “To have first release containing all components "core", "gui", "api" and "ui" working together with a minimum functionality of "ui" (only new-patient and search-patient)”.

Retrospective

The time was enough but the team focus factor was not yet tested and many issues remained unresolved.

Also, the peaks you see on the real trend (in red) are due to the fact that, once the sprint was started (instant 0), we did some tests adding and removing issues: some of these actually went to oversize the Sprint for our abilities and also the goals, others have been added as bugs, and therefore must be resolved as soon as possible. The gray oblique line is the "ideal" course of work. The classic working capacity of the work group was 4.6 days / week if we consider only those who worked, 2.3 days / week if we consider the whole potential group (at least double the number of people), 1.15 days / week if we consider 4-hour days (part-time) compared to the classic 8h (full-time). This means that in a week we cannot think of completing more than that amount of hours, even less. It's not cheap! We are still volunteers!

However, I would first try 3 Sprints in a row to calculate a real group average speed.

Start doing

Stop doing

Keep doing

Start doing

Stop doing

Keep doing

  • To use the last 3 sprints average velocity to plan the current sprint

  • To inform the SM (SCRUM Master) if any deadlock occurs in the issue assignment

  • Planning what is not possible to achieve

  • Documenting issues has been the best part in having some issues closed.

Action items

To document any finding under the issues
To hit the community for help and to foster the online discussion
To inform the SM (SCRUM Master) if any deadlock occurs in the issue assignment

Open Hospital powered by ISF
2005 - 2016 ISF © Informatici senza frontiere - ONLUS