The document discusses how quality and agile development are not contradictory but rather necessary. It defines quality using various frameworks and argues that quality in agile focuses on building the right product and meeting requirements and customer needs as they evolve. Various agile practices for testing such as test-driven development, different levels of testing, and fixing bugs early are described as helping ensure quality.

1. Agile and Quality
It is not an Oxymoron but a Necessity
Ralph Jocham
25-­‐Nov-­‐2011
effective agile. ralph@effectiveagile.com
1

2. 25-­‐Nov-­‐2011
effective agile. 2

3. Quality
Six
Sigma
Number
of
defects
per
million
ISO
9000
opportuni8es
Degree
to
which
a
set
of
inherent
characteris8cs
fulfills
Philip
B.
Crosby
requirements
Conformance
to
requirements
25-­‐Nov-­‐2011
effective agile. 3

4. 35% of Requirements Change
25-­‐Nov-­‐2011
effective agile. 4

5. 25-­‐Nov-­‐2011
effective agile. 5

6. 25-­‐Nov-­‐2011
effective agile. 6

7. Quality a better definition
Intrinsic
Must-­‐be
Fitness
for
Use
Quality
Noriaki
Kano
Extrinsic
What
the
customer
AHracIve
would
love,
but
has
Quality
not
yet
thought
about
25-­‐Nov-­‐2011
effective agile. 7

8. 25-­‐Nov-­‐2011
effective agile. 8

9. Right Product
Original
Solu8on
Domain
Welcoming
Change/
Coping
with
Complexity
Spri t
n+1
nt
n
Sprin
Addi8onal
Value
2
Sprin Sprint
t
1
Original
Vision
25-­‐Nov-­‐2011
effective agile. 9

10. >60% of features are rarely or never used
(source:
Standish
Group)
25-­‐Nov-­‐2011
effective agile. 10

11. Scrum
Review
Retrospec8ve
Increment
Daily
Scrum
Sprint
Sprint
Sprint
Backlog
Planning
Mee8ng
Product
Backlog
ScrumMaster
(source:
ADM)
25-­‐Nov-­‐2011
effective agile. 11

12. Right Quality – No!
SoTware
Interpret
Spec
Spec
Interpret
Spec
to
Design
and
to
Design
and
Code
System
Script
Test
Cases
Code
Test
and
Spec
Executable
And
Images
Match?
Scripts
(source:
Mary
Poppendieck)
25-­‐Nov-­‐2011
effective agile. 12

13. Right Quality – Yes!
Implement
incrementally
Define
Spec
to
saIsfy
the
Details
next
test
plus
Code
SoQware
Incrementally
and
as
Tests
Executable
Spec
and
Scripts
all
those
from
previous
Images
increments
(source:
Mary
Poppendieck)
25-­‐Nov-­‐2011
effective agile. 13

14. Agile Testing Quadrants
Automated
Business-­‐Facing
Manual
Func8onal
Tests
Exploratory
Tes8ng
Story
Tests
Usability
Tes8ng
Suppor8ng
the
Team
Examples
User
Acceptance
Tes8ng
Cri8que
Product
Q2
Q3
Q1
Q4
Performance
&
Load
Tes8ng
Unit
Test
Security
Tes8ng
Component
Tests
‚ility‘
Tes8ng
Automated
Tools
Technology-­‐Facing
(source:
Brian
Marick)
25-­‐Nov-­‐2011
effective agile. 14

15. Agile Testing Quadrants
Automated
Business-­‐Facing
Manual
What
Func8onal
Tests
Exploratory
Tes8ng
VStory
Tests
n
alida8o
Usability
Tes8ng
Suppor8ng
the
Team
Examples
User
Acceptance
Tes8ng
Cri8que
Product
Acceptanc
e
Cri teria
Every
Q2
Q3
Sprint
Q1
Q4
HOTW
n
Performance
&
Load
Tes8ng
NFR
.
Unit
est
ifica8o
Security
Tes8ng
Component
Tests
Ver ‚ility‘
Tes8ng
Automated
Tools
Technology-­‐Facing
(source:
Brian
Marick)
25-­‐Nov-­‐2011
effective agile. 15

16. Agile Testing and Tiers
UI
Q3
Business
Q2
Q4
Domain
Q1
Persistence
25-­‐Nov-­‐2011
effective agile. 16

17. ATDD to TDD
(source:
David
Starr)
(source:
David
Starr)
25-­‐Nov-­‐2011
effective agile. 17

18. Cost of fixing a Bug
Construc8on
Detailed
Design
Architecture
Requirements
Requirements
Architecture
Requirements
Detailed
Design
Architecture
Detailed
Design
Construc8on
Construc8on
Maintenance
25-­‐Nov-­‐2011
effective agile. 18

19. Review
Retrospec8ve
Increment
Daily
Scrum
Sprint
Sprint
Sprint
Backlog
Planning
Mee8ng
Product
Backlog
ScrumMaster
(source:
David
Starr)
25-­‐Nov-­‐2011
effective agile. 19

20. Questions?
25-­‐Nov-­‐2011
effective agile. 20

21. Ralph Jocham
www.effecIveagile.com
effective agile. ralph@effec8veagile.com
@rjocham
25-­‐Nov-­‐2011
effective agile. 21