1 / 9

MyOcean Change Management & Baseline Control

MyOcean Change Management & Baseline Control. WP2. MyOcean PRR, Roma, 2011 April 29 th. Changes arise. Changes arise and are unavoidable: Discrepancies with the agreed System / Service / Product requirements baselines: anomalies

temira
Download Presentation

MyOcean Change Management & Baseline Control

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MyOcean Change Management & Baseline Control WP2 MyOcean PRR, Roma, 2011 April 29th

  2. Changes arise • Changes arise and are unavoidable: • Discrepancies with the agreed System / Service / Product requirements baselines: anomalies • New identified needs or improvements, involving updates of requirements and baseline control: evolutions • Modifications of the IT infrastructure, not under MyOcean control and without effect on the rest of the System / Service: notifications • Changes originate from: • Within the Project: • System Development Teams • Oceanographic Product Contributors (Product Managers) • IT infrastructure Contributors (Service Managers) • Outside the Project: • Users’ feedbacks and requests • MyOcean Stakeholders

  3. Changes arise and they are numerous • Changes may be related to : • The System (automated capabilities) • Anomalies with respect of expected behaviour (detected by IV&V activities) • Evolutions of desired behaviour (asked by users, stakeholders or project members) • The Products • Anomalies / Evolutions in Products descriptions, quality or performances • Anomalies / Evolutions in Product Management processes (including Catalogue Management). • The IT Infrastructure Support Services • Anomalies / Evolutions / Notifications on the deployed components of the IT Infrastructure (DSL & HDL).Examples : • Notification of a disk capacity change on an operational sub system, • Evolution of the IT CMDB involving the transition (acceptance) of a new released system or sub system in the operational environment. • Anomalies / Evolutions in IT Service Management processes (including Service Desk). MyOcean PRR, Roma, 2011 April 29th

  4. Changes must be controlled • A process to control, assess and prioritize changes • Request For Change (RFC) Lifecycle • Changes are not done savagely • They evolve under control and are planned through defined steps : • Open, • Analyzed, • Accepted or Refused, • In progress, • Implemented, • Tested, • Validated, • Closed. • Decisions are made in periodic SCAMG meetings (Service/System Change Approval and Management Group) : • In Change Control Review, the SCAMG assesses the analyzed RFCs and schedule them for future and defined releases. • In Delivery Readiness Inspection, the SCAMG assesses the RFCs that are already tested and scheduled for the next release. SCAMG Decision in CCR SCAMG Decision in DRI MyOcean PRR, Roma, 2011 April 29th

  5. Change Management is organized Project Managers, Stakeholders Users Answers RFCs (MSWord Form) RFCs (MSWord Form) Change Manager SCAMG chairwoman (WP2.2) System Change Manager (WP2.1) IT Infrastructure Change Manager (WP16) Service Managers & Contributors System Development Teams Routing Consistency IT Infrastructure RFCs (tooled) System RFCs (tooled) + Service Desk(s) Products Change Manager (WP17) +Engineering, PMO • Members : • Permanent members, 3 co chairs: Simon (WP2.2), Joël (WP2.1), Michèle (WP1) • Change managers (MyOcean Change Manager, system, products, IT services) • On demand : QUARG, experts (PCs, sub-systems) + SCAMG members Products RFCs (tooled) Product Managers & Contributors + Catalogue Managers MyOcean PRR, Roma, 2011 April 29th

  6. Changes are under control and monitored Necessary automation to share and update RFC information : Jira Currently 78 RFCs by assignee by type by status by filtering criteria MyOcean PRR, Roma, 2011 April 29th

  7. RFC (sample) MyOcean PRR, Roma, 2011 April 29th

  8. RFC (sample, continued) MyOcean PRR, Roma, 2011 April 29th

  9. RFC (sample, continued) – edition mode MyOcean PRR, Roma, 2011 April 29th

More Related