Software Change, Configuration and Release Management – In Class Training in SFO

You Will Learn How To:

  • Proactively manage the components of projects
  • Construct a Configuration Management (CM) plan for traditional and Agile projects
  • Choose hardware and software items to control through Configuration Identification
  • Manage requests by specifying Configuration Control procedures

Workshop Activities Include:

  • Matching project needs to CM process capability
  • Coordinating check-in/check-out of CIs from/to the library
  • Designing a change control process
  • Identifying key reports needed for effective CM communications
  • Preparing a CM plan for a project
  • Base-lining a product throughout the project

Talk To Trainers

Your Name*

Your Email*

Phone Number*


Enter the letters or numbers shown above:

Course Info

1. Configuration and Release Management

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

  2. Identifying Configuration Items (CIs)

 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

  Base-lining CIs

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

3. Controlling Change

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

  4. Communicating Configuration Status

 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

5. Auditing in Preparation for a Release

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

 6. Building and Releasing the Product

 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

Who Should Attend

Configuration and release management professionals new to their position, software developers, hardware engineers, testers, project managers and anyone needing a solid foundation in monitoring and controlling a product during the development life cycle.
Sign Up

What is this course about?

Software configuration management (SCM) is a process for facilitating and controlling changes to software products within an organization. This course covers configuration activities such as: configuration planning, change control and management, system building, and version and release management. You learn how the application core processes of SCM contribute to the success of a software project. A software and hardware prototype is used in the case study throughout the course, allowing the concepts of SCM to be applied during workshops and activities.

What background do I need?

No particular programming language or specific software expertise is assumed. Familiarity with a software development life cycle is helpful.

Who will benefit from this course?

The course is valuable to software development and maintenance personnel coding or designing systems, systems administrators and those leading software-intensive activities such as business analysts, project leaders and configuration managers. Anyone involved with software development, integration, maintenance, operations, testing, quality assurance or process improvement benefits from this course.

Does my whole development team need to attend?

While beneficial to entire development teams, providing a foundation for representatives of each group would be a good starting point. It is also not necessary that the entire development team attend at the same time, and onsite options for your company are also available. Please ask your Sales representative if onsite is something of interest to you.

Is the course linked to a specific CM approach, programming language or operating system?

No. The practical techniques that the course advocates are applicable to mainframes, servers, workstations and personal computers across the spectrum of operating systems.

Is the course relevant for all types of programming teams?

Yes. This course is beneficial to one person teams as well as teams with large co-located groups as well as geographically dispersed groups. The course approaches the software development life cycle by considering phases in development, not by aligning with one approach or another. SCM applies at the SDLC phase, regardless of the type, size, language, or budget of a programming project.

Are SCM techniques effective for projects of varying sizes and complexity?

Software expected to have long operational life needs to be maintained and altered over time. It may need to be distributed to multiple locations or modified to run on a different platform. Software in fast-changing Web applications with aggressive, market-drive deadlines also need to be controlled. The control mechanisms built into the software configuration management process ensure that these challenges are understood, controlled and supported. SCM concepts can be applied to any project, regardless of size and complexity.

Are there software packages useful for configuration management? If so, will they be demonstrated during the course?

Yes. The course focuses on the principles and application of SCM processes, taking a tool-independent approach. When you return to your work environment, the SCM principles built into the various tools of the industry will be evident and will then be able to be properly used according to the software vendor’s implementation.

How much time is spent on each topic?

Content Hours
Foundation for configuration and release management 3.0
Identifying Configuration Items (CIs) 3.0
Controlling change 3.0
Communicating configuration status 2.0
Auditing in preparation for a release 2.0
Deciding on a build strategy 2.0
Developing a release strategy 2.0

Times, including the workshops, are estimates; exact times may vary according to the needs of each class.

How much time does the course spend in activities?

Approximately 40 percent of this course is spent in activities. Throughout the course, an interactive and evolving case study immerses you in the SDLC of a project from inception to product release. Working in small groups, you employ both PC-based and paper tools to gain first-hand knowledge and experience in all SCM processes and tasks. Activities include:

  • Matching software project needs to SCM process capability
  • Gathering the attributes and characteristics to create a Configuration Item list
  • Designing a change control process that accommodates change requests and problem reports
  • Creating a design baseline
  • Identifying key reports needed for effective SCM communications

FREE After-Course Instructor Coaching

Your training with SQA Solution continues after your course is over!

After-Course Instructor Coaching is one of many practical benefits that SQA Solution course attendees receive. Once you’ve completed a course, your instructor will be available to help you apply your newly gained knowledge, overcome any start-up hurdles, and offer guidance on specific applications.
#SQASolutionShare on FacebookShare on Google+Share on LinkedInTweet about this on TwitterEmail this to someone