ISO/IEC TR 29119-6:2021

TECHNICAL ISO/IEC TR
REPORT 29119-6
First edition
2021-07
Software and systems engineering —
Software testing —
Part 6:
Guidelines for the use of ISO/IEC/IEEE
29119 (all parts) in agile projects
Ingénierie du logiciel et des systèmes — Essais du logiciel —
Partie 6: Lignes directrices pour l'utilisation de l'ISO/IEC/IEEE 29119
(toutes les parties) dans les projets agiles
Reference number
©
ISO/IEC 2021
© ISO/IEC 2021
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO/IEC 2021 – All rights reserved

Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Concepts . 1
4.1 Agile practices and artefacts . 1
4.2 Mapping of agile practices to ISO/IEC/IEEE 29119-2 test processes . 2
4.2.1 Overview . 2
4.2.2 Acceptance criteria . 3
4.2.3 Acceptance test-driven development (ATDD) . 3
4.2.4 Amplify learning . 3
4.2.5 Backlog management . 3
4.2.6 Behaviour-driven development (BDD) . 4
4.2.7 Build integrity in . 5
4.2.8 Burn-down and burn-up charts . 5
4.2.9 Co-located teams . . 6
4.2.10 Collective code ownership . 6
4.2.11 Continuous delivery and deployment. 6
4.2.12 Continuous integration and continuous testing . 7
4.2.13 Cross-functional team . 7
4.2.14 Daily stand-up . 8
4.2.15 Definition of done . 8
4.2.16 Definition of ready . 9
4.2.17 Eliminate waste .10
4.2.18 Empowered team .11
4.2.19 Emergent design .11
4.2.20 Epic .11
4.2.21 Fast user feedback .11
4.2.22 Feature-driven development (FDD) .12
4.2.23 Feature toggle .12
4.2.24 Frequent interaction with product owner .12
4.2.25 Increment .12
4.2.26 Informal defect management .12
4.2.27 Iteration backlog .13
4.2.28 Iteration goal .13
4.2.29 Iteration planning .13
4.2.30 Iteration review .13
4.2.31 Iteration zero .14
4.2.32 Just in time .14
4.2.33 Limit work in progress .14
4.2.34 Mood chart .14
4.2.35 Occasional test iterations .15
4.2.36 Pair programming .15
4.2.37 Parallel test iterations .15
4.2.38 Planning poker.15
4.2.39 Product backlog .16
4.2.40 Product owner .16
4.2.41 Refactoring .16
4.2.42 Relative estimation .16
4.2.43 Release planning .17
4.2.44 Retrospective meeting .17
4.2.45 Scrum master .17
© ISO/IEC 2021 – All rights reserved iii

4.2.46 Self-organizing teams .17
4.2.47 Short iterations .17
4.2.48 Simplicity .18
4.2.49 Story mapping .18
4.2.50 Story testing .18
4.2.51 Sustainable pace .18
4.2.52 Task board .18
4.2.53 Team charter .18
4.2.54 Team room .18
4.2.55 Team-based estimation .19
4.2.56 Technical debt .19
4.2.57 Test-driven development (TDD) .19
4.2.58 Timebox .20
4.2.59 Transparency .20
4.2.60 User story .20
4.2.61 User stories – INVEST mnemonic.20
4.2.62 User story format – role/feature/rationale .20
4.2.63 Velocity .21
Annex A (informative) Mapping of The Scrum Guide to ISO/IEC/IEEE 29119-2 test processes .22
Annex B (informative) Mapping of ISO/IEC/IEEE 29119-2 (test processes) to agile practices
and techniques covered under Clause 4.24
Annex C (informative) Example mapping of typical agile test artefacts to
ISO/IEC/IEEE 29119-3 test documentation .37
Annex D (inform
...