Updated DCC Release Management Policy

Transcription

1 To: SEC Parties, SEC Technical Subcommittee 2 nd Floor, Ibex House Minories London EC3N 1DY 23 December 2015 Dear colleague, Updated Purpose The purpose of this letter is to seek your views on the updated DCC Release Management Policy and the future content of the accompanying DCC Release Management Guidance (together the DCC Release Management Approach Document ). The proposed DCC Release Management Approach Document is set out in Appendix A of this letter. Background Section H8.9 of the SEC requires that DCC maintains a policy for Release Management. On 18th September 2015, DCC released a consultation 1 on an enduring DCC Release Management Policy. In light of stakeholder responses, DCC has created a new document: the DCC Release Management Approach Document, which incorporates the and the DCC Release Management Guidance. DCC notes that the contains only the policy information required by SEC Sections H8.9 and H8.10. The DCC Release Management Guidance will contain more detailed information required by Parties in relation to new Releases of DCC System functionality. The content of the DCC Release Management Guidance is not required by the SEC and will be added in early The Release Management Guidance will be based largely on information requested by Parties (including consultation feedback). DCC Release Management Approach Document DCC Release Management Policy (Annex A) Release Management Guidance (Annex B) 1 Consultation on DCC Enduring Release Management Policy, DCC Public

2 This structural change has been made to provide clarity on the scope and responsibilities of DCC in relation to Release Management as suggested by a number of Parties in their responses to DCC s September consultation. DCC also received comments relating to the role of DCC in refining change, the applicability of the Release Management model (previously 8-step, now 7-step) and information provided to industry at each stage in the Release Management cycle. DCC has endeavoured to reflect these comments in the revised Policy. Consultation questions DCC invites parties to respond to the following questions: Q1 Q2 Do you agree with the content of the DCC s Release Management Policy (Annex A)? Where you do not agree, please provide rationale. In relation to Releases of DCC System functionality, what information would you find useful in the DCC Release Management Guidance Document (Annex B)? Next steps Please provide responses by 29 January 2016 to DCC at contact@smartdcc.co.uk. If you have any questions in relation to the content of this consultation, please contact Eliot.Miles@smartdcc.co.uk. Responses may be published on the DCC website. Please state whether all, or any part, of your review is confidential. Please note that responses in their entirety (including any text marked confidential) may be made available to the Department of Energy and Climate Change (DECC) and the Gas and Electricity Markets Authority (the Authority). If you have questions about our approach to consultations, please contact our Regulation Manager at richard.sullivan@smartdcc.co.uk. Yours faithfully, Eliot Miles Head of Design, DCC DCC Public 2

3 DCC Release Management Approach Document Incorporating the and the DCC Release Management Guidance Release date: 23 December 2015 Consultation closes 29 January 2016 Classification: DCC Public

4 Contents 1 Introduction Purpose Requirements Annex A: Scope of the Development and timing of Releases Prioritising Change Source of changes under the Seven-Phase Release Management Model Supporting Documentation Definitions Annex B: DCC Release Management Guidance... 9 DCC Public Page 2 of 11

5 1 Introduction 1.1 Purpose DCC has a Smart Energy Code (SEC) obligation to develop a (SEC Section H8.9), which requires that DCC ensures that it plans, schedules and controls the building, testing and deployment of releases of IT updates, procedures and processes in respect of the DCC Internal Systems and/or the Parse and Correlate Software in accordance with a policy for Release Management (the ). The covers DCC Internal Systems and Parse and Correlate Software only, whereas the Panel Release Management Policy covers matters relating to the implementation of approved Modification Proposals. In order to account for various sources of change and to fully inform Stakeholders of DCC s Systems, this DCC Release Management Approach Document comprises two parts: 1) the ( the Policy ) in Annex A of this document, meeting the requirements set out in the SEC and covering changes to the following: a. DCC Internal Systems (e.g. defect remediation, continuous improvement); and b. Parse and Correlate Software. 2) DCC Release Management Guidance ( the Guidance ) in Annex B of this document, providing additional information in respect of how DCC will plan its activities that relate to all changes to the DCC Total System, including (in addition to those listed above): a. SEC Modification Proposals; b. New Services and Products (not introduced through SEC Modifications); c. Elective Communication Services; and d. Value Added Services. 1.2 Requirements The scope of the is defined in SEC Section H8.10, which requires DCC to ensure the : a) defines the scope of the matters that are to be subject to the policy in a manner consistent with the Service Management Standards; b) includes a mechanism for setting priorities for different types of such matters; c) defines periods of change-freeze where no such matters may be implemented; and d) defines periods of notice to be given to the Stakeholders prior to the implementation of such matters. In respect of the specific systems that are the subject of the (namely DCC Internal Systems and the Parse and Correlate Software): for DCC Internal Systems, SEC Section H8.8 sets out the steps that DCC must take when proposing a change; and for Parse and Correlate Software, SEC Section H8.11 sets out the steps that DCC must take when proposing to make a change. Provisions in respect of changes to other systems are set out in the SEC (in the case of Modifications and Elective Services) and in DCC s Licence (in the case of Value Added Services). DCC Public Page 3 of 11

