Software Change, Configuration and Release Management – In Class Training in SFO
You Will Learn How To:
Workshop Activities Include:
Talk To Trainers
1. Configuration and Release Management
Analyzing business factors driving CM
Demystifying core CM processes
2. Identifying Configuration Items (CIs)
Deriving candidate items for the project
Categorizing and naming items
3. Controlling Change
Determining roles and responsibilities
Creating a change control process
Distinguishing between defects and enhancements
4. Communicating Configuration Status
Planning the reporting requirements
Matching reporting needs to development life cycle
5. Auditing in Preparation for a Release
Designing Configuration Audits
Assessing release readiness
6. Building and Releasing the Product
Ensuring consistency through the build process
Specifying the product release process
Who Should Attend–
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?
|Foundation for configuration and release management||3.0|
|Identifying Configuration Items (CIs)||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