BSI PD ISO/IEC TR 29119-6:2021

$198.66

Software and systems engineering. Software testing – Guidelines for the use of ISO/IEC/IEEE 29119 (all parts) in agile projects

Published By	Publication Date	Number of Pages
BSI	2021	54

Guaranteed Safe Checkout

Category: BSI

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

This document provides guidance for the application of ISO/IEC/IEEE 29119 (all parts) in agile life cycles. This document is intended for (and not limited to) testers, test managers, business analysts, product owners, Scrum masters and developers involved in agile projects. The mappings provided in this document are designed to benefit any team or organization that is either moving away from traditional/waterfall life cycles and into agile or vice versa as well as new organizations that are commencing agile as their chosen life cycle. It is designed to be understandable regardless of the reader’s familiarity with ISO/IEC/IEEE 29119 (all parts).

PDF Catalog

PDF Pages	PDF Title
2	National foreword
7	Foreword
8	Introduction
9	1 Scope 2 Normative references 3 Terms and definitions 4 Concepts 4.1 Agile practices and artefacts
10	4.2 Mapping of agile practices to ISO/IEC/IEEE 29119‑2 test processes 4.2.1 Overview
11	4.2.2 Acceptance criteria 4.2.3 Acceptance test-driven development (ATDD) 4.2.4 Amplify learning 4.2.5 Backlog management
12	4.2.6 Behaviour-driven development (BDD)
13	4.2.7 Build integrity in 4.2.8 Burn-down and burn-up charts
14	4.2.9 Co-located teams 4.2.10 Collective code ownership 4.2.11 Continuous delivery and deployment
15	4.2.12 Continuous integration and continuous testing 4.2.13 Cross-functional team
16	4.2.14 Daily stand-up 4.2.15 Definition of done
17	4.2.16 Definition of ready
18	4.2.17 Eliminate waste
19	4.2.18 Empowered team 4.2.19 Emergent design 4.2.20 Epic 4.2.21 Fast user feedback
20	4.2.22 Feature-driven development (FDD) 4.2.23 Feature toggle 4.2.24 Frequent interaction with product owner 4.2.25 Increment 4.2.26 Informal defect management
21	4.2.27 Iteration backlog 4.2.28 Iteration goal 4.2.29 Iteration planning 4.2.30 Iteration review
22	4.2.31 Iteration zero 4.2.32 Just in time 4.2.33 Limit work in progress 4.2.34 Mood chart
23	4.2.35 Occasional test iterations 4.2.36 Pair programming 4.2.37 Parallel test iterations 4.2.38 Planning poker
24	4.2.39 Product backlog 4.2.40 Product owner 4.2.41 Refactoring 4.2.42 Relative estimation
25	4.2.43 Release planning 4.2.44 Retrospective meeting 4.2.45 Scrum master 4.2.46 Self-organizing teams 4.2.47 Short iterations
26	4.2.48 Simplicity 4.2.49 Story mapping 4.2.50 Story testing 4.2.51 Sustainable pace 4.2.52 Task board 4.2.53 Team charter 4.2.54 Team room
27	4.2.55 Team-based estimation 4.2.56 Technical debt 4.2.57 Test-driven development (TDD)
28	4.2.58 Timebox 4.2.59 Transparency 4.2.60 User story 4.2.61 User stories – INVEST mnemonic 4.2.62 User story format – role/feature/rationale
29	4.2.63 Velocity
30	Annex A (informative) Mapping of The Scrum Guide to ISO/IEC/IEEE 29119‑2 test processes
32	Annex B (informative) Mapping of ISO/IEC/IEEE 29119‑2 (test processes) to agile practices and techniques covered under Clause 4
45	Annex C (informative) Example mapping of typical agile test artefacts to ISO/IEC/IEEE 29119‑3 test documentation
47	Annex D (informative) Example agile test artefact
53	Bibliography