6 2 Annex A: 2.1 Scope of the The applies to all Releases from Release 2, inclusive. Any Releases of the DCC Systems prior to Release 2 are transitional Releases. For the purposes of this document, a Release is defined as a group of approved changes which are implemented as one package, allowing implementation of multiple changes simultaneously. SEC Modification Proposals are not discussed in DCC s Release Management Policy, however Releases of the consequential DCC Total System Changes are covered in DCC s Release Management Guidance. 2.2 Development and timing of Releases In order to discharge its SEC obligations in relation to changes to DCC Internal Systems and the Parse and Correlate Software, DCC will typically follow a Release cycle which comprises a set of three scheduled Releases each year. The schedule release cycle will be the last Thursday in February; the last Thursday in June; and the first Thursday in November. These dates have been selected to align with the Release schedules within the SEC and other energy codes Standard Release Management (SRM) The Standard Release Management ( SRM ) approach will use the defined and phased approach set out in section 2.5 of this document, with supporting milestones that will provide clarity and certainty for Stakeholders. SRM Releases will go live according to the scheduled Releases. Typically, the majority of changes will be allocated to a scheduled Release Urgent Release Management (URM) The URM process is provided to deal with urgent changes in relation to changes to DCC Internal Systems and the Parse and Correlate Software. The URM process will follow the same phases as set out in section 2.5 of this Policy, however DCC will propose milestone dates to reflect the nature of the urgent change requirements. Typically, this will result in compressed timescales for certain phases, for example in relation to consultation, and between the completion of UAT (DCC s acceptance testing of the solution, prior to testing with Stakeholders Phase 5 of 7 in DCC s Release Management Model) and Release. Where an Urgent Release is required, additional resources and costs would typically be required to implement an Urgent Release. A truncated Urgent Release timetable will be determined and published, following consultation with Stakeholders. 2.3 Prioritising Change DCC will take the following in to account, when prioritising DCC Internal Systems and Parse and Correlate Software changes for Releases: Views of Stakeholders; Benefits delivered through the change; Cost of delivering the change; An assessment of risk (including security risks); and Scheduling of other changes to DCC Systems. DCC Public Page 4 of 11

7 2.4 Source of changes under the DCC Internal Systems changes The definition of DCC Internal Systems is set out in SEC Section A1.1. Changes to DCC Internal Systems may be identified as a result of: defects identified in DCC s Internal Systems, which require amendment either in a scheduled Release or (in exceptional circumstances) an Urgent Release. Such defects may affect Stakeholders of DCC Total Systems, or may be resolved without any Stakeholder impact; or continuous improvement as part of the ITIL-based operations, DCC will undertake continuous improvement activities and will typically implement identified changes as part of a scheduled Release. The changes will be identified, designed, built, tested and deployed in accordance with DCC s Seven-Phase Release Management Model, as set out in section 2.5 of this document and in accordance with the relevant provisions of Section H of the SEC (including Section H8.8 and Section H14.36) Parse and Correlate Changes Obligations in respect of changes to the Parse and Correlate Software are set out in Section H of the SEC. The changes will be identified, designed, built, tested and deployed in accordance with DCC s Seven-Phase Release Management Model, as set out in section 2.5 of this document and in accordance with the relevant provisions of Section H of the SEC (SEC Section H11). 2.5 Seven-Phase Release Management Model The DCC Seven-Phase Release Management Model governs the phases of identification, design, build, test and deployment of changes that relate to the. The Seven-Phase Release Management Model is summarised below. The DCC s phased approach is consistent with DCC s Development Plan 2. 2 DCC Development Plan; DCC Public Page 5 of 11

