BS ISO IEC 29155-2-2013 Systems and software engineering Information technology project performance benchmarking framework Requirements for benchmarking《信息和软件工程 信息技术项目绩效杠杆.pdf

1、BSI Standards Publication BS ISO/IEC 29155-2:2013 Systems and software engineering Information technology project performance benchmarking framework Part 2: Requirements for benchmarkingBS ISO/IEC 29155-2:2013 BRITISH STANDARD National foreword This British Standard is the UK implementation of ISO/I

2、EC 29155-2:2013. The UK participation in its preparation was entrusted to Technical Committee IST/15, Software and systems engineering. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary pr

3、ovisions of a contract. Users are responsible for its correct application. The British Standards Institution 2013. Published by BSI Standards Limited 2013 ISBN 978 0 580 76317 5 ICS 35.080 Compliance with a British Standard cannot confer immunity from legal obligations. This British Standard was pub

4、lished under the authority of the Standards Policy and Strategy Committee on 30 November 2013. Amendments issued since publication Date Text affectedBS ISO/IEC 29155-2:2013 Systems and software engineering Information technology project performance benchmarking framework Part 2: Requirements for ben

5、chmarking Ingnierie des systmes et du logiciel Cadre de conduite de tests de performance de projet de technologies de linformation Partie 2: Exigences pour le marquage de rfrence ISO/IEC 2013 INTERNATIONAL STANDARD ISO/IEC 29155-2 First edition 2013-11-01 Reference number ISO/IEC 29155-2:2013(E)BS I

6、SO/IEC 29155-2:2013ISO/IEC 29155-2:2013(E)ii ISO/IEC 2013 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2013 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, includin

7、g photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22

8、 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in SwitzerlandBS ISO/IEC 29155-2:2013ISO/IEC 29155-2:2013(E) ISO/IEC 2013 All rights reserved iii Contents Page Foreword iv Introduction v 1 Scope . 1 2 Normative references 1 3 T erms and definitions . 1 4 Abbreviated terms 2 5 Benchmarki

9、ng process model 2 5.1 Outline of the benchmarking process model 2 5.2 Requirements and tasks for business layer 4 5.3 Requirements and tasks for program layer 5 5.4 Requirements and tasks for project and operational layer 5 Annex A (informative) Framework model of IT project performance benchmarkin

