ISO/IEC TR 15504-6:1998

Information technology — Software process assessment — Part 6: Guide to competency of assessors

Technologies de l'information — Évaluation des procédés du logiciel — Partie 6: Guide de la compétence des évaluateurs

General Information

• Status: Withdrawn
• Publication Date: 12-Aug-1998
• Withdrawal Date: 12-Aug-1998
• ICS: 35.080 - Software
• Technical Committee: ISO/IEC JTC 1/SC 7 - Software and systems engineering
• Drafting Committee: ISO/IEC JTC 1/SC 7/WG 10 - Process assessment
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 06-Jan-2004

Relations

• Revised: ISO/IEC 15504-3:2004 - Information technology — Process assessment — Part 3: Guidance on performing an assessment
• Effective Date: 15-Apr-2008

Standards Content (Sample)

TECHNICAL ISO/IEC
REPORT TR 15504-6
First edition
1998-08-15
Information technology — Software process
assessment —
Part 6:
Guide to competency of assessors
Technologies de l’information — Évaluation des procédés du logiciel —
Partie 6: Guide pour la compétence des évaluations
Reference number
B C
ISO/IEC TR 15504-6:1998(E)

---------------------- Page: 1 ----------------------
ISO/IEC TR 15504-6:1998(E)
Contents
1 Scope .1
2 Normative reference .1
3 Terms and definitions.1
4 An overview of the assessor and competence .1
4.1 The role of the assessor.1
4.2 Philosophy.3
4.3 The process of gaining and maintaining competence.3
4.3.1 Becoming a provisional assessor.3
4.3.2 Becoming a competent assessor.4
4.3.3 Maintenance of competence.4
5 Assessor competence.4
5.1 The software process .4
5.2 Aspects of assessment .4
5.3 Personal attributes.5
5.3.1 General.5
5.3.2 Effective written and verbal communication.5
5.3.3 Diplomacy .5
5.3.4 Discretion.5
5.3.5 Persistence and resistance handling ability .5
5.3.6 Judgment and leadership.5
5.3.7 Integrity .5
5.3.8 Rapport .6
© ISO/IEC 1998
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or
utilized in any form or by any means, electronic or mechanical, including photocopying and micro-
film, without permission in writing from the publisher.
ISO/IEC Copyright Office • Case postale 56 • CH-1211 Genève 20 • Switzerland
Printed in Switzerland
ii

---------------------- Page: 2 ----------------------
© ISO/IEC
ISO/IEC TR 15504-6:1998(E)
6 Validation of education, training and experience. 6
6.1 Overview . 6
6.2 Education. 6
6.3 Training. 6
6.3.1 General. 6
6.3.2 Specific training . 7
6.4 Experience. 8
6.4.1 General. 8
6.4.2 Customer-supplier process category . 8
6.4.3 Engineering process category . 9
6.4.4 Support process category . 9
6.4.5 Management process category . 9
6.4.6 Organization process category . 9
6.5 Experience of assessments using ISO/IEC TR 15504 . 9
6.6 Maintenance of competence. 9
6.7 Maintenance of records. 10
Annex A (informative) Training record. 11
Annex B (informative) Record of experience. 12
Annex C (informative) Record of participation. 13
Annex D (informative) Assessment log. 14
Annex E (informative) Professional activities log. 15
Annex F (informative) Mechanisms for demonstrating competence. 16
Annex G (informative) Mechanisms for validating education, training and experience . 18
iii

---------------------- Page: 3 ----------------------
© ISO/IEC
ISO/IEC TR 15504-6:1998(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission)
form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC
participate in the development of International Standards through technical committees established by the
respective organization to deal with particular fields of technical activity. ISO and IEC technical committees
collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in
liaison with ISO and IEC, also take part in the work.
In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
The main task of technical committees is to prepare International Standards, but in exceptional circumstances a
technical committee may propose the publication of a Technical Report of one of the following types:
— type 1, when the required support cannot be obtained for the publication of an International Standard, despite
repeated efforts;
— type 2, when the subject is still under technical development or where for any other reason there is the future
but not immediate possibility of an agreement on an International Standard;
— type 3, when a technical committee has collected data of a different kind from that which is normally published
as an International Standard (“state of the art”, for example).
Technical Reports of types 1 and 2 are subject to review within three years of publication, to decide whether they
can be transformed into International Standards. Technical Reports of type 3 do not necessarily have to be
reviewed until the data they provide are considered to be no longer valid or useful.
ISO/IEC TR 15504-6, which is a Technical Report of type 2, was prepared by Joint Technical Committee ISO/IEC
JTC 1, Information technology, Subcommittee SC 7, Software engineering.
ISO/IEC TR 15504 consists of the following parts, under the general title Information technology — Software
process assessment :
 Part 1: Concepts and introductory guide
 Part 2: A reference model for processes and process capability
 Part 3: Performing an assessment

