OpenNCP Weekly Sprint Meeting
...
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 [completed]
[NOT] OpenNCP V2.0.3 (after PPT) 2013-10-16 OPERATION Ready for: PAC + HCER epSOS 2 Services
11º Sprint: 15Oct > 28Oct (2 weeks) > completed
- PPT Ready for: MRO (new epSOS 2 Service)
- [√] OpenNCP V2.0.3 (after PPT) 2013-11-05 OPERATION Ready for: PAC + HCER epSOS 2 Services
12º Sprint: 1Nov > 14Oct (2 weeks) [ in progress ]
12º Sprint: 5Nov > 19Oct (2 weeks) [ in progress ] (delayed one week due to lack of resources to work in the 1st week)
- PPT Ready for: CI Automated Testing Suite Enhancements > COMPLETED
- OpenNCP V2.1.0-RC0 (PPT Ready) 2013-11-20 > MRO + CI Automated Testing Suite Enhancements [DONE]
PPT/QA Stage [not a formal PPT but a more structured QA stage - coordinated by the OpenNCP Community]
- OpenNCP V2.1.0 GOLD (after PPT stage) 2013-12-18 OPERATION Ready for: MRO + CI Automated Testing Suite Enhancements
AGENDA
a) PNs QA -
...
Monitoring and Closing
a.1) Issue solving progress.
a.2) Plans for GOLD release process.
b) Documentation preparing
...
LOCATION
- Skype (sirLicman) + Jira Board + MeetingWords
...
PARTICIPANTS
Today's Meeting Participants:
Invited Members List:
...
...
...
++++++++++++++++++++++++++++++++
OpenNCP Support Activities
- From now on every activity (improvements, task, bugs) should be reported to the Support Board.
- The Development Board is Officialy closed, until further "scope" and "conditions" concerning development;
- Let's try to have a minimum "task force"
++++++++++++++++++++++++++++++++
- Internal QA activities progress monitoring, RESULTS and needed ACTIONS
- All issues have been registered in the "Support Board" https://openncp.atlassian.net/secure/RapidBoard.jspa?rapidView=2
- Issues have been discussed, prioritized and estimated for correction.
- Corrections will start to come up during the current week, accordingly to the developers availability;
- Please take in consideration that we are in the midle of the two week test period given to the PNs, so other issues may arise along the week.
- PN QA Stage end - 9 December
- OpenNCP 2.1.0 (GOLD release) - 18Dec
a.1) Central Support Services (migration)
- Progress and Impedements??
- IMPEDEMENT: The current installation API does not work and the current provider says that they don't have the knowledge to make it work.
- SOLUTION: Obtaian the full database, install a compatible instance from RedMind, connect to the old database, and the try the API for import it to Jira.
- Estimated operation time: 8h.
b) Documentation preparing
- [LKM] epSOS Technical Aspects review, in order to include OpenNCP references:
- [LKM] OpenNCP General Presentation
- [DONE] OpenNCP Installation Manual Overview
- OpenNCP Installation Overview
- [LKM] epSOS D 3.B.2 document
- Articulate with MM, but without feedback so far;
c) Knowledge sharing
- Knowledge sharing & Collaborative Design
- Have been already presented to TPM and NEPC, and now is waiting for support and engagement from PNs and other project that may be interested in epSOS technological deliveries
...