How to establish SEPG and SPI functions?

How to establish SEPG and
SPI functions?

By
Panitta Kaewkallaya
SPI Consultant and IT Specialist
panittak@gmail.com

How to establish SEPG and SPI functions? 1

Topics
Overview of SPI and Rationale Behind Process Groups
On Going Activities of Established Process Groups
Costs and Benefits


Software Process Improvement
Quality is a key factor today
What is it?
in international business competition.
Who owns it? And quality, most people would now
agree, is not something added to the
product during testing at the end of the
development process;
it is something everyone owns and is
responsible for throughout that process.

Source: From Ford’s "Quality is Job 1" slogan to the DoD Total Quality Management program [TQM88]


The Process Improvement Cycle
3. Analyze
the variance
2. Assess the
between
current practice.
Expectation
and practice.

4. Propose changes
1. Set expectations. that will reduce the variance and thereby
improve the process.

5. Plan the integration of
8. Start over. the improvements into the existing process
and update the process definition.

7. Perform
the process 6. Implement the
as it is now improvements.
defined.


How do organizations move from their current state to one
where there is continuous improvement?
Establish
Organization Commitment

Continuous
Improvement
Create
An Entity Carefully Plan
(the focal point)

In the software industry, the organizational focal point is
a software engineering process group, and the model for the step-by-step change is
the process improvement cycle. In fact, the phrase
"software process improvement" is often used as a synonym for
"software quality."


The SEPG
Composed of line practitioners who have varied skills
The group is at the center of the collaborative effort of
everyone in the organization who is involved with
software engineering process improvement.
Group size is usually equal to 1-3% of the development
staff.
The process group is not part of product development
but is staffed by practitioners.
One way to view the process group is as a permanent
task force.
The challenge of the process group and its managers
and sponsors is to maintain the enthusiasm and vitality
of a task force on a continuing basis.


SEPG and Work Groups Composition
Steering
Committee

SW Dev. Team SW Dev. Team

SEPG

SPI Project SPI Project
Permanent Member Work Group 1 Work Group 2

Involve in SEPG activities
for short periods How to establish SEPG and SPI functions? 7

Placing the SEPG in the Organization
President
Placement in a
Typical Hierarchy
Organization
Managing Director

SEPG

Dept. Mgr. Dept. Mgr. Dept. Mgr. Dept. Mgr. Dept. Mgr.


Placing the SEPG in the Organization

Placement in a
Typical Matrix
Organization
Adapted from
[Janger79].


SEPG and Work Group activities
Evaluate Transition
Proposed by
Steering
SEPG Outcome to Organization
Committee

Suggested by
Projects members
Select
Proposals arise Improvement Implement
from Area
assessment

Analysis of
Industry Trends Work
Group
Emerging
technologies
or project needs


Ongoing Activities of SEPG
1. Obtains and maintains the support of all levels of management.
2. Facilitates software process assessments.
3. Works with line managers whose projects are affected by changes in
software engineering practice, providing a broad perspective of the
improvement effort and helping them set expectations.
4. Maintains collaborative working relationships with software engineers,
especially to obtain, plan for, and install new practices and technologies.
5. Arranges for any training or continuing education related to process
improvements.
6. Tracks, monitors, and reports on the status of particular improvement
efforts.
7. Facilitates the creation and maintenance of process definitions, in
collaboration with managers and engineering staff.
8. Maintains a process database.
9. Provide process consultation to development projects and management.

SEPG Membership
SEPG members should collectively have experience from
throughout the software life cycle.
They should have experience with multiple frames of
reference, and their backgrounds should complement
each other. Membership is usually
full-time,
for a fixed period of time, and
recommended as a condition of promotion to a senior
position.


Selecting the SEPG Leader
The SEPG leader must be an acknowledged technical leader,
with these characteristics:
Extensive experience in or knowledge of the software
process.
Experience advocating improved software development
processes, methods, and tools—that is, improved quality
and productivity.
Experience in management or project leadership.
Knowledge of the software development environment.
Candidates for process group leadership may be found
among senior technical staff who have lobbied for
improvements within their software projects.