Part 4: Guide to performing assessments
 Part 5: An assessment model and indicator guidance
 Part 6: Guide to competency of assessors
 Part 7: Guide for use in process improvement
 Part 8: Guide for use in determining supplier process capability
 Part 9: Vocabulary
Annexes A to G of this part of ISO/IEC TR 15504 are for information only.
iv

---------------------- Page: 4 ----------------------
© ISO/IEC
ISO/IEC TR 15504-6:1998(E)
Introduction
Conducting a software process assessment in accordance with the provisions of ISO/IEC TR 15504 assumes that
the assessment team includes at least one competent assessor. The competent assessor has the responsibility for
ensuring that the requirements are met during the assessment.
As described in ISO/IEC TR 15504-3 and ISO/IEC TR 15504-4, rating the assessed processes ultimately depends
on the skilled judgment of the assessors. The various elements of ISO/IEC TR 15504 provide the framework within
which assessors exercise judgment, working together to remove, or at least reduce to a minimum, any subjective
elements. Nevertheless, the achievement of an acceptable level of consistency, repeatability and reliability of
results relies on competent assessors with appropriate skills, experience, and knowledge of the software process,
of the model for processes described in ISO/IEC TR 15504-2, and of performing assessments as described in
ISO/IEC TR 15504-3 and ISO/IEC TR 15504-4.
The competent assessor in a team has the pivotal role of ensuring that other team members collectively have the
right blend of specialized knowledge and assessment skills. The competent assessor provides the necessary
guidance to the team, and helps to moderate the judgments and ratings made by the other members of the team to
ensure consistency of interpretation.
This part of ISO/IEC TR 15504 is concerned with assessor competencies and appropriate education, training and
experience including mechanisms that may be used to demonstrate competence and to validate education, training
and experience.
This part of ISO/IEC TR 15504 is primarily directed to assessors, to those responsible for the selection and
development of assessors, and to sponsors of assessments seeking assurance that an assessor is competent to
carry out the task.
v

---------------------- Page: 5 ----------------------
TECHNICAL REPORT  © ISO/IEC ISO/IEC TR 15504-6:1998(E)
Information technology — Software process assessment —
Part 6:
Guide to competency of assessors
1 Scope
This part of ISO/IEC TR 15504 provides guidance for the preparation of assessors to perform software process
assessments. It describes mechanisms that may be used to demonstrate assessor competence and to validate an
assessor’s education, training and experience.
The guidance in this part of ISO/IEC TR 15504 is applicable to an organizational unit or a sponsor of an assessment
wishing to select or specify the type of assessors to perform either self-assessments or independent assessments.
The guidance is also applicable to the identification and demonstration of the competencies necessary for the
performance of assessments, and to the process of obtaining those competencies.
Guidance on the competence of those who perform process capability determination or process improvement
activities is outside the scope of this part of ISO/IEC TR 15504.
2 Normative reference
The following normative documents contain provisions which, through reference in this text, constitute provisions of
this part of ISO/IEC TR 15504. For dated references, subsequent amendments to, or revisions of, any of these
publications do not apply. However, parties to agreements based on this part of ISO/IEC TR 15504 are encouraged
to investigate the possibility of applying the most recent editions of the normative documents indicated below. For
undated references, the latest edition of the normative document referred to applies. Members of ISO and IEC
maintain registers of currently valid International Standards.
ISO/IEC TR 15504-9:1998, Information technology — Software process assessment — Part 9: Vocabulary.
3 Terms and definitions
For the purposes of this part of ISO/IEC TR 15504, the terms and definitions given in ISO/IEC TR 15504-9 apply.
4 An overview of the assessor and competence
4.1 The role of the assessor
The role of the assessor, as described in ISO/IEC TR 15504-4, is to assess the software process of an
Organizational Unit in a constructive and an objective manner. The assessment should be focused on the process
and not the people implementing the process. The role varies depending on the assessment approach as shown in
table 1.
1

