1 / 58

Change,Configuration and Release Management

The only Constant is Change. Change,Configuration and Release Management. Ed McMahon Chair, CMSG October 2001. To be the voice of CM in the UK To promote the disciplines of Change, Configuration and Release Management To actively pursue the establishment of standards

craig
Download Presentation

Change,Configuration and Release Management

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. The only Constant is Change Change,Configuration and Release Management Ed McMahon Chair, CMSG October 2001

  2. To be the voice of CM in the UK To promote the disciplines of Change, Configuration and Release Management To actively pursue the establishment of standards To introduce ISEB approved education and examinations….. WHY? CMSG: Aims and Objectives

  3. BSI PD0005 Service Management framework Service Design & Management Processes Security Service Level Management Capacity Management Management Service Reporting Availability Financial & Service Control Processes Management Continuity Configuration Management Change Management Release Relationship Processes Processes Resolution Processes Business Relationship Management Release Incident Management Management Problem Management Supplier Management Automation

  4. Organisation Change Control Plans Configuration Management Quality in a project environment Controls Stages Management of Risk Projects & PRINCE Source: OGC’s PRINCE ® methodology PRINCE is a registered trademark of OGC

  5. Why? • Related processes with a direct impact on Quality • Essential disciplines that must be planned for and • Implemented early in the Lifecycle • Provides key information and input to • Project Management • Testing • Quality Management • Audit and Verification.

  6. Day events and seminars Running introductory sessions on the disciplines Presentations at other SIGS Introduction of an education syllabus Linking with ITIL and the ISM Levels. Accomplishing these Objectives?

  7. Time. Committee work is voluntary Money. Group is self financing. Position. Not seen by industry OR Seen but not recognised as effective. Problems and Issues

  8. Higher Profile Semi-dedicated resource from BCS to support volunteers Financial support from BCS A higher profile from BCS itself. BCS promotion of the SIGS What is required? - Discussion point.

  9. Make the group more attractive. Appeal to a wider audience. Appeal to a Management audience. Present solutions as well as awareness Promote ISEB qualifications in recognised disciplines - Train practitioners Promote appropriate ISM Level within organisations. What can we do ourselves?

  10. From Configuration Management to Change, Release and Configuration Management. Long and heated arguments: against and for Esoteric arguments - not commercial. Easier to Sell? Name Change

  11. Proposed Courses and syllabus for two levels Essential: Target BCS ISM Level 3 for Change, Configuration & Release Management 2 days, 14 hours, 1 hour exam ISEB Business Systems Development: Certificate in Change, Configuration & Release Management Essentials Intermediate/Practitioners: Target BCS ISM Level 4-5 for Asset & Configuration Management 3-4 days, 20 hours, 2 Assignments, 1 hour exam ISEB Certificate in Change, Configuration & Release Management Intermediate/Practitioners Education

  12. Conformance Management Awareness Assessments : BS 15000 Standard Achieve this Manager’s Overview PD0005 Process Definition Capability & Maturity ITIL Solutions In-house procedures ITIL Best Practice & Standards Links

  13. Change, Configuration and Release Management Structure, Relationships and Content

  14. ITIL Version 2 Service Support Configuration Mgt. -identifies impact & updates records The Service Desk Release Mgt. -controls release of software & hardware to implement the change Incident Mgt. -logs & resolves incidents Problem Mgt. -identifies root cause & minimises effect Change Mgt. - assesses & authorises change

  15. Change Management - Activities Manage Requests For Change Approve & schedule changes Change Management Oversee change building, testing and implementation Review all implemented changes

  16. RFCs & Configuration Management Initial Change Request Configuration Management Assess Impact & Proposal Software CI to be changed Related Training CI C M D B Related Operating CI Related Hardware CI Combined Change Request

  17. Change Procedure Raise RFC CMDB Manage, monitor, report, chase, RFCs Assess Impact Identify CIs Approve Release CIs CMDB Implement Update CIs Post Impl. Review Audit CIs Close RFC

  18. Configuration Management Objectives • Enabling control by monitoring and maintaining information on: • Resources and configurations needed to deliver projects, systems and services • Configuration Item (CI) status and history • CI relationships • Providing information on the infrastructure for all other processes & Programme/IT/IS Management

  19. Configuration Management - activities Management information Identification & Naming Verification & Audit Configuration Management Control Status Accounting Need to be planned!

  20. Configuration Control Configuration Control is responsible for the way in which we put our projects and systems together. It allows us to assign and associate a series of selected elements to form a Release Unit or Release Package (i.e. Set) Pre-grouped elements formed into identifiable packages are what we move through the life cycle.

  21. Configuration Control Procedures • Depend on Configuration Item Type: • Check-out/Check-in • Impact Analysis • Versioning • Move/Copy/Build • Baselining - packages, systems & environments • Environment Restore • System/Package/Change Backout/restore • Security

  22. Build • Inputs must be from controlled library or repository • Identify environment, inputs, outputs and build tools • Identify dependencies to permit rebuilding later on & order! IN OUT Build Tools & Clean Environment Built Environment

  23. Configuration Management Categories include • Programmes/Projects • Services • Systems • Hardware • Software • Documentation • Environment • People • Data Items you want to control are called Configuration Items (CIs) Data about all the CIs are held in the Configuration Management System or Database (CMDB)

  24. A Configuration Item Is needed to deliver a system/product/service Is uniquely identifiable Is subject to change Can be managed A Configuration Item Belongs to a CI category Has relationships Has descriptive attributes Changes status over time Configuration Item (CI)

  25. Configuration Item (CI) Attributes CI number Name Category Description Security Own attributes Version Euro Size/Capacity Supplier Status Support Group Location Owner

  26. CIs - scope and detail Service People resources Hardware Software Documen- tation Environ- ment D E T A I L Network printer PC Local printer Bundled s/w No break power VDU Keyboard CPU W.P. DBMS E-mail SLA SCOPE

  27. Web World - What to Control? Multimedia Formats URL Servers Layout SMIL XML Editors HTML Tag List Databases VRML Perl Java Design HTML4 JavaScript Tools Plugins CGI ASP Cascading Style Sheets Open Source Protocols Images Virtual Library Software Icons Flash Tutorials Navigation Security Domains UNIX DHTML Browsers Graphics

  28. Role of Status Accounting What have weConfigured? I’m doing a release, take the baselines for me please. OK, I’ll Get the pictures Recorded Baselines

  29. Desktop ‘As Built’ Desktop ‘Live’ App. Server ‘As Built’ NT Server ‘As Built’ Appl. Server ‘Live’ NT Server ‘Live’ Configuration Audit ‘As Built’ Baseline Records Live Infrastructure Audit Tools & Scripts • Perform audit • Log exceptions • Notify exceptions • Investigate exceptions • Follow up & resolve

  30. RFC - Scope and Contents Change Sponsor & Originator Software Hardware Justification What, Why, When CIs SLA Documentation Service impact etc.. Change Request (RFC) Environment Category Priority Resource Estimates etc.. Change Advisory Board (if appropriate)

  31. Change Management Process Manage Implement RFC Preparation Categorise Prioritise Authorise Plan Refusal Build CAB Test Approve Release Refusal Implementation Backout Review

  32. Design, develop, build, configure release Fit for Purpose Testing & Release Acceptance Distribution & Installation Release Policy Release Planning Roll-out Planning Comms., Preparation & Training Configuration Management Database and Definitive Software Library ITIL Version 2 Release Management Development Environment Controlled Test Environment Live Environment

  33. Release Management Objectives • Deliver systems that are correctly configured and built first time e.g. 99% of target • Repeatable, consistent process that is cost effective, responsive and flexible • Everyone knows what is happening & when • Accurate updates are fed back to configuration management • Can do OFTEN & QUICKLY! • Maintain quality

  34. Platform & Cultural Challenges Network Computer Mainframes B2B Systems Mobiles Internet Release management Laptops Compact Disks Personal computers Client/server Balancing control of corporate, regulated systems with end user flexibility across platforms

  35. Release Policy 1. Roles & Responsibilities 2. Levels of Authority 8. Business critical times & risks 3. Identification & Packaging Release policy 7. Emergency change 4. Release unit - full/delta 6. Release frequency 5. Release numbering

  36. Release Management Best Practices • Designer/developer should design for change, configuration & release management • Release management should offer advice & info. • Standards, identification, tools, techniques • Release, build and back-out procedures • Re-use of standard procedures & CIs from CM system • Automate installation routines if sensible • Automated one-off jobs need equivalent back-out routines • Design software distribution so that the integrity of software is OK during handling, packaging, delivery & AUTOMATE!

  37. Definitive Software Library Release & Roll-Out CI records CM System Release Record Build New Release Test New Release Distribute release

  38. Release Planning - Why? • What is to be released and to where? • Who is responsible for what? • How it will be done? • How do we know it has worked?

  39. Release Planning • Release contents & schedule • Roll-out planning • Phasing over time and by geographical location, business unit and customers • Site surveys/audits • Obtaining quotes for new hardware, software or installation services • Quality plan • Back-out plans • Acceptance criteria

  40. What Does It Mean? Part 3 - Making it Work.

  41. The Brave New World • No central computer, no single network • A changing environment where anyone can publish information or read it • Information is on any server • And we need to be able to trust our business partners, suppliers, and customers engaging in e-commerce!

  42. B2B value chain WWW By 2003 • More than 500 million users • Dominant growth in Europe where 60% of Web users will live & work • No. of devices will be more than 700 million • B2B will be 90% of all internet traffic & B2B e-commerce may be $7 trillion • Related IT services opportunity is estimated at just under $1 trillion

  43. DEV TEST LIVE World-wide prototype to B2B • Support more data, applications , processes across enterprises • Separate information and services (logical) from infrastructure (physical) • Use remote services (internal & external) • Re-engineered IT infrastructure for maximum cost-effectiveness and reliability

  44. Business Programme Challenges • Short Lead Time to Market • Fast & clear decision making and risk analysis • Ever More Complex Technical Systems • Need to manage variants and dependencies • Needs clear ownership through the lifecycle • High demand for Deliverables from Organisation and Staff • Need to know ‘true’ status

  45. Start with Change Management • Keep It Sufficiently Simple • Appoint Change Manager • Document Scope • Establish Communications • Base it upon • Business Continuity • Necessity but Risk of Change • Ignore Content for now • Appoint a Change Manager

  46. Appoint Change Manager • Use BCS Industry Structure Model • Senior appointment • Business AND IT knowledge • Expert Communicator • Programme and Project knowledge • Service Management knowledge • Risk Management experience • People person • Process Person - Process is everything

  47. Change Manager Process Manager Manage Change and Risk - Defines scope and process - Operates process - Manages data and records - Interface & communicator - Sets targets & measures - Reduce Incidents - Manage risk of change - Process reviews - Efficiency & effectiveness reviews - Manages improvement cycle - Evolve sub-processes - Measure change & effect Quality Parameters & Key Performance Indicators - Establish interfaces/ links with all areas, projects, programmes, service & support - Identify Interface Impacts for Business Impact Change Manager & Team (& all staff) Change Manager Change Administrator

  48. Possible Problems • Systems overload easily • Circumvention of procedures • Excessive over-ruling for strategic expedience • Suppliers • Over-zealousness can lead to analysis-paralysis • Unclear responsibilities and definitions

  49. Possible Problems • Establishing depth and breadth • Interfaces to other systems where CI information is stored • Data collection and maintenance of accuracy • Roles and responsibilities in distributed, client/server environments • Establishing owners for CIs • Over-ambitious schedules and scope • Management commitment to importance of Configuration Management as a foundation block

  50. Potential Benefits • Increased productivity of customers and IT staff • Less adverse impact of changes on services • Ability to absorb a higher level of error-free change helps speed to market & quality of service • Better up-front assessment of the cost and business impact of proposed changes • Reduction in the number of disruptive changes • Reduction in the number of failed changes • Valuable management information

More Related