1、raising standards worldwide NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW BSI Standards Publication BS ISO/IEC 26515:2011 Systems and software engineering Developing user documentation in an agile environmentBS ISO/IEC 26515:2011 BRITISH STANDARD National foreword This Briti
2、sh Standard is the UK implementation of ISO/IEC 26515:2011. The UK participation in its preparation was entrusted to T e c h n i c a l C o m m i t t e e I S T / 1 5 , S o f t w a r e a n d s y s t e m s e n g i n e e r i n g . A list of organizations represented on this committee can be obtained on
3、request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2012 Published by BSI Standards Limited 2012 ISBN 978 0 580 73278 2 ICS 35.080 Compliance with a Bri
4、tish Standard cannot confer immunity from legal obligations. This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 March 2012. Amendments issued since publication Date T e x t a f f e c t e dBS ISO/IEC 26515:2011Reference number ISO/IEC 26515:20
5、11(E) ISO/IEC 2011INTERNATIONAL STANDARD ISO/IEC 26515 First edition 2011-12-01 Systems and software engineering Developing user documentation in an agile environment Ingnierie du logiciel et des systmes Dveloppement de la documentation de lutilisateur dans un environnement agile BS ISO/IEC 26515:20
6、11 ISO/IEC 26515:2011(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2011 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 microfilm, without permission in writing fro
7、m 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 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2011 All rights reservedBS ISO/IEC 26
8、515:2011 ISO/IEC 26515:2011(E) ISO/IEC 2011 All rights reserved iiiContents Page Foreword iv Introduction . v 1 Scope 1 2 Conformance . 1 2.1 Application of conformance . 1 3 Normative references 2 4 Terms and definitions . 2 5 User documentation processes in an agile environment . 4 5.1 Relationshi
9、p between user and life cycle documentation processes . 4 5.2 Life cycle software documentation in an agile environment 5 5.3 Life cycle documentation in agile development 6 6 Management of information development in an agile environment 6 6.1 Documentation management considerations for agile develo
10、pment 6 6.2 Change management when moving to an agile development process . 7 6.3 Composition of agile development teams 7 6.3.1 Communication in agile development teams . 8 6.3.2 Teams working in different locations 8 6.4 Management of information development across teams using agile development 9
11、6.5 Management of tasks across sprints 9 6.5.1 Planning the project as a whole . 9 6.5.2 Sizing and resourcing each sprint . 10 6.5.3 Handling last-minute documentation changes 11 6.6 Monitoring and analysing progress in an agile environment . 11 6.6.1 Status meetings . 11 6.6.2 Monitoring progress
12、12 6.6.3 Rework and changing requirements . 13 6.7 Stakeholder involvement 13 6.8 Improving the user documentation process in an agile environment . 14 6.8.1 Assessing customer satisfaction 14 7 Developing user documentation in an agile environment 14 7.1 What agile development means for information
13、 development . 14 7.2 Product design and developing the user documentation . 15 7.3 Design and development of user documentation in an agile environment 16 7.3.1 Design techniques . 16 7.3.2 Information development tasks . 20 7.3.3 Planning of information units 20 7.4 Testing and reviewing documenta
14、tion in an agile environment 20 7.4.1 Reviewing user documentation . 20 7.4.2 System test of documentation . 21 7.4.3 Usability testing of user documentation . 21 7.5 Translation and localisation of user documentation . 22 7.6 Production for manufacturing cycles 22 Annex A (informative) Agile Develo
15、pment Practices 23 Annex B (informative) Example interview questions 25 Bibliography 27 BS ISO/IEC 26515:2011 ISO/IEC 26515:2011(E) iv ISO/IEC 2011 All rights reservedForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the sp
16、ecialized 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
17、 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. Intern
18、ational Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. 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 votin
19、g. Publication as an International Standard requires approval by at least 75 % of the national bodies 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
20、 all such patent rights. ISO/IEC 26515 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering. BS ISO/IEC 26515:2011 ISO/IEC 26515:2011(E) ISO/IEC 2011 All rights reserved vIntroduction Anyone who uses application software
21、 needs accurate information about how the software will help the users accomplish a task. The documentation may be the first tangible item that the user sees, and so influences the first impressions the users have of the product. If the information is supplied in a convenient form and is easy to fin
22、d and understand, the users can quickly become proficient at using the product. Hence, well designed documentation not only assists the users and helps to reduce the cost of training and support, but also enhances the reputation of the product, its producer, and its suppliers. Projects that implemen
23、t agile development focus on providing rapid and frequent deliveries of high value software. These methods often involve detailed planning only for the short term, and the implementation of processes in parallel, rather than planning for an entire project in distinct phases. Although agile developme
24、nt methods often advocate less life cycle documentation, the users of a software product still expect and require quality user documentation to be provided with these software products. Although the end results of the user documentation process are the same, the methods to get there may be very diff
25、erent in an agile environment. Agile development methods may lead to the production of less user documentation, but the user documentation developed must be sufficient to meet the needs and requirements of the users. If the deliverables of user documentation and associated life cycle documentation a
26、re agreed in a contractual relationship between an acquirer and a supplier, then the deliverables that are produced are dictated by the terms of the contract. In these circumstances, the user and life cycle documentation deliverables that are agreed upon will depend on the demands of the acquiring o
27、rganization regardless of the types of development methodologies used to produce them. Technical writers and other personnel involved in the production of user documentation should understand the agile development processes used by their organization, and use the most effective agile development met
28、hods to produce relevant and useful user documentation. Because of the nature of agile development methods, the traditional means of developing the end user documentation (both print and onscreen) as described in the current ISO/IEC 2651n family of International Standards are not entirely applicable
29、. This International Standard was developed to assist users of ISO/IEC 15288:2008 (IEEE Std 15288:2008), Systems and software engineering System life cycle processes, or ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering Software life cycle processes, and ISO/IEC 26514, Syste
30、ms and software engineering Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering Requirements for Designers and Developers of User Documentation) and others in the IS
31、O/IEC 2651n family of International Standards. It provides requirements and guidance to technical writers and related roles on how to adapt the processes described in the ISO/IEC 2651n family of International Standards to develop quality user documentation. This International Standard is independent
32、 of the agile development methods and tools that are used to produce the software. This International Standard will conform to ISO/IEC 12207:2008 (IEEE Std 12207:2008) as an implementation of the user documentation part of 6.1: Documentation. The primary references for this International Standard ar
33、e ISO/IEC 26514:2008 and ISO/IEC 26513:2009. BS ISO/IEC 26515:2011BS ISO/IEC 26515:2011 INTERNATIONAL STANDARD ISO/IEC 26515:2011(E) ISO/IEC 2011 All rights reserved 1Systems and software engineering Developing user documentation in an agile environment 1 Scope This clause presents the scope, purpos
34、e, organization, and candidate uses of this International Standard. This International Standard supports the interest of technical writers and associated roles responsible for producing user documentation for software and systems developed within an agile environment. This International Standard tak
35、es a process standard approach to specify the way in which user documentation can be developed in agile development projects. This International Standard provides requirements on information management and documentation processes appropriate for software projects that are using agile development met
36、hods. Clause 5 covers the overall requirements for documentation in the software life cycle. Clause 6 describes how the information development lead or project manager may plan and manage the user documentation development team in an agile environment. Clause 7 covers the relationship between the us
37、er documentation process and life cycle documentation process in agile development. This International Standard is intended neither to encourage nor to discourage the use of any particular agile development tools or methods. This International Standard provides guidance on processes appropriate for
38、developers of user documentation in software and systems projects that are using agile development methodologies. It will not be limited to the development phase of the life cycle of user documentation, but includes activities throughout the user documentation life cycle. This International Standard
39、 is intended for use in all organizations that are using agile development, or are considering implementing their projects using these techniques. It is assumed that users of this International Standard have experience or general knowledge of traditional user documentation processes. 2 Conformance T
40、his International Standard may be used as a conformance or a guidance document for projects and organizations claiming conformance to ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering System life cycle processes and/or ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and so
41、ftware engineering Software life cycle processes. 2.1 Application of conformance Throughout this International Standard, “shall” is used to express a provision that is binding, “should” to express a recommendation among other possibilities, and “may” to indicate a course of action permissible within
42、 the limits of this International Standard. BS ISO/IEC 26515:2011 ISO/IEC 26515:2011(E) 2 ISO/IEC 2011 All rights reservedUse of the nomenclature of this International Standard for the features of agile methodology or the parts of user documentation (that is, scrum, sprint, chapters, topics, pages,
43、screens, windows, etc.) is not required to claim conformance. Conformance to this International Standard may only be claimed by an organization if all of the requirements in this International Standard can be met by the organization. When conformance is claimed for a multi- supplier program, it may
44、be the case that no individual supplier may claim conformance because no single contract calls for all the required activities. Nevertheless, the program, as a whole, may claim conformance if each of the required activities are performed by an identified party. This International Standard may be inc
45、luded or referenced in contracts or similar agreements when the parties (called the acquirer and the supplier) agree that the supplier shall deliver user documentation services in accordance with this International Standard. It may also be adopted as an in-house standard by a project or organization
46、 that decides to develop documentation in accordance with this International Standard. Organizations, projects, or multi-supplier programs intending to claim tailored conformance should consult ISO/IEC 12207/IEEE Std 12207:2008, Annex A, Tailoring Process. 3 Normative references The following refere
47、nced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC/IEEE 24765:2010, Systems and software engineering Vocabulary
48、4 Terms and definitions For the purposes of this document, the terms and definitions given in ISO/IEC/IEEE 24765 and the following apply. 4.1 agile development software development approach based on iterative development, frequent inspection and adaptation, and incremental deliveries, in which requi
49、rements and solutions evolve through collaboration in cross-functional teams and through continuous stakeholder feedback 4.2 agile environment organization or team implementing agile development methods and approaches 4.3 audience category of users sharing the same or similar characteristics and needs (for example, purpose in using the documentation, tasks, education level, abilities, training, and experience) that determine the content, structure, and use of the intended documentation NOTE There may be a number of different audiences