---------------------- Page: 6 ----------------------
© ISO/IEC
ISO/IEC TR 15504-6:1998(E)
Table 1 — The role of the assessor in different assessment approaches
Self-assessment approach Independent assessment approach
Is task and people oriented. Is task oriented.
Guides the assessment. Controls the assessment.
Agrees a rating. Delivers a rating.
Promotes discussion. Regulates discussion.
Works with projects. Works separately from projects.
Uses Organizational Unit's business goals. May be indifferent to Organizational Unit's
business goals.
Influences through results obtained, Influences through position and expertise.
relationships established and expertise.
Seeks commitment. Determines process adequacies.
Is like being a change agent. Is like being an auditor.
Figure 1 — Entity relationships
2

---------------------- Page: 7 ----------------------
© ISO/IEC
ISO/IEC TR 15504-6:1998(E)
4.2 Philosophy
Figure 1 shows the key entities and relationships which may be articulated as follows:
a) assessors demonstrate their competence to carry out assessments;
b) competence results from:
1) the knowledge of the software process,
2) skills in the principal technologies of ISO/IEC TR 15504 including: the reference model; assessment
models, methods and tools; and rating processes,
3) personal attributes which contribute to effective performance;
c) the knowledge, skills and personal attributes are gained by a combination of education, training and
experience;
d) an alternative to the demonstration of competence is to validate an intending assessor's education, training and
experience.
4.3 The process of gaining and maintaining competence
4.3.1 Becoming a provisional assessor
A provisional assessor is a person who has reached the required levels of education, training and experience but
who has not necessarily participated in assessments conducted according to the provisions of ISO/IEC TR 15504.
A provisional assessor should be trained and experienced in the software process as well as in software process
assessment or software quality assessment. A provisional assessor should have received training that satisfies the
guidance of ISO/IEC TR 15504. A provisional assessor should also have evidence of an acceptable level of
education. (Education is a combination of general education and software education.)
Acceptable levels of education may comprise:
 courses offered by a college or university;
 professional courses organized by recognized local or international bodies;
 vendor sponsored courses;
 employer sponsored courses.
Acceptable levels of training may comprise:
 training provided by recognized local or international bodies;
 training provided by vendors and trainers based on the guidance in this part of ISO/IEC TR 15504.
Acceptable levels of experience may comprise:
 direct "hands-on" experience in specialist areas such as software engineering, software
development/maintenance, software quality, or quality assurance;
 management experience overseeing software specialist areas such as software engineering, software
development/maintenance, software quality or quality assurance.
3

---------------------- Page: 8 ----------------------
© ISO/IEC
ISO/IEC TR 15504-6:1998(E)
4.3.2 Becoming a competent assessor
To become a competent assessor, one should have participated in assessments conducted according to the
provisions of ISO/IEC TR 15504. Competent assessors should maintain a record of ongoing professional activities
to demonstrate continuing competencies of skills, knowledge and training. Assessors’ professional activities should
be recorded (see Annex D and Annex E) for validation.
4.3.3 Maintenance of competence
To maintain their competence, assessors should update their knowledge and skills by engaging in a number of
professional activities as well as carrying out further assessments conducted according to the provisions of
ISO/IEC TR 15504.
5 Assessor competence
5.1 The software process
An assessor should be familiar with software development and maintenance including various life cycle models and
be able to demonstrate competence in at least one of the process categories of the process model described in
ISO/IEC TR 15504-2.
An assessor should also be able to demonstrate familiarity with the software process, and should be experienced
with the use of one or more development models such as Waterfall or Rapid Prototyping.
In addition, an assessor should show an understanding of the activities required to support the software process,
methods and tools, including when and how they should be applied according to the development model chosen
within the application domain in which the assessor is experienced.
An assessor should be familiar with a range of relevant software engineering standards.
5.2 Aspects of assessment
Assessors should demonstrate competence in aspects of the assessment pertaining to ISO/IEC TR 15504,
particularly the core aspects included in parts 2 to 5 as shown below.
a) Overview of the framework for process assessment
(ISO/IEC TR 15504-1: Information technology - Software process assessment - Part 1: Concepts and introductory guide)
b) The process assessment architecture
(ISO/IEC TR 15504-2: Information technology - Software process assessment - Part 2: A reference model for processes
and process capability)
c) Performing process assessment
(ISO/IEC TR 15504-3: Information technology - Software process assessment - Part 3: Performing an assessment, and
ISO/IEC TR 15504-4: Information technology - Software process assessment - Part 4: Guide to Performing assessments)
d) Compatible assessment models
(ISO/IEC TR 15504-5: Information technology - Software process assessment - Part 5: An assessment model and indicator
guidance; or other compatible model)
e) Relevant software standards
4

