ISO IEC IEEE 26515-2011 pdf download Systems and software engineering — Developing user documentation in an agile environment
Scope
This clause presents the scope, purpose, organization, and candidate uses of this lnternational Standard
This lnternational Standard supports the interest of technical writers and associated roles responsible foiproducing user documentation for software and systems developed within an agile environment. Thisinternational Standard takes a process standard approach to specify the way in which user documentatiorcan be developed in agile development projects.
This International Standard provides requirements on information management and documentation processesappropriate for software projects that are using agile development methods.
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 useidocumentation development team in an agile environment.
Clause 7 covers the relationship between the user documentation process and life cycle documentationprocess in agile development.
This lnternational Standard is intended neither to encourage nor to discourage the use of any particular agiledevelopment tools or methods.
This lnternational Standard provides guidance on processes appropriate for developers of user documentatiorin software and systems projects that are using agile development methodologies. lt will not be limited to thedevelopment phase of the life cycle of user documentation, but includes activities throughout the userdocumentation life cycle
This International Standard is intended for use in all organizations that are using agile development, or areconsiderina implementing their projects using these techniques. lt is assumed that users of this internationaStandard hav experienc or general knowledge of traditional user documentation processes.
Conformance
This lnternational Standard may be used as a conformance or a guidance document for projects andoroanizations claiming conformance to SO/EC 152882008 EEE Std 15288-2008). Svstems and softwareengineering – System life cycle processes and/or ISO/EC 12207:2008 (IEEE Std 12207-2008), Systems andsoftware engineering – Software life cycle processes.
2.1 Application of conformance
Throughout this lnternational Standard, “shal” is used to express a provision that is binding, “should” toexpress a recommendation among other possibilities, and “may” to indicate a course of action permissiblewithin the limits of this International Standard.
Use of the nomenclature of this lnternational Standard for the features of agile methodology or the parts ofuser documentation (that is, scrum, sprint, chapters, topics, pages, screens, windows, etc,) is not required toclaim conformance.
Conformance to this lnternational Standard may only be claimed by an organization if all of the requirementsin this lnternational Standard can be met by the organization. When conformance is claimed for a multisupplier program, it may be the case that no individual supplier may claim conformance because no singlecontract calls for al the required activities. Nevertheless, the program, as a whole, may claim conformance ifeach of the required activities are performed by an identified party.
This lnternational Standard may be included or referenced in contracts or similar agreements when the partiescalled the acquirer and the supplier) agree that the supplier shall deliver user documentation services iraccordance with this lnternational Standard. lt may also be adopted as an in-house standard by a project ororganization that decides to develop documentation in accordance with this lnternational Standard.
Organizations, projects,or multi-supplier programs intending to claim tailored conformance should consultSO/IEC 12207/IEEE Std 12207:2008,Annex A,Tailoring Process.
Normative references
The following referenced documents are indispensable for the application of this document, For datedreferences, only the edition cited applies. For undated references, the latest edition of the referenceddocument (including any amendments) applies.
ISO/IEC/IEEE 24765:2010, Systems and software engineering – Vocabulary
4 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/EC/IEEE 24765 and the followingapply.
4.1 agile developmentsoftware development approach based on iterative development,frequent inspection and adaptation, andincremental deliveries. in which requirements and solutions evolve through collaboration in cross-functionateams and through continuous stakeholder feedback
4.2 agile environment
organization or team implementing agile development methods and approaches