OpenNCP Weekly Sprint Meeting

25 MAR 10:00 to 11:00 CET

Work RoadMap

1º Sprint: 28Jan > 8 Fev (2 weeks) > Completed
2º Sprint: 11Fev > 22Fev (2 weeks) > Completed
3º Sprint: 25Fev > 8Mar (2 weeks) > Completed
4º Sprint: 11Mar > 22Mar (2 weeks) ~~(<- both weeks, or perhaps just the last week could be the code freeze?)~~ Completed
- Release date: 25March (Monday) > OpenNCP 2.0.0 > WE ARE HERE
-- Release Notes

Agenda

Prior to this meeting, the Portuguese team will have scoped the sprint which will eventually lead to the release of OpenNCP 2.0.This meeting will schedule the sprint and provide a code freeze date and a release date

Sprint Review:
1. What have we achieved, regarding the first 4 sprints of epSOS 2 services development?
2. What can we release?
Sprint Retrospective:
1. What went well during the sprint?
2. What could be improved in the next sprint?
Sprint Planning:
1. Time frame
2. Goals
3. Impediments
4. Available resources

Location

Skype (sirLicman) + EtherPad (http://openetherpad.org/mMCay1yDC8)

Participants:

Aarne Roosi <Aarne.Roosi@affecto.com>,

Alexander Berler <a.berler@gnomon.com.gr>,

[yes] Anders Nyström <Anders.Nystrom@apotekensservice.se>,

Arnaud Gaudinat <arnaud.gaudinat@hesge.ch>,

[yes] Fredrik Dahlman <fredrik.dahlman@cag.se>,

[yes] Gareth Woodham <Gareth.Woodham@apotekensservice.se>,

Gergely Heja <heja.gergely@eski.hu>,

Giorgio Cangioli <giorgio.cangioli@gmail.com>

[yes] Ivo Pinheiro <ivo.pinheiro@iuz.pt>,

[yes] Konstantin Hypponen <konstantin.hypponen@kela.fi>,

[not present] Kostas Karkaletsis <k.karkaletsis@gnomon.com.gr>,

Licinio Mano <licinio.mano@iuz.pt>,

Marcello Melgara <Marcello.Melgara@cnt.lispa.it>,

Mate Beštek <mate.bestek@gmail.com>

[yes] Marcelo Fonseca <marcelo.fonseca@iuz.pt>,

Mika Myllyvirta <mika.myllyvirta@kela.fi>,

Mindaugas Ajauskas <mindaugas.ajauskas@lispa.it>,

Norbert Repas <norbert.repas@elga.gv.at>,

Patrick Ruch <Patrick.Ruch@unige.ch>,

Tomaz Cebular <Tomaz.Cebular@ivz-rs.si>

[vacation] Steen Manniche <STMA@ssi.dk>,

Stefan Gustafsson <stefan.gustafsson@callistaenterprise.se>,

[yes] Stéphane Spahni <stephane.spahni@hcuge.ch>,

MEETING NOTES

1. Sprint Review:

1.1 Work Completed

[Licinio Mano] OpenNCP 2.0.0 > Can we release it?

[Marcelo] PAC: This service is closer to be finnished, since the new Patient role is already implemented. It is now waiting for final feedback from Kostas.

[Konstantin] HCER: Country A part ready and committed to the develop, but not tested, as there are no testing tools, and Country B implementation not ready yet. Country B (portal part) is being implemented by Kostas.

[Licinio Mano] We cannot start releasing the OpenNCP 2.0.0 today, because we haven't yet completed the development cycle for any of the aimed epics.

1.2. What have we achieved, regarding the first 4 sprints of epSOS 2 services development?

- Divided effort between Development and Support.

- Team effort/focus in the PPT slot.

1.3. What can we release?

- We cannot release today, that's for sure. We should plan for next sprint.

2. Sprint Retrospective:

2.1. What went well during the sprint?

- Focus on the Support/Bug Fix regarding PPT;

- Fewer bugs/ more quality / more sustainability

- Enhanced documentation;

2.2. What could be improved in the next sprint?

- The specifications raise a lot of questions, so it is very dificult to get a good development velocity.

- Last week: PSB anounced licensing issues concerning PAC and approved the funding for HCER portal implementation;

[Licinio Mano]

- Last 2 week - we have development and PPT running at the same time.

[Licinio Mano]

[GoLive - Implement]- For give diferent visibility to Development Stories and Support Issues, maybe we could have separated boards:

OpenNCP Development (Epics, Stories and Sub-Task)

OpenNCP Support (Bugs, Improvements, Task)

3. Sprint Planning:

3.1. Time frame

-- 5 Sprint 25Mar to Apr 5 (2 weeks)

-- 8 April - Code freeze;

-- 8 to 10 April - Quality Control Stage;

-- 11 to 12 April - OpenNCP 2.0.0 Release

3.2. Goals

-- PAC Service release;

-- ?? HCER release maybe but depending on Gnomon availability in the next 2 weeks.

3.3. Impediments

- [RAISE] Licensing issues that afect PAC > should keep developing or we should suspend developments until further clarifications;

- [RAISE] HCER Country implementation, is being done by Gnomon, and it depends on how much effort they can apport to the OpenNCP development;

3.4. Available resources

- Istambul Projecthaton > should use OpenNCP 1.1.2

- [konstantin] Should focus in the Support

3.5 Other topics- related to Security Expert groups

- Will need to refactor tsl-sync, in order to comply with the discontinuation of security relaxations.

- Provide a means for the national connector of the country A to have information about the way in which HealthCare Professional has been identified in country B.

- Try to understand who in the SEG may provide insights for OpenNCP development.

+++++++++++++++++++++++++++++++

[KOSTAS feedback - for today meeting]

I have at least these 2 issues waiting (https://openncp.atlassian.net/browse/PT-223,https://openncp.atlassian.net/browse/PT-224)

from Marcelo and Eric in order to be resolved, so it should be better to appear as open and have to do with Patient Identification when using birth date and patient gender

I have also these issues that come from pre pat testing

https://openncp.atlassian.net/browse/PT-226

https://openncp.atlassian.net/browse/PT-227

https://openncp.atlassian.net/browse/PT-231

https://openncp.atlassian.net/browse/AV-5

and https://openncp.atlassian.net/browse/PT-232 that has to do with audit problems.

Last week work done:

1. Testing of audits are being created by OpenNCP have been tested (https://openncp.atlassian.net/browse/PT-232). Some problems exist there. Mustafa, Konstantin have been informed for this (See this https://support.epsos.cz/issues/276).

2. PAC Scenario tested after Marcello fixes for new patient role (See https://openncp.atlassian.net/browse/GUI-37)

3. Pre PAT testing

4. OpenNCP support (several tests with Marcelo Fonseca for the https://openncp.atlassian.net/browse/PT-226 issue)