---------------------- Page: 9 ----------------------
© ISO/IEC
ISO/IEC TR 15504-6:1998(E)
5.3 Personal attributes
5.3.1 General
Effective written and verbal communication
Diplomacy
Discretion
Persistence and resistance handling ability
Personal attributes
Judgement and leadership
Integrity
Rapport
Figure 2 — Personal attributes
Assessors should possess the personal attributes shown in figure 2 and described below. Their functional and
hierarchical position relative to the Organizational Unit should allow them to take advantage of these attributes.
5.3.2 Effective written and verbal communication
Assessors who perform assessments will interact with members of the organizational unit being assessed. They
may be feeding back the results of the assessment in the form of written reports and/or presentations. Assessors
should be able to communicate the findings of the assessments in a clear, non-judgmental style. Assessment
findings should be documented in clear and unambiguous language.
5.3.3 Diplomacy
Assessors should act with professionalism and decorum at all times. Independent assessors are guests of the
organizational unit being assessed and their conduct should be above reproach at all times.
5.3.4 Discretion
Assessors should develop and maintain the confidence of the assessment participants. In particular, assessors
should preserve the confidentiality of the results of the assessment and of information received during an
assessment in accordance with the terms of any confidentiality agreement included in the assessment constraints
(see ISO/IEC TR 15504-3 and ISO/IEC TR 15504-4).
5.3.5 Persistence and resistance handling ability
Assessors should be persistent in carrying out the duties that are expected of them. They should be able to resolve
any conflicts and handle any resistance that they may experience from assessment participants.
5.3.6 Judgment and leadership
It is critical that the Organizational Unit being assessed has confidence in, and respect for individual assessment
team members. If they are not respected within the Organizational Unit, then the assessment findings may not be
accepted by the organizational unit.
5.3.7 Integrity
The assessment team leader, team coordinator and team members should have no conflict of interest in performing
the assessment. For example, the risks should be considered including as team members’ managers who evaluate
the performance of individuals involved in a project being assessed.
5

---------------------- Page: 10 ----------------------
© ISO/IEC
ISO/IEC TR 15504-6:1998(E)
5.3.8 Rapport
Individuals who might stifle the open and honest flow of information because of their organizational position or
personality should not participate in the assessment. Assessors should create an open and honest spirit of
communication between people so that project personnel will freely discuss issues.
6 Validation of education, training and experience
6.1 Overview
Validation of an assessor’s education, training and experience is an alternative to the demonstration of competence.
The education, training and experience may be validated by a review of these elements. The right balance is of
prime importance. In general terms, the balance includes general education and software education together with a
combination of training and experience in both software development activities and assessments, including those
that are conducted according to the provisions of ISO/IEC TR 15504.
The following factors should be considered when reviewing the education, training and experience of an assessor.
Duration: The amount of time the assessor has spent in a particular process category. (See ISO/IEC TR 15504-2
for process categories).
Range: The assessor’s breadth of exposure to the process categories.
Depth: The level of specialization.
Responsibility: The extent to which an assessor has held responsibility in terms of both range and depth.
Currency: How recent is the assessor’s education, training and experience, and the extent to which the assessor’s
knowledge and skill have been updated.
6.2 Education
Assessors should maintain documented evidence of their education in terms of certificates and course outlines for
validation. The following levels of educational achievement may be considered as appropriate in the categories of
general education and software education.
General education: A degree or equivalent in any discipline from an educational establishment.
Software education: A degree or equivalent in Computer Science, Software Engineering or a similar discipline.
6.3 Training
6.3.1 General
An assessor’s training should be recorded (see Annex A) for validation.
Acceptable training would cover at least some aspects of software development.
In order to be familiar with software development and maintenance processes, the assessor should have been
trained, or have documented experience, in all the processes in the Engineering (ENG) process category.
Project management or technical leadership training provides a background in the Customer Supplier (CUS) and
the Organizational (ORG) process categories. Assessors need not have been trained in each process in the two
process categories, but should be familiar and conversant with the topics. Assessors should have extensive
training in at least one of the processes in these two process categories.
6

