Scribd Logo
Upload

Welcome to Scribd!

  • 49 views

    ChangeManagement

    Uploaded by

    Anamica Bharti
    This document outlines best practices for change management infrastructure. It discusses establishing a centralized source control library, component versioning, approval processes, testing, and automated rollback capabilities. Foundational requirements include configuration management tools, standardized protocols for remote access and deployment controls. Key benefits are improved software quality, reduced costs, standardized processes, auditability, and reliability through change control.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd

    ChangeManagement

    Uploaded by

    Anamica Bharti
    49 views8 pages
    This document outlines best practices for change management infrastructure. It discusses establishing a centralized source control library, component versioning, approval processes, testing, and automated rollback capabilities. Foundational requirements include configuration management tools, standardized protocols for remote access and deployment controls. Key benefits are improved software quality, reduced costs, standardized processes, auditability, and reliability through change control.

    Original Title

    20040112_ChangeManagement

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document outlines best practices for change management infrastructure. It discusses establishing a centralized source control library, component versioning, approval processes, testing, and automated rollback capabilities. Foundational requirements include configuration management tools, standardized protocols for remote access and deployment controls. Key benefits are improved software quality, reduced costs, standardized processes, auditability, and reliability through change control.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    49 views8 pages

    ChangeManagement

    Uploaded by

    Anamica Bharti
    This document outlines best practices for change management infrastructure. It discusses establishing a centralized source control library, component versioning, approval processes, testing, and automated rollback capabilities. Foundational requirements include configuration management tools, standardized protocols for remote access and deployment controls. Key benefits are improved software quality, reduced costs, standardized processes, auditability, and reliability through change control.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    of 8

    Change Management

    Infrastructure

    1
    Table of Contents
     Introduction
     Business Drivers
     Best Practices Principles
     Infrastructure
     Foundational requirements
     Key Points
     Benefits
    2
    Change Management
    Introduction
    Change
    ChangeManagement
    Management(aka (akaChange
    ChangeControl)
    Control)refers
    refers
    To the process of managing the evolution
    To the process of managing the evolution of of
    Change
    Changeover
    overtime.
    time.The
    TheSoftware
    SoftwareChange
    Change
    Management
    Management process is designed toinsure
    process is designed to insure
    That the software development changes
    That the software development changes
    Initiated
    Initiatedby
    bythe
    thesoftware
    softwareprogramming
    programmingstaff
    staffare:
    are:

     Software Development Life Cycle Controlled, autonomously tested,


    components approved and promoted by the development teams,
    application QA testers and Production Support staff
     Change events documented and communicated in the Change Calendar
     Scheduled & Installed via automated process with associated
    automated rollback ability

    3
    Business Drivers
     Improved software quality
     Significant software development cost reductions
     Industry standards based software configuration
    management best practices
     Specific and repeatable process management for controlling
    change
     Historical change reporting, audit ability and impact analysis
     Reduced risk of system outage or failure - improved system
    availability.
     Compliance to internal and external audit requirements.

    4
    Software Change Management
    Principles
     Centralized Source Control
    Library/Directory Management(Secured)
     Component/Artifact Versioning Control
     Component Promotion Management
     Approval Processing
     Independent/Autonomous QA/UA testing
     Process Flow Software Development
    Lifecycle Control
     Automated Software Component Rollback
     Project and Component level release mgmt
    5
    Foundational Change Management
    Requirements

    Network
    Network Software
    Software
    Configuration
    Configuration Configuration
    ConfigurationManagement
    Management
    Infrastructure
    Infrastructure Infrastructure
    Infrastructure

    Server Farming to provide a •Automated Change Mgmt tool to provide Remote


    hardware infrastructure for basic Directory Browsing for Software Development
    SCM Configuration i.e.: Life Cycle Mgmt across servers
    •Development Servers •Standard TCP/IP Protocols to facilitate cross
    •QA/UA Servers server communications for remote directory
    •Parallel Production Baseline browsing and managing components
    Servers •Automated User Mgmt functionality to control
    •Production Runtime Servers application user access and software development
    life cycle process flow navigation ability
    •Application specific deployment control to
    manage production runtime installation
    6
    Key Points

    Common
    Commonpitfalls
    pitfallsencountered
    encountered
    when
    when establishingan
    establishing an
    SCM
    SCMInfrastructure
    Infrastructure

    •Network Configuration Infrastructure not


    addressed in the initial planning phases (Must be
    in place prior to any physical SCM effort)
    •Implementation not driven down into the
    enterprise with Senior Mgmt Mandates
    •Enterprise culture change not anticipated and not
    included in the project planning phases
    •ROI not fully developed to support project
    implementation costs

    7
    Change Management
    Benefits
    The standardization of processes for change control of new and existing
    applications would significantly reduce the time required for developing software
    components and improving/expediting the pre-production testing and production
    runtime application deployment/rollback process.
    Facilitate the establishment of a core set of requirements guidelines for developing
    new applications by insuring that the all software development life cycle processes
    flow through the same specific and repeatable source code development practices.
    Improved time to market for all software development efforts. A structured
    software development methodology followed by all applications developers.
    More robust impact analysis due to the historical audit trails captured during the
    software development life cycle process.
    Support for more reliable trend analysis reporting to measure developer coding
    standards, production failures and the associated components while reducing
    production downtime by improving the quality of the software product deployed in
    the production environment.
    Last but not least, adherence to both internal and external audit guidelines.

    You might also like