SPM Unit 4
SPM Unit 4
Change Management
Change management must be automated & enforced to manage multiple iterations & to
enable change freedom.
Change is the fundamental primitive of iterative Development.
I. Software Change Orders
The atomic unit of software work that is authorized to create,modify or obsolesce
components within a configuration baseline is called a software change orders ( SCO )
The basic fields of the SCO are Title, description, metrics, resolution, assessment &
disposition
Change management
II.Configuration Baseline
A configuration baseline is a named collection of software components &Supporting
documentation that is subjected to change management & is upgraded, maintained,
tested, statuses & obsolesced a unit
There are generally two classes of baselines
External Product Release
Internal testing Release
Three levels of baseline releases are required for most Systems
1. Major release (N)
2. Minor Release (M)
3. Interim (temporary) Release (X)
Major release represents a new generation of the product or project
A minor release represents the same basic product but with enhanced features,
performance or quality.
Major & Minor releases are intended to be external product releases that are
persistent & supported for a period of time.
An interim release corresponds to a developmental configuration that is intended to
be transient.
Once software is placed in a controlled baseline all changes are tracked such that a
distinction must be made for the cause of the change. Change categories are
Type 0: Critical Failures (must be fixed before release)
Type 1: A bug or defect either does not impair (Harm) the usefulness of the system or
can be worked around
Type 2: A change that is an enhancement rather than a response to a defect
Type 3: A change that is necessitated by the update to the environment
Type 4: Changes that are not accommodated by the othercategories.
Change Management
III Configuration Control Board (CCB)
A CCB is a team of people that functions as the decision
Authority on the content of configuration baselines
A CCB includes:
1. Software managers
2. Software Architecture managers
3. Software Development managers
4. Software Assessment managers
5. Other Stakeholderswho are integral to the maintenance of the controlled
software delivery system?
Infrastructure
The organization infrastructure provides the organization’s capitalassets including two
key artifacts - Policy & Environment
I Organization Policy:
A Policy captures the standards for project software developmentprocesses
The organization policy is usually packaged as a handbook that defines the life cycles
& the process primitives such as
Major milestones
Intermediate Artifacts
Engineering repositories
Metrics
Roles & Responsibilities
Infrastructure
II Organization Environment
The Environment that captures an inventory of tools which are building blocks from
which project environments can be configuredefficiently & economically
Stakeholder Environment
Many large scale projects include people in external organizationsthat represent other
stakeholders participating in the development processthey might include
Procurement agency contract monitors
End-user engineering support personnel
Third party maintenance contractors
Independent verification & validation contractors
Representatives of regulatory agencies & others.
These stakeholder representatives also need to access to development resources so that
they can contribute value to overall effort. These stakeholders will be access through
on-line
An on-line environment accessible by the external stakeholdersallow them to
participate in the process a follows
Accept & use executable increments for the hands-on evaluation.
Use the same on-line tools, data & reports that the development organization uses to
manage & monitor the project
Avoid excessive travel, paper interchange delays, format translations, paper *
shipping costs & other overhead cost
Unit – Important Questions