---------------------- Page: 11 ----------------------
© ISO/IEC
ISO/IEC TR 15504-6:1998(E)
6.3.2 Specific training
An intending assessor should receive specific training that satisfies the guidance in this part of ISO/IEC TR 15504
in order to become a provisional assessor. A training course to cover the requirements and assessment elements of
ISO/IEC TR 15504 should comprise at least the following topic areas:
6.3.2.1 Overview of ISO/IEC TR 15504
 Background
 Architecture and principles
 The component parts of ISO/IEC TR 15504
 Vocabulary and definitions
 Comparison of ISO/IEC TR 15504 with other standards and/or methodologies
Assessment vs. auditing

 How to use the parts of ISO/IEC TR 15504
6.3.2.2 The process assessment architecture
(Based on ISO/IEC TR 15504-2 A reference model for processes and process capability)
 The Process Dimension:
 Life cycle process groupings
 Process categories
 Basic and component processes
 Process purposes
 The Capability Dimension:
 Capability levels
 Process attributes
 Rating processes and the process capability level model
 Requirements for compatible models
 How to use ISO/IEC TR 15504-2.
6.3.2.3 Process Assessment
(Based on ISO/IEC TR 15504-3 Performing an assessment and ISO/IEC TR 15504-4 Guide to performing
assessments)
 Defining the assessment input
 Responsibilities
 The assessment process:
 Planning
7

---------------------- Page: 12 ----------------------
© ISO/IEC
ISO/IEC TR 15504-6:1998(E)
 Data validation
 Process rating
 Reporting
Recording the assessment output

 Selection and use of a documented assessment process:
 Using indicators
 Selection and use of assessment instruments and tools
 How to use ISO/IEC TR 15504-3 and ISO/IEC TR 15504-4
6.3.2.4 Compatible models for assessment
(Based on ISO/IEC TR 15504-2 A reference model for processes and process capability; ISO/IEC TR 15504-4
Guide to performing assessments, and ISO/IEC TR 15504-5 An assessment model and indicator guidance, or any
other compatible model.)
 The purpose of an assessment model
 Compatibility with the reference model:
 Purpose and scope of the assessment model
 Model elements and indicators
 Mapping the assessment model to the reference model
 Translating assessment results to process profiles
 Selection and use of a compatible model in assessments
6.4 Experience
6.4.1 General
Assessors’ experience should be recorded (see Annex B) for validation.
Some of the factors which should be taken into account when assessing the relevance of experience in each of the
process categories are addressed in 6.4.2 to 6.4.6 below. In lieu of personal experience, the teaching of the
particular subject at a suitable level may suffice.
There is an interaction between experience and training: training alone is insufficient. There is also a beneficial
interaction between experiences in different roles. For example, team leaders or managers of projects may have
had contact with software configuration management and software quality assurance functions. The experience
gained may overlap and cover a number of process categories in any particular assignment.
In consequence, recent graduates, or individuals who have spent their entire working lives in a single process
category, are unlikely to have accumulated sufficiently broad experience.
6.4.2 Customer-supplier process category
The key element of these practices is joint customer and supplier interaction. Participation in activities within an
organizational unit with a recognized quality management system would be helpful. The provision of customer
references would aid verification.
8

---------------------- Page: 13 ----------------------
© ISO/IEC
ISO/IEC TR 15504-6:1998(E)
6.4.3 Engineering process category
Assessors should demonstrate evidence of work experience that shows the use of some of the development
practices within this process category. Experience solely in the development of user documentation is insufficient.
6.4.4 Support process category
A key feature of these practices is the development of plans and the measurement of performance against these
plans. Relevant experience includes developing project or user documentation.
Assessors should be able to
...