Date
Participants
Goals
Goals of the meeting were
Introduce themself new attendants
To discuss the just closed Sprint (20th of January 2020): pros and cons
Main issues on the roadmap
To define next Sprint (20th of February 2020): what needs to be done?
Reactions and suggestions
Note: we also had a look to the tools and instruments we are using in the project (GitHub, Jira, Slack, issues estimations and workflow, Gitflow and Smart Commits)
Discussion topics
Time | Item | Presenter | Notes |
|---|---|---|---|
21:10 | What you see and what you do? | All | Each participant shortly introduced *self and explained what he/she has done since last call and how he/she feels about the project. All participant agreed that work with the project has been easied by well documented issues. Therefore we invited all participant and dev to help us in documenting event better the future ones. |
21:30 | Last Sprint | We had a look to the sprint graph and explained how to read it and what we understand out of it. Briefly we have too plan much less workload for the team, in order to achieve goals in a steady way. Much less workload has been identified as 1-2days/week with sprints of 3-weeks lenght. | |
21:45 | Roadmap | We briefly discussed the roadmap from OH1.9 → OH2.0 meant as, briefly, a release joining together “core” + “api” + “gui” + “ui” + “doc” in a single package (note: the “ui” will not cover 100% of the “gui” for the first several months):
Until these collage is not possibile, we’ll continue with minor releases, like 1.9.x (or 1.x in case of DB changes) | |
22:00 | Next Sprint | All | We defined the new sprint (already started) for the coming month: it will last for 3-weeks so it will finish 1 week before the next planned call (end of February) |
22:30 | Reactions and suggestions | We agreed that much work need to be done before the version OH2.0, especially on the “ui” side, for which it would be bettere to have a specific call with whom involved on that side. We also talked about different paths the application |