The NoiPA Cloudify Program has geared up into the implementation phase to finally put in practice the system requirements defined through the “User Centricity Approach”. As described in the section “Tools and work methodologies” in this portal, this approach will be used to guarantee the user centricity and the development of a system designed according to the needs and experiences of the users.

With the aim of following an approach that is more focused on the final user, the Direction of Informative Systems and Innovation (Direzione dei Sistemi informativi e dell’Innovazione - DSII) has worked up until now towards the definition of those software developments functional requirements, that will be managed conforming to the “Agile” methodology. This will lead to a reduction of the time needed to release the functionalities and it will guarantee a clearer review process of the produced outputs.

As from July up until the 30^th of September 2017, the Development Teams will be committed to the building of the first software components, functional to the supply of “Built-in” services, divided into Authority Records Office (Anagrafica Enti) and reference structures, Employees Records Office (Anagrafica dipendenti), User Management (Gestione Utenze), Roles and safety functionalities related, and, eventually, Documentary Management (Gestione documentale). All the Teams will be highly committed to the work because of the tight schedule of only 12 weeks in which all the required services will be delivered.

This is why, in order to guarantee coherence with both time and quality, each one of the requirements to be implemented, is going to be presented to the Development Teams by the Product Owners whose task will be to represent the needs of the final user. Moreover, each Development Team is composed of:

• A Scrum Master: the person in charge of the monitoring of the Development Team during its activities, by facilitating the understanding of the requirements, smoothening the dialogue with the Product Owner and identifying the implementation priorities;
• A Technical Leader: the person in charge of designing the technological solution and subdividing it in activities that are going to be assigned to individual developers;
• Ten Developers: those ones who actively contribute to the creation/compilation of the software code that will be released.

Each development activity (also defined as “Sprint”), in accordance to the methodology adopted, will have a fixed realization time of four weeks. At the beginning of each development activity there is going to be a moment for planning the activity itself, in which it will be defined which are the priorities of the functionalities to be realized. The progress status of the activities is monitored every day so to promptly intervene with adjustments and corrections.

Upon conclusion of the software development activities there is going to be a moment to review and share the produced results in favour of future developments.