T2S high level programme plan and work streams First meeting of the T2S central bank experts network 16-17 March 2009 Flora Laszlo T2S Division Technical Programme Management European Central Bank 1
Agenda Programme management - planning of work Building the plan top down and bottom up Workstreams - objectives and main deliverables High level plan and major dependencies between the workstreams Rolling plans - monitoring 2
Programme management planning of project work Final goal is to have a secure, legally sound and wellfunctioning system In order to achieve this target: plan tasks and the way of executing them; create a feasible work plan; schedule the tasks; visualise them; track the status and revise the future plans (if needed). High level programme plan and short term rolling plans 3
Building the plan Top-down approach high level plan: Identification of 9 core workstreams, 2 supporting and 2 value adding works streams Gather information for core workstreams and prepare a high level plan Consolidate these high level plans into a master plan Bottom-up approach short term rolling plans: Detailed plans for the next 6 months for each core workstream Monitoring status, rolling them over Each core workstream has: Its general objectives and main deliverables Interdependencies with other workstreams and tasks Timing 4
The workstreams 9 core workstreams I Governance II User requirements III Functional Specifications IV Non-Functional Specifications V Technical Infrastructure VI Financial framework VII Legal framework VIII Testing and Migration IX Information Security Management 2 value-adding workstreams Harmonisation Non-euro business 2 supporting workstreams Programme management Communication 5
Objectives and main deliverables of the core workstreams I. Governance what is the appropriate decision making structure? responsibilities within the Eurosystem Document(s) on governance arrangements II. III. User requirements which service T2S should deliver (UR)? various changes proposed by stakeholders Functional specifications basis for the 4CB to develop the T2S application update of the GFS/UDFS triggered by UR change requests UR documents (annual) Change requests to UR GFS document(s) UDFS document(s) User handbook (UHB) 6
Objectives and main deliverables of the core workstreams (cont.) IV. Non-functional specifications arrangements on technical performance of system (processing capacity, response time etc) operational requirements (support, escalation procedures etc) V. Technical infrastructure building the technical system VI. Financial framework Cost assessment of the 4CB Fees received from CSDs SLA with 4CB SLA with CSDs Manual of Operational Procedures (MOP) Technical design Testing and production platforms Conditional final offer Pricing policy Pricing scheme and its implementation 7
Objectives and main deliverables of the core workstreams (cont) VII. Legal framework contractual relationship of CSDs with Eurosystem Eurosystem internal legal set-up VIII. Testing and migration acceptance of the software application (on the basis of UR and UDFS) verification of functions (user tests) move the settlement activity to T2S IX. Information security policy Check of confidentiality, integrity and availability of information in T2S management and operations Contracts with CSD Intra-Eurosystem arrangements Other arrangements (noneuro NCB and third party providers) Testing strategy, testing plans Migration strategy, migration plans Acceptance test; user test Information Security Policy Sec. requirements & controls Risk analysis 8 Security assessment report
I. Governance, IV. non-functional specifications, VI. financial, IX. information security and VII. legal workstreams Governance: substantial elements of governance Governance arrangements for the operation phase Technical and operational commitments: substantial elements of SLAs Pricing policy Security Requirements/controls Pricing scheme Final SLAs Security Assessment Report MoU Framework Agreement Final agreements for operation phase (CSD, internal Eurosystem) Q1 2009 Q2 2009 Q3 2009 Q4 2009 Q1 2010 Q2 2010 Q3 2010 Q4 2010 Q1 2011 Q2 2011 Q3 2011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Q1 2013 Q2 2013 9
II. User requirements, III. functional specifications, V. technical infrastructure and VIII. testing/migration workstreams User requirements management: URD 4.1 URD 5.0 URD 6.0 GFS 2.0 UDFS 1.0 UDFS 2.0 UDFS 3.0 UHB 1.0 UHB 2.0 Test platform Production platform Testing and migration strategies Acceptance test plans Start user testing Q1 2009 Q2 2009 Q3 2009 Q4 2009 Q1 2010 Q2 2010 Q3 2010 Q4 2010 Q1 2011 Q2 2011 Q3 2011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Q1 2013 Q2 2013 10
Major dependencies between the workstreams Harmonisation Non-euro business II. User requirements III. functional specifications V. technical infrastructure VIII. Testing and migration G O IX. Information security IV. non-functional specifications L I V E I. Governance VII. legal VI. financial 11
Rolling plans Planning and monitoring the activities at a more granular level with a detailed 6 month rolling plan Summarising the workstream reports, holding status review meetings, discussing task interdependencies Monitoring progress compared to previous cycle and to the high level plan top down meets bottom up! Regular status tracking internally and presentations to the AG 12
Rolling plans 13
Questions 14