10、g 21 Bibliography .24BS ISO/IEC 29155-2:2013ISO/IEC 29155-2:2013(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 part

11、icipate 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, government

12、al 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. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.

13、 The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodi

14、es casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC 29155-2 was prepared by Joint Technical Committee ISO/IEC JTC 1, I

15、nformation technology, Subcommittee SC 7, Software and systems engineering. ISO/IEC 29155 consists of the following parts, under the general title Systems and software engineering Information technology project performance benchmarking framework: Part 1: Concepts and definitions Part 2: Requirements

16、 for benchmarking Part 3: Guidance for reporting Part 4: Guidance for data collection and maintenance Further parts might follow.iv ISO/IEC 2013 All rights reservedBS ISO/IEC 29155-2:2013ISO/IEC 29155-2:2013(E) Introduction This part of ISO/IEC 29155 identifies the required activities and tasks that

17、 are necessary to successfully identify, define, select, apply, and improve benchmarking for information technology (IT) project performance. This part of ISO/IEC 29155 is intended to provide guidance for organizations which are preparing to introduce and implement benchmarking techniques to evaluat

18、e performance of IT projects. This part of ISO/IEC 29155 assists organizations to establish a well-defined process to perform benchmarking. The process includes activities and tasks not only for data selection and comparison in IT project performance benchmarking but also for data collection, benchm

19、arking repository management, and providing benchmarking instruments. This part of ISO/IEC 29155 is developed as the second part of multiple parts which will complete the IT project performance benchmarking framework as is shown in Figure 1. This part of ISO/IEC 29155 provides the requirements for a

20、 benchmarking process. Part 4: Guidance for data collection and maintenance Data characteristics INPUT Part 3: Guidance for reporting Data analysis OUTPUT Part 2: Requirements for benchmarking PROCESS Part 1: Concepts and definitions RESOURCES Benchmarking domains CONTROLS Figure 1 IT project perfor

21、mance benchmarking standards overview ISO/IEC 2013 All rights reserved vBS ISO/IEC 29155-2:2013BS ISO/IEC 29155-2:2013Systems and software engineering Information technology project performance benchmarking framework Part 2: Requirements for benchmarking 1 Scope This part of ISO/IEC 29155 provides g

22、eneral requirements for processes of “the information technology (IT) project performance benchmarking framework” by prescribing: the requirements for the processes for individual activities within the benchmarking framework (e.g. conduct benchmarking, maintain repository, submit data), the tasks ne

23、cessary to successfully execute activities and equip them with components, both of which are defined in ISO/IEC 29155-1. This part of ISO/IEC 29155 is intended for use by any stakeholder(s) of IT project performance benchmarking (e.g. benchmarking user, benchmark provider, benchmarking service provi

24、der, and IT project team). NOTE The following are examples of how this part of ISO/IEC 29155 can be used: by a systems and software supplier to implement a benchmarking process to estimate and/or evaluate performance of an IT project, by a systems and software acquirer (or a third-party agent) for e

25、valuating the performance of the suppliers IT project, by a benchmark provider to implement processes to collect and analyze IT project data and provide benchmarks, by a benchmarking service provider to implement various services (e.g. providing instruments for benchmarking, or conducting an instanc

26、e of benchmarking for a benchmarking user). This part of ISO/IEC 29155 does not prescribe how to utilize benchmarking results, nor does it prescribe the name, format, or explicit content of the documentation that results from the benchmarking processes. 2 Normative references The following documents

27、, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 29155-1, Systems and s

28、oftware engineering Information technology project performance benchmarking framework Part 1: Concepts and definitions 3 T erms a nd definiti ons For the purposes of this document, the terms and definitions given in ISO/IEC 29155-1 and the following apply. 3.1 data submitter person or organization t

29、hat provides IT project data to be included into a benchmarking repository INTERNATIONAL ST ANDARD ISO/IEC 29155-2:2013(E) ISO/IEC 2013 All rights reserved 1BS ISO/IEC 29155-2:2013ISO/IEC 29155-2:2013(E) 3.2 repository owner person or organization that owns and maintains a benchmarking repository 3.

30、3 task smallest unit of work subject to management accountability; a well-defined work assignment for one or more project members Note 1 to entry: Related tasks are usually grouped to form activities. SOURCE: IEEE 829-2008 IEEE Standard for Software and System Test Documentation, 3.1.38 4 Abbreviate

31、d terms CBa “Conduct Benchmarking” activity IBa “Issue Benchmarks” activity IT Information Technology MPa “Measure IT Project” activity MRa “Maintain Repository” activity MBLa “Manage benchmarking Business Level” activity MPLa “Manage benchmarking Program Level” activity PIa “Provide Instruments” ac

32、tivity SDa “Submit Data” activity URa “Utilize benchmarking Results” activity 5 Benchmarking process model 5.1 Outline of the benchmarking process model IT project performance benchmarking requires various mutually related activities to be executed systematically as presented in Figure A.1. In addit

33、ion, it outlines requirements for data retention and storage activities for an organizational benchmarking repository. To ensure that all activities in the benchmarking framework will be managed and systematically executed, this part of ISO/IEC 29155 adopts a three-layered benchmarking management pr

34、ocess model (see Figure 2) that consists of: Business layer, which takes responsibility for organizational business decision making and commitment, Program layer, which controls all benchmarking activities in the organization and supervises projects, Project and operational layer, which consists of

35、various projects and/or operations to perform one or more allocated activities. NOTE 1 The project and operational layer corresponds to the IT project performance benchmarking framework that was introduced in ISO/IEC 29155-1 (Concepts and definitions) of which an excerpted outline is included as Ann

36、ex A .2 ISO/IEC 2013 All rights reservedBS ISO/IEC 29155-2:2013ISO/IEC 29155-2:2013(E) NOTE 2 Depending on the maturity of the organization, IT project performance benchmarking might include only the activities in the project and operational layer. For example, an organization might choose to pilot

37、a benchmarking activity as a single instance of benchmarking. Figure 2 Benchmarking process model Table 1 presents a description of the activities for which each layer is responsible, and to which activities other layers participate. NOTE 3 In this part of ISO/IEC 29155, the word “project” (except w

38、hen it is prefixed with IT as in, IT project) means performing a benchmarking activity as a project. ISO/IEC 2013 All rights reserved 3BS ISO/IEC 29155-2:2013ISO/IEC 29155-2:2013(E) Table 1 Responsibility and activity assignments in benchmarking process model Assignment (Action) Responsibility Busin

39、ess layer Program layer Project and operational layer Identify organizational needs and priorities for benchmarking, establish long term benchmarking plan, identify and allocate the necessary resources, and commit to the execution of benchmark- ing plan. R C, I I Establish execution plan to implemen

40、t the benchmarking plan, allocate the necessary activities to multiple projects and opera- tions, invoke and manage progress. C R C, I Prepare and execute activity. I C,I R Responsibilities: R: Responsible, C: Consulted, I: Informed. The processes at each layer require the following task groups: G1

41、“Initiating”, which launches a project, G2 “Planning”, which establishes a project plan, G3 “Executing”, which conducts one or more benchmarking activities, G4 “Evaluating”, which evaluates processes and outcomes of the benchmarking activities, G5 “Improving”, which plans the changes to be implement

42、ed for future benchmarking based on lessons learned. 5.2 Requirements and tasks for business layer The following tasks should be performed: a) identify business goals for the organization, b) specify how benchmarking can provide information to support the business goals, c) launch a benchmarking pro

43、gram, d) create and maintain the benchmarking plan, e) receive and evaluate the benchmarking feedback against the business goal(s), f) decide improvement actions. Strategic management of benchmarking is performed at the business layer. For this reason, the organization should execute a “manage bench

44、marking business level” activity. The activity includes, but is not limited to, following tasks: specify the purpose of adopting IT project performance benchmarking, map the organizational focus on the aspects of IT project performance, define role(s) of the organization (e.g. benchmarking service p

45、rovider and/or benchmarking user), check strategic programs to justify the business goals of organization, estimate the amount of resources to be invested in the benchmarking program, check and justify the organizational policy to allocate outsourced or in-house resources in various benchmarking act

46、ivities.4 ISO/IEC 2013 All rights reservedBS ISO/IEC 29155-2:2013ISO/IEC 29155-2:2013(E) determine acceptance criteria for the program, assign the program to one or more organizational units, acquire commitments to ensure the execution of the program, evaluate the adequacy of human and financial res

47、ources to execute the program. 5.3 Requirements and tasks for program layer At the program layer, a program steering committee shall be organized to activate and control each program. The program steering committee shall: a) determine the total number of projects and operations within the program, b

48、) establish a project and operational level work breakdown plan for the execution of the program, c) divide benchmarking activities into projects and operations, d) assign projects and operations to organizational units, e) launch projects and operations by allocating necessary resources, f) synchro

49、nize the management practices, g) supervise and control the progress, h) perform mutual adjustments to coordinate the project(s) and operation(s), i) indicate the observable improvements to business layer. The organization should execute a “manage benchmarking program level” activity. The activity includes, but is not limited to, following tasks: break the assigned mission (purpose) of the program into projects and operations, determine acceptance crite