1、 ISO 2017 All rights reserved C:UsersannetterDesktopAnnetteWG226515IEEE_26515-D1.docx Basic template BASICEN3 2002-06-01 ISO/IEC/IEEE CD 26515 d1 Second edition Date: 2017-03-30 ISO/IEC/IEEE TC JTC1/SC 7/WG 2 Secretariat: SCC Systems and software engineering Developing information for users in an ag
2、ile environment Warning This document is not an ISO International Standard. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an International Standard. Recipients of this draft are invited to submit, with their comments, notification of a
3、ny relevant patent rights of which they are aware and to provide supporting documentation. Document type: International standard Document subtype: if applicable Document stage: (30) Committee Document language: E Copyright notice This ISO document is a working draft or committee draft and is copyrig
4、ht-protected by ISO. While the reproduction of working drafts or committee drafts in any form for use by participants in the ISO standards development process is permitted without prior permission from ISO, neither this document nor any extract from it may be reproduced, stored or transmitted in any
5、 form for any other purpose without prior written permission from ISO. Requests for permission to reproduce this document for the purpose of selling it should be addressed as shown below or to ISOs member body in the country of the requester: ISO copyright office IEC Central Office Institute of Elec
6、trical and Case postal 56 3, rue de Varemb Electronics Engineers, Inc. CH-1211 Geneva 20 CH-1211 Geneva 20 3 Park Avenue, New York Tel. + 41 22 749 01 11 Switzerland NY 10016-5997, USA Fax + 41 22 749 09 47 E-mail inmailiec.ch E-mail stds.iprieee.org E-mail copyrightiso.org Web www.iec.ch Web www.ie
7、ee.org Web www.iso.org Reproduction for sales purposes may be subject to royalty payments or a licensing agreement. Violators may be prosecuted. Contents Page 1 Scope . 1 2 Normative references . 1 3 Terms and definitions . 1 4 Conformance . 3 5 Information development process in an agile environmen
8、t 4 6. Management of information development in an agile environment . 4 6.1 Information management considerations for agile development . 4 6.2 Change management for Agile development 5 6.3 Composition of agile development teams 5 6.3.1 General . 5 6.3.2 Communication in agile development teams . 5
9、 6.3.3 Globally distributed teams 6 6.4 Management of information development across teams using agile development 7 6.5 Management of information development tasks across iterations . 7 6.5.1 General . 7 6.5.2 Planning the project as a whole. 7 6.5.3 Sizing and resourcing each iteration 8 6.5.4 Han
10、dling last-minute content changes . 10 6.6 Monitoring and analyzing progress in an agile environment . 10 6.6.1 General . 10 6.6.2 Stand-up meetings 10 6.6.3 Monitoring progress 10 6.6.4 Rework and changing requirements 11 6.7 Stakeholder involvement 11 6.8 Improving the information development proc
11、ess in an agile environment . 12 6.8.1 General . 12 6.8.2 Assessing customer satisfaction 12 7 Developing information for users in an agile environment . 12 7.1 Relationship of agile development to information development 12 7.2 Product design and developing information for users 12 7.3 Design and d
12、evelopment of information for users in an agile environment 13 7.3.1 General . 13 7.3.2 Design techniques 14 7.3.3 Information development tasks 16 7.3.4 Planning of information for users . 17 7.4 Testing and reviewing information for users in an agile environment 17 7.4.1 Reviewing information for
13、users . 18 7.4.2 System test of information for users . 18 7.4.3 Usability testing of information for users 18 7.5 Translation and localization of information for users 19 7.6 Production of Information for users . 19 7.7 Delivering information for users with a continuous delivery process (DevOps) .
14、19 Annex A (informative) Agile Development Practices . 21 Bibliography . 23 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
15、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, go
16、vernmental 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. IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating C
17、ommittees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus development process, approved by the American National Standards Institute, which brings together volunteers representing varied viewpoints and interests to achieve the final pr
18、oduct. Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote fairness in the consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of the i
19、nformation contained in its standards. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of ISO/IEC JTC 1 is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated
20、 to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is called to the possibility that implementation of this standard may require the use of subject matter covered by patent rights. By publicatio
21、n of this standard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. ISO/IEEE is not responsible for identifying essential patents or patent claims for which a license is required, for conducting inquiries into the legal validity or scope o
22、f patents or patent claims, or determining whether any licensing terms or conditions provided in connection with the submission of a Letter of Assurance or a Patent Statement and Licensing Declaration Form, if any, or in any licensing agreements are reasonable or non-discriminatory. Users of this st
23、andard are expressly advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. It is possible to obtain further information from ISO or the IEEE Standards Association. ISO/IEC/IEEE 26515 was prepared by Joint T
24、echnical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering, in cooperation with the Systems and Software Engineering Committee of the IEEE Computer Society, under the Partner Standards Development Organization cooperation agreement between ISO and I
25、EEE. This version gives an overview of agile methodologies although it neither encourages nor discourages the use of any particular agile methodology. Therefore, this version uses generic agile terminology as much as possible. This second edition of ISO/IEC/IEEE 26515 cancels and replaces ISO/IEC/IE
26、EE 26515:2011 with technical revisions: alignment with the widespread use of agile methods to include systems as well as software; replacement of the paper-based term “documentation” with the general term “information for users” where appropriate; inclusion of agile information development across mu
27、ltiple teams and projects, especially projects in continuous maintenance situations such as DevOps; editorial changes; new definitions. CD ISO/IEC/IEEE 26515 vi ISO/IEC / IEEE 2017 All rights reserved Introduction Software with an application user interface should generally be intuitive for most use
28、rs or follow common user interface conventions that limit the need for exhaustive or detailed documentation. However, users should be provided with accurate information about how to use the softwares functions if questions arise. This information should explain the major features or use cases delibe
29、rately created for all types of users. The information should be easily accessible and clearly written to enable quick learning and user proficiency, while reducing help desk support. Hence, well designed information not only assists the users and helps to reduce the cost of training and support, bu
30、t also enhances the reputation of the product, its producer, and its suppliers. Projects that implement 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 processe
31、s in parallel, rather than planning for an entire project in distinct phases. Although agile development methods often advocate less life cycle documentation, the users of a software product still expect and require quality information to be provided with these software products. Although the end re
32、sults of the process for developing information for users are the same, the methods may be very different in an agile environment. Agile development methods follow short, iterative development cycles and continuous refactoring based on customer requirements and feedback. In order to fulfill contract
33、ual requirements and provide valuable information for users, the main goal is to produce all information deliverables related to features developed during every iteration. The quantity and quality of the information deliverables will depend on the completeness and maturity of the software features a
34、nd design after each iteration, specified through user stories, tasks and personas. Information developers and other personnel involved in developing information for users should understand the agile development processes and methods used by their organization. This will enable them to tie in seamle
35、ssly and provide relevant and useful information for users. Because of the nature of agile development methods, the traditional means of developing information (both print and onscreen) for end users are not entirely applicable. This document was developed to assist users of the following documents:
36、 ISO/IEC/IEEE 15288:2015 Systems and software engineering System life cycle processes; ISO/IEC 12207 (IEEE Std 12207), Systems and software engineering Software life cycle processes; ISO/IEC 26514:2008 Systems and software engineering Requirements for designers and developers of user documentation (
37、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); Other documents in the ISO/IEC/IEEE 265NN family of International Standards. It provides requirements and guidan
38、ce to information developers and related roles on how to adapt the processes described in the ISO/IEC 265NN family of International Standards to develop quality information for users. The International Standard is independent of the agile development methods and tools that are used to produce the so
39、ftware. COMMITTEE DRAFT ISO/IEC 26515 ISO/IEC/IEEE 2017 All rights reserved 1 Systems and software engineering Developing information for users in an agile environment 1 Scope This document supports the interest of information developers and associated roles responsible for producing information for
40、 users for software and systems developed within an agile environment. This document takes a process standard approach to specify the way in which information for users can be developed in agile development projects. This document provides requirements of information management and information devel
41、opment processes appropriate for software projects that are using agile development methods. Clause 5 covers the overall requirements for information in the software life cycle. Clause 6 covers requirements for the information development lead or project manager to plan an agile information developm
42、ent project and manage the information development activities in an agile environment. Clause 7 covers requirements for designing, developing, and providing information for users in an agile environment. Annex A describes agile development practices and methods. This document is intended neither to
43、encourage nor to discourage the use of any particular agile development tools or methods. This document provides guidance on processes appropriate for information developers of information for users in software and systems projects that are using agile development methodologies. It is not limited to
44、 the development phase of the life cycle of information for users, but includes activities throughout the whole life cycle. This document is intended for use in all organizations that are using agile development, or are considering implementing their projects using these techniques. It is assumed th
45、at users of this document have experience or general knowledge of information for users (traditionally called “user documentation”) and agile processes. 2 Normative references There are no normative references in this document. 3 Terms and definitions For the purposes of this document, the following
46、 terms and definitions apply. 3.1 agile development software development approach based on iterative development, frequent inspection and adaptation, and incremental deliveries in which requirements and solutions evolve through collaboration in cross-functional teams and through continuous stakehold
47、er feedback Note 1 to entry: Any use of the word “agile” in this document refers to methodology. Various agile methods can be found in Annex A. CD ISO/IEC/IEEE 26515 2 ISO/IEC/IEEE 2017 All rights reserved 3.2 agile environment organizational culture, infrastructure, and methodologies that support a
48、gile development 3.3 agile team organization or team implementing agile development methods and approaches Note 1 to entry: Typically with roles such as team lead, product owner, user or user representative, software and information developers, and testers. 3.4 DevOps integrated activities of softwa
49、re development, testing, and operational IT to support the reliable building, testing, and releasing of software in rapid succession Note 1 to entry: DevOps supports Agile methodologies by implementing a culture of communication between development, quality assurance, and IT operations for continuous delivery, due to continuous integration and automated releases. 3.5 documentation information that explains how to use software, devices, applications, or services Note 1 to entry: Throughout this document, the term documentation refer