Selecting the SEPG Members
Each SEPG member should meet this fundamental set of
qualifications:
Be a regular employee of the organization, with experience
within the software projects that will be served by the SEPG
Members.
Have application domain expertise.
Have a basic understanding of the software development
process.
Have knowledge of local software development methods,
tools, and practices.


Selecting the SEPG Members
The composite background of the SEPG Members must be
considered. The group should have experience that supports
objectivity about the organization’s technical environment,
culture, management style, and reward systems. This
experience includes:
Work on other software development projects.
Work in other companies or government organizations.
Experience in a variety of software development or support/staff
positions, for example, in testing, design, and product assurance (rather
than in just one of these).
Experience with other target and host computers, as well as other
software development tools and environments.
Use of other software development processes.
Work in other application domains.
Attendance at professional society conferences and workshops.


Length of Membership
Tenure of two to three years is recommended for process
group members.
Membership should be staggered, allowing a month or
two of overlap as members are replaced.
Ideally, SEPG members should come from and return to
line organizations; i.e., organizations building or revising
software.


Advantages of Membership
Exercise communication skills in preparing and refining
plans and briefings.
Group members develop leadership ability as they work
in cooperation with peers and management.

Because of this, SEPG members may become
qualified for promotion to management
in a short time.


Organizing for Process Improvement:
“Collaborators”
The Steering Committee Working Groups


The Steering Committee Responsibilities
Line and supervisory management.
Meets periodically (perhaps monthly).
Translates related corporate policy and sets
priorities.
Reviews the results of assessments
Charters technical areas working groups to
prepare plans, approve those plans in priority
order
Monitors the progress of the working groups
Help obtain resources for the process group


The Steering Committee Ongoing Works
Policy oversight.
Resource and process management.
Integration and consensus building
among groups having different
perspectives.
Serving as liaison to higher level steering
groups or corporate planning
organizations.


Working Groups Responsibilities
These groups are chartered to work a wide range of issues
from selecting new design methods to choosing the measures
of software productivity and quality to be included in the
process database.
Groups usually do this by taking advantage of the experience
and expertise of the population to be served.
The members of working groups:
Engineers from a number of project types and
application domains (cross-fertilization)
Staffed by senior people
Ready consulting expertise


Costs and Benefits
Costs
Primarily labor costs.
In organizations of a hundred or more software
professionals, the recommended budget for a process
group [Humphrey89] is normally 1% to 3% of the overall
software development budget of the organization it
supports.
* These are consumed in staff for the software engineering process group, and in
the time spent in planning and implementing improvement actions. Often these
are costs that would be expended on similar activities in any case, but in a less
organized and therefore less visible way.


Costs and Benefits
Benefits: The primary benefit of an improved—that are,
more disciplined—software process is improved visibility of
the process.
This visibility makes the process more manageable during
software development and maintenance, thus reducing risk.
Schedules become more predictable, as do costs.
Software is of higher quality at delivery and is easier to
maintain.
Another benefit is the improved prospect of winning and
keeping contracts when the government includes software
process maturity in its source selection and contract
management criteria [Thomas88].


Additional Suggestions
Communication channel Extra process improvement
among SEPG and to all staff activities to encourage
e.g. organization innovation and
Process Assets Library deployment e.g.
Announcement Process improvement
Process newsletter campaign e.g. Innovation
contest
Web board
Rewarding/recognition,
Process Gurus or
communities


References
Software Engineering Process Group Guide, Priscilla Fowler and Stan Rifkin,
September 1990
An Experience of SEPG Organization
http://www.iscn.at/select_newspaper/installation/sodalia.html
http://www.iscn.com/projects/pico/news/billi.htm
What is an SEPG and how do we use it for CMMI?
http://askthecmmiappraiser.blogspot.com/2007/02/dear-appraiser-i-want-
some-information.html


How to establish SEPG and SPI functions?

More Related Content

What's hot (20)

Viewers also liked (10)

Similar to How to establish SEPG and SPI functions? (20)

Recently uploaded (20)

How to establish SEPG and SPI functions?