Software Change, Configuration and Release Management Training

Course 342

  • Duration: 3 days
  • Language: English
  • 17 NASBA CPE Credits (live, in-class training only)
  • 17 PMI PDUs
  • Level: Foundation
Get This Course $2,650
  • 3-day instructor-led training course
  • After-course instructor coaching benefit
  • Learning Tree end-of-course exam included
  • Earn 17 NASBA credits (live, in-class training only)
#342
  • Guaranteed to Run - you can rest assured that the class will not be cancelled.
    Dec 7 - 9 9:00 AM - 4:30 PM EST
    Washington, DC or Virtual
  • Mar 8 - 10 9:00 AM - 4:30 PM EST
    Herndon, VA or Virtual
  • Jun 7 - 9 9:00 AM - 4:30 PM EDT
    Washington, DC or Virtual
  • Sep 6 - 8 9:00 AM - 4:30 PM EDT
    Herndon, VA or Virtual

Increase efficiency, and decrease maintenance time and development costs with this Software Control Management (SCM) training. In this course, you practice configuration activities — such as configuration planning, change control and management, system building, and version and release management — and learn how the application core processes of SCM contribute to the success of a software project.

  • Familiarity with the software development life cycle

Software Change, Configuration and Release Management Training Delivery Methods

  • After-course instructor coaching benefit
  • Learning Tree end-of-course exam included

Software Change, Configuration and Release Management Training Course Benefits

Implement and effectively lead SCM activitiesMatch project needs to CM process capabilityConstruct a CM plan for traditional and Agile projectsManage requests by specifying Configuration Control procedures

Software Configuration Management Course Outline

Analyzing business factors driving CM

  • Determining causes of failure in project scenarios
  • Positioning strong internal CM controls
  • Controlling quality in the development life cycle
  • Releasing stable configurations

Demystifying core CM processes

  • Configuration Identification
  • Version Management
  • Configuration Control
  • Change Management
  • Configuration Status Accounting
  • Reporting
  • Configuration Audits
  • Compliance
  • Build and Release Management

Deriving candidate items for the project

  • Extracting CIs from the product and the project
  • Itemizing six steps to bring a work product under configuration management control

Categorizing and naming items

  • Devising an effective naming scheme
  • Classifying items based on the nature of the project
  • Aligning a CI into one of four categories

Baselining CIs

  • Defining baselining procedures and creating a checklist
  • Declaring configuration or phase baselines
  • Checking CIs into a repository

Determining roles and responsibilities

  • Establishing an infrastructure to manage project change
  • Comparing change control from a traditional to an Agile perspective
  • Specifying the role of the SCM team

Creating a change control process

  • Establishing change control procedures
  • Facilitating change from requirements through maintenance

Distinguishing between defects and enhancements

  • Processing a change request
  • Investigating defects and deciding corrective action
  • Evaluating urgency
  • Determining severity
  • Prioritize

Planning the reporting requirements

  • Identifying reports required in each phase of CM
  • Determining the communication needs of stakeholders
  • Improving processing by using a configuration database

Matching reporting needs to development life cycle

  • Anticipating report types by role types
  • Planning what to collect in order to report
  • Adding CSA requirements to vendor contracts

Designing Configuration Audits

  • Distinguishing between QA and SCM activities
  • Clarifying types of SCM audits
  • Timing audits throughout the development life cycle
  • FCA and PCA checklists
  • Baseline and release audits

Assessing release readiness

  • Ensuring the documentation matches the product
  • Verifying product configuration

Ensuring consistency through the build process

  • Establishing independence by separating development from the build
  • Managing unique code lines and versions
  • Knowing why and when to branch and use variants

Specifying the product release process

  • Planning a release strategy
  • Resources needed for a smooth release process
  • Matching process steps to release types
  • Positioning Quality Gates in the development life cycle
  • Timing the release appropriately

Need Help Finding The Right Training Solution?

Our training advisors are here for you.

Course FAQs

Software Configuration Management (SCM) helps organizations manage, organize, and control the development process by tracking the changes in software. SCM can determine what was changed and who changed it, as well as how to replicate it across hosts.

Yes! We know your busy work schedule may prevent you from getting to one of our classrooms which is why we offer convenient online training to meet your needs wherever you want, including online training.

Chat With Us