1. Configuration Management Checkpoint

2. Presentation Goals Describe: Describe:  Our interpretation of the Technical Configuration Management charter  What we’ve been doing since the re-org  Current state as we begin Configuration Management  Are our assumptions accurate? Illustrate: Illustrate:  Our understanding of CMII to date  Our approach with implementing CM into BBY  Are we on target?

3. Agenda Post Re-Org (Initial) Deliverables Post Re-Org (Initial) Deliverables Current State Current State Configuration Management II (CMII) Configuration Management II (CMII) Application Hierarchy Application Hierarchy Change Process Change Process Scope & Goals Scope & Goals Go Forward Strategy Go Forward Strategy Q&A Q&A

4. Post Re-Org State of Mind What are our Deliverables? Manage Server configuration with “Police / Auditor” Mentality  Inventory Control, “Definitive Record of Authority”  Audit Deviations  Correlation of Configuration Change to approved Change Mgmt ticket (or lack thereof)  Provide Deviation-to-Standard Configuration Information to Customers  Alignment under ITIL with deployment of CMDB and small number of initial Configuration Items (i.e. – Server Name, Location, etc.)  Become Foundation for key business areas (Issue Mitigation, Release Mgmt, Disaster Recovery, Systems Monitoring)  Role of Software Config Mgmt. unclear (Integration? Top to Bottom? Parallel?)

5. ITIL Definition of CM “Identify, record and report on all IT components that are under the control and scope of Configuration Management.”

6. Current Wintel Engineering State Engineering ‘Flavor’ of the Month Engineering ‘Flavor’ of the Month  Documentation non-existent and/or inconsistent across Engineering team  Information captured not audited or reviewed by interested parties  Engineering against documented Technical Specification is not occurring Byproducts of Current State Byproducts of Current State  Intellectual Capital walks out the door  Corrective Action is the norm  Customer Confusion over varying ‘standards’  Difficult to backfill Engineers due to dissimilar processes  Management of Server / App Configuration hampered due to missing and/or inaccurate information  “Waste Approach” to Server Procurement and Utilization  Ineffective Outage Impact Assessment Capability  Inability to track Device History (what changed?)  Inconsistent License Tracking  Difficult to track end of Lease Information

7. Configuration Management Terms Fun with Acronym’s… Fun with Acronym’s…  CM: Configuration Management  CMM-SW: Capability Maturity Model, Software  Sunsetted in favor of:  CMMI: Capability Maturity Model Integration  SEI: Software Engineering Institute Steward of all Capability Maturity Model-related intellectual Property at Carnegie Mellon University Steward of all Capability Maturity Model-related intellectual Property at Carnegie Mellon University  Open Source approach to CM  CMII: Configuration Management, Version 2 aka ‘CM2’  ICM: Institute of Configuration Management Doing CMM “one version better” and branding it as CMII Doing CMM “one version better” and branding it as CMII Applying CMM principles across the Organization rather than focusing entirely on Software Applying CMM principles across the Organization rather than focusing entirely on Software

8. CMM – Maturity Levels

9. Application Hierarchy

10. Infrastructure Drill-Down

11. Instruction (I) Set Example

12. Master List (ML) Example

13. CMII Mantra Only two types of work that occur in a CM2 organization Only two types of work that occur in a CM2 organization  Time spent Documenting Technical Specifications  Time spent performing work described in Technical Specifications No changes are made to code or Infrastructure unless the Technical Specifications that describe them are documented, validated and approved No changes are made to code or Infrastructure unless the Technical Specifications that describe them are documented, validated and approved

14. Change Process Fast Track

15. End State New (Authorized) Tech Spec. (Rev) describing Configuration Ability to leverage historical Data (how many Rev A’s are still in the environment, what was the original configuration, etc.)

16. Expanding Scope Technology Configuration Management Process MaturityAccountability Audit

17. Configuration Management Goals Accurate inventory of deployed hardware Accurate inventory of deployed hardware Accurate information on CIs and their documentation Accurate information on CIs and their documentation Work is performed according to technical specification Work is performed according to technical specification Integrate a document management system Integrate a document management system Track Configuration deviations Track Configuration deviations Achieve Dev/QA/PROD consistency Achieve Dev/QA/PROD consistency Provide reporting and auditing capabilities Provide reporting and auditing capabilities Transfer software licenses from device to device & track Transfer software licenses from device to device & track Enable more accurate financial & capacity planning Enable more accurate financial & capacity planning Dependencies between apps, devices and services Dependencies between apps, devices and services Disaster Recovery – Leverage CMDB info Disaster Recovery – Leverage CMDB info Help Desk, SOC, Incident and Problem Mgmt tie in Help Desk, SOC, Incident and Problem Mgmt tie in

18. Technical Configuration Management Interfaces

19. Scope Phase 1: Wintel & Unix devices Proposed Phases for the roadmap may include: Network devices Network devices Network Security devices Network Security devices Desktop devices Desktop devices Hand held, PDA devices Hand held, PDA devices Store Servers Store Servers Middleware Middleware

20. Technical Configuration Management Roadmap 2-5 years: Strategic Management 2-5 years: Strategic Management  Planning and long term control over quality, stability and flexibility 6-24 months: Tactical Management (Service Delivery) 6-24 months: Tactical Management (Service Delivery)  To guarantee quality, stability and flexibility  Service Level, Availability Management, Capacity Management, Financial Management 0-6 months: Operational Management (Service Support) 0-6 months: Operational Management (Service Support)  To achieve quality, stability, flexibility  Service Desk, Configuration Management, Incident & Problem Management, Change Management and Release Management Procedures Processes Policies

21. Next Steps Continued Education Continued Education  Training for BSI, ESM, Network, Network Security and Data Center representatives  Ramp up the Technical Configuration Management Team Close the gap between CMM, CMII and ITIL vision with Joe and Lisa Close the gap between CMM, CMII and ITIL vision with Joe and Lisa Integrate roadmap with Software Configuration Management Integrate roadmap with Software Configuration Management Validate and gain buy-in with server teams Validate and gain buy-in with server teams Market CM with all Platform & Production Services Leaders Market CM with all Platform & Production Services Leaders ITIL progress check with Platform & Production Services Leaders ITIL progress check with Platform & Production Services Leaders Define “governing body” to oversee all capabilities Define “governing body” to oversee all capabilities Gain customer buy-in Gain customer buy-in  Approach has to be easily understood and not seen as another hindrance  ITIL recommends we should define things as what the Customer sees as a service (i.e. – ‘EMAIL’) rather than the underlying Technology (i.e. – SMTP, POP3, etc.)

22. Q&A Are we on Target with our assumptions? Are we on Target with our assumptions? Are we in line with upper management’s vision when our capability was created? Are we in line with upper management’s vision when our capability was created? Are there any red flags? Are there any red flags?