1 OCS Change Management Board 18/04/2013

2 Introduction General Vision Proposed approach Identified requirements Tour de table Agenda

3 Online Collection Software General Vision Main stakeholders: European Commission, ECI organisers and National authorities; All stakeholders more involved into the development of OCS, in particular into the evolution process OCS is and will remain a tool for gathering Statements of Support, nothing less, nothing more EC: responsible for compliance with legal framework and with security requirements

4 What is going to change? EC is inviting the OCS stakeholders to work closer. Two boards, chaired by EC will meet periodically: Change Management Board, responsible for the general orientation of the software Release Management Board, "technical" group responsible for the development and delivery of the software In order to ensure transparency, all the requirements will be managed through the joinup platform

5 Roles of the Change Management Board Orientate the future versions of the Online Collection Software, proposing future changes of the software Review and prioritize the requirements published in joinup Based in the "technical" board feedback, propose the scope of the release or adapt the planning

6 In practice CMB will be composed by up to 15 members from ECI organisers, National authorities, other stakeholders CMB will meet "virtually" on a regular basis to review requirements and plan releases Before each meeting, the secretary of the board will send the agenda of the meeting Minutes of the meetings will be published in joinup

7 OCS Requirements in joinup Go to "Issues" page in joinup: Filter "1.4.0-DD Edition" version Main requirements: Make captcha easier Enable interface customization Links to Social Media Graphical display for the support received Customized error messages Call-back URL