IEEE ISO IEC 26515 2012
$54.17
Systems and software engineering — Developing user documentation in an agile environment
Published By | Publication Date | Number of Pages |
IEEE | 2012 | 36 |
New IEEE Standard – Active. ISO/IEC/IEEE 26515:2012 specifies the way in which user documentation can be developed in agile development projects. It is intended for use in all organizations that are using agile development, or are considering implementing their projects using these techniques. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. ISO/IEC/IEEE 26515:2012 addresses the relationship between the user documentation process and the life cycle documentation process in agile development. It describes how the information developer or project manager may plan and manage the user documentation development in an agile environment. It is intended neither to encourage nor to discourage the use of any particular agile development tools or methods.
PDF Catalog
PDF Pages | PDF Title |
---|---|
1 | ISO/IEC/IEEE 26515:2012(E) Front Cover |
3 | Contents |
4 | Foreword |
5 | Introduction |
7 | 1 Scope 2 Conformance 2.1 Application of conformance |
8 | 3 Normative references 4 Terms and definitions |
10 | 5 User documentation processes in an agile environment 5.1 Relationship between user and life cycle documentation processes |
11 | 5.2 Life cycle software documentation in an agile environment |
12 | 5.3 Life cycle documentation in agile development 6 Management of information development in an agile environment 6.1 Documentation management considerations for agile development |
13 | 6.2 Change management when moving to an agile development process 6.3 Composition of agile development teams |
14 | 6.3.1 Communication in agile development teams 6.3.2 Teams working in different locations |
15 | 6.4 Management of information development across teams using agile development 6.5 Management of tasks across sprints 6.5.1 Planning the project as a whole |
16 | 6.5.2 Sizing and resourcing each sprint 6.5.2.1 Sizing information development work |
17 | 6.5.2.2 Assigning information development resources 6.5.3 Handling last-minute documentation changes 6.6 Monitoring and analysing progress in an agile environment 6.6.1 Status meetings |
18 | 6.6.2 Monitoring progress |
19 | 6.6.3 Rework and changing requirements 6.7 Stakeholder involvement |
20 | 6.8 Improving the user documentation process in an agile environment 6.8.1 Assessing customer satisfaction 7 Developing user documentation in an agile environment 7.1 What agile development means for information development |
21 | 7.2 Product design and developing the user documentation |
22 | 7.3 Design and development of user documentation in an agile environment 7.3.1 Design techniques 7.3.1.1 Use cases |
23 | 7.3.1.2 User roles 7.3.1.3 Personas |
24 | 7.3.1.4 User stories |
25 | 7.3.1.5 Scenarios |
26 | 7.3.2 Information development tasks 7.3.3 Planning of information units 7.4 Testing and reviewing documentation in an agile environment 7.4.1 Reviewing user documentation |
27 | 7.4.2 System test of documentation 7.4.3 Usability testing of user documentation |
28 | 7.5 Translation and localisation of user documentation 7.6 Production for manufacturing cycles |
29 | Annex A (informative) Agile Development Practices |
31 | Annex B (informative) Example interview questions |
33 | Bibliography |
35 | IEEE Notice to Users |