OpenNCP Weekly Sprint Meeting
15th October 10:00 to 11:00 CET
Work RoadMap - epSOS 2 Services
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) Completed
5º Sprint: 25Mar > 8Apr (2 weeks) Completed
6º Sprint: 22Apr> 3May (2 weeks) > Completed
7º Sprint: 6May> 17May (2 weeks) > Completed
8º Sprint: 20May> 31May (2 weeks) > Completed
9º Sprint: 3June> 14June (2 weeks) > Completed
10º Sprint: 24June > 19July (4 weeks) > Completed
- Release OpenNCP 2.0.1 >
31 July, 2013 (Wednesday) 6th August
- Release OpenNCP V2.0.2 > 2013-09-12 Transformation Manager + Emergency Scenario + Bug Fixing
5ª PPT [in progress]
OpenNCP V2.0.3 (after PPT) 2013-10-16 OPERATION Ready for: PAC + HCER epSOS 2 Services
Due to PPT extension
- OpenNCP V2.0.3 (after PPT) 2013-10-23 OPERATION Ready for: PAC + HCER epSOS 2 Services
11º Sprint: 15Oct > 28Oct (2 weeks) [in progress]
- OpenNCP V2.1.0 2013-10-30 PPT Ready for: MRO + TSAM-sync (adaptation for CTS2 compliance)
??ª PPT [recommended]
- OpenNCP V2.1.1 (after PPT) 2013-12-05 OPERATION Ready for: ??
Agenda
a) 5º PPT slot - retrospective and lessons learned
b) Dev Sprint Planning
Location
Skype (sirLicman) + Jira Board + MeetingWords ()
Participants:
MEETING NOTES
a) 5º PPT slot - retrospective and lessons learned
- NEW process: RELEASE CANDIDATE (due to security policies - by Italy)
--- Demand the creation of RC (they do not work with snapshots)
--- So far we already have 2 RC, and probably we will have 1 more;
--- Each release take 30 minutes;
- Regarding Opening ISSUES
-- only slight problems with the Audit messages have been reported and fixed;
-- clearly the OpenNCP software is getting solid and mature, and fully prepared for Operation;
- OpenNCP 2.0.3 Release > Reschedule for 23 October, after confirmation on TConf if no impediments found;
b) Dev Sprint Planning
- Missing task regarding the Audit messages, that probably could be similar to the PS with different identifiers;
-- Ask or digging the documentation?
--- Let's start by reading any available documentation;
NEXT Steps
- [LKM] next meeting > 22Oct > 10h00 CET > Sprint progress monitoring
- Due to lack of availability from Licinio, next meeting will be lead by Marcelo Fonseca (skype: marcelo.fonseca.iuz)
- [Ivo] Assess conditions for OpenNCP 2.0.3 Release, and in case of "all green" > proceed with the release.
- [MF and KK] Proceed with the MRO developments;
Previous Actions [to check progress]
- [Giorgio] Provide the initial design from LTR database scheme;
- [Marcello] Suggest "Reverse Engineering" in order to understand the current scheme, and compare it with the "DOC" to understand the initial rationale for the design;
- [Giorgio] Undesrtand the maturity of PAST implementation;
- [Marcello] Undesrtand if Mayo Clinic is available for testing scenarios and understand if there are any license constraints with the "CTS2 Development framework";
- [Norbert] Check possibility for providing inputs regarding AT CTS2 implementation (Peter Brosch, Kathrin Trunner);
- [Norbert] A refined approach to QA via a semi-sync process;
- [LKM] Build Wikipage with all the knowledge gathered around CTS2 > also including Candiate Design of implementation > visual overview on components, operations and workflow;
- [Norbert + Fonseca] Work on Quality Assurance mechanisms, namely by providing a clear perspective on what could and MUST be developed, regarding transactions;
- [LKM] next meeting > 15Oct > 10h00 CET (inform Juergen and Milan, to confirm that the TPM meeting is moved from the 15th to the 16th)