As part of the New Delivery model according to the priorities defined with
Release 0.9 is proceeding as planned
o Delivery is expected to close by the end of May 2019
The consolidation of the back log is progressing very satisfactorily with the UAT champions.
The next step is now to generate more details on the iterative part :
o This process should start next week
Participants would like more information on the prioritization of these few hundred bugs
o What feasibility for a realistic planning to fix these bugs?
The clock is ticking : 6 months from now
Is it possible to organize a UAT at the end of May to check if the system is working properly?
o What is planned: a demo or a test?
Participants want to have metrics that can be used to evaluate IT4U's performance
o A demo is planned but no testing
o Prioritisation has yet to go forward:
Champions will decide on the basis of criteria in line with business values
A business value will be allocated to each item
The list is systematically implemented in Jira
Meetings with champions are held weekly
This process will be completed by June 19
It will be possible to determine the N of sprints required before the UAT
o This process makes it possible to establish a list of items to be analysed according to
3 essential criteria related to business value:
Bugs or items to fix:
Before the audit
Before the GO LIVE
After the GO live
o It would be useful to have a Sand box at the end of May so that champions can test
and familiarize themselves with the features.
Preparation of the Management Board
o A priori EMA wishes to present the Big Picture to the MB as well as the metrics
defined in the contract
asked to present a precise planning & timeline:
Presentation of IT4U
Sprint 5 and 6 is going according to plan :
o There's just a little delay for sprint 4
Manual testing is complete:
o there is no major deviation
R0.9 does not record any BCM, which is quite reassuring
Sprint 5 of R 0.7 includes 35 of the 52 bugs:
o 17 bugs have already been fixed
o The cycle is scheduled to end on March 13
o There is no UAT planned at the end of R0.9
o From now on, the process will be simplified since there will only be 1 backlog for 1
system that integrates both the development of the Data Base and Safety
Slide 7 showing the Actual % of completion and SPI is indicative of the type of report to be
o Extra note on Schedule Performance Index (SPI):
The Schedule Performance Index indicates how efficiently project is actually
progressing compared to the planned project schedule.
It gives information about the schedule performance of the project.
It is the efficiency of the time utilized on the project:
SPI the performance of time in a unitless dimension:
o > 100%: project ahead of schedule
o = 100%: project on time
o < 100%: project delay
reminded IT4U that it is necessary to focus on monitoring and clearly mention deviations
from the schedule:
Everis has been asked to provide an update for each release on:
Schedule Performance Index
Forecast end date
Baseline end date
Variances between Forecast and Baseline
o This will allow for better monitoring and for clear Project Picture.
Next meeting is planned on 20 March 2019.
A date must be set for the next coordination meeting at the end of March