8 Phase / Title Phase 1 Requirements gathering Phase 2 Requirements refinement Phase 3 Plan & Contract, Requirements Freeze Phase 4 Design and build Phase 5 DCC testing Phase 6 User testing Phase 7 Release Steps Confirm and communicate the requirement to plan a new scheduled Release (24 months prior to Release). Business statement of scope for Release. Receipt of requirements for proposed changes (from DCC and/or Stakeholders). An indicative requirement submission freeze of 12 months prior to the Release Date used as a guide (i.e. no further requirements will be accepted for the target Release). Continuation of the above process to refine and prioritise requirements (per SEC Section H8.9). Costing and shaping to ensure positive business case can be maintained for the Release and that the scope of Release can be delivered within the defined timescales. DCC evaluates the change. If it is determined that a Modification to the SEC is required, then it will be submitted through the Modification Process (and will therefore not be subject to the DCC s Release Management Policy). DCC prepares a report setting out the nature of the change and its impact. If the change is likely to materially impact Stakeholders, DCC will consult with Stakeholders and the Technical Sub-Committee (as set out in Section H8.8 of SEC for DCC Internal System changes or SEC Section H8.12 for the Parse and Correlate Software) to determine the urgency and priority of the change. Development of plans and procurement of solution(s) to meet the agreed requirements. Conclude consultation. Closure of requirements based on consultation responses. Detailed design and build by Service Providers/suppliers. Functional and non-functional testing by DCC, including integration with existing systems. Complete integration testing, regression testing and roll-back testing. Once complete, 6 month window for DCC Systems Stakeholder testing can commence. Stakeholders may test against any new functionality or Stakeholder-affecting enhancements/fixes (in accordance with SEC Sections H11.8 and H14.36). DCC releases the updated systems into the live environment in accordance with the relevant Release schedule. DCC monitors for problems and if necessary, activates the roll-back plan. Table 1: DCC Seven-Phase Release Management Model DCC consultation / interaction with Stakeholders Release notified to Stakeholders. Stakeholders may submit proposed changes. Details of proposed changes available to Stakeholders. DCC engages with Stakeholders to assure alignment of requirements and delivery timetable. DCC engages with Stakeholders to agree design freeze and finalise Release timetable. Periodic progress updates to Stakeholders. Progress reporting and design/technical information transfer, as required. DCC provides Stakeholders with instructions and support for testing against the planned Release content. Stakeholders informed of success (or otherwise) of the Release s introduction. DCC Public Page 6 of 11

9 2.6 Supporting Documentation In support of the Seven-Phase Release Management Model, DCC will manage planning for the deployment and completion of all documentation associated with each scheduled Release or Urgent Release. Documentation and details of all Releases will be made available to Users via the Self Service Interface (SSI) and to other Stakeholders via the Release Schedule (accessible via the DCC Website). The Release Schedule will be updated and published as required. Release Notes for each Release will also be made available, which will detail as a minimum: Changes included in the Release, which will include: o Changes to DCC Internal Systems; o Changes to the Parse and Correlate Software; Statement of Business Requirements; Service(s) impacted by the Release; Documents to be amended as a result of the Release (including installation guides, which for Parse and Correlate will be in accordance with the provisions of SEC Section H11); Release Communications Plan; Release Rollback Plan; and Release Plan key dates. DCC Public Page 7 of 11

10 2.7 Definitions Where defined terms are used in the and are defined in Section A of the SEC, the definitions as set out in the SEC will apply. For defined terms not set out in the SEC, the following definitions apply. Term Abbr. Description Release A group of approved changes to DCC Internal Systems and Parse and Correlate Software which are implemented as one package, allowing implementation of multiple changes simultaneously Release 2 The first Release subsequent to the full implementation of the DCC plan, as approved by the Secretary of State, in accordance with DCC s Licence Condition 13 Release Management Policy RMP How DCC will manage enduring Release Management for DCC Internal System Changes and Releases of Parse and Correlate Software beyond the commencement of DCC live operations Release Plan A plan setting out the phases of a particular DCC Internal System or Parse & Correlate Release with start and end dates for each phase Stakeholder A party potentially impacted by changes to DCC Internal Systems or Parse and Correlate Software e.g. Users, RDPs, non-users and non-parties (e.g. meter manufacturers) Standard Release Management SRM Release Management that follows the three scheduled Releases, as set out in section 2.2 of this Policy Urgent Release Management URM Management of Releases that have to follow an accelerated Release schedule, as set out in section of this Policy DCC Public Page 8 of 11

11 3 Annex B: DCC Release Management Guidance [To be added in early 2016, following this consultation and further stakeholder engagement] DCC Public Page 9 of 11