fusing the agile testing into an agile team
Post on 16-Apr-2017
430 Views
Preview:
TRANSCRIPT
manoelpthink sharp
Fusing the Agile Testing into an Agile Team
1
Manoel PimentelAgile Coach - Elabor8elabor8.com.au
manoelpthink sharp 2
manoelp
manoelpthink sharp 3
manoelpthink sharp 4
2002
manoelpthink sharp 5
manoelpthink sharp 6
manoelpthink sharp 7
manoelpthink sharp
ESL8
manoelpthink sharp
WTH faces
9
manoelpthink sharp 10
manoelpthink sharp 11
SIX! NINE!
manoelpthink sharp
Agile?12
manoelpthink sharp
Responding to change without trauma
Delivering value more often
Continuous Improvement
13
Collaboration
manoelpthink sharp 14
Agile
Scrum
XP
FDD
SAFe
LeSS
Nexu
sD
AD
Kanban
manoelpthink sharp
Individuals and interactions
Working Software
Customer Collaboration
Responding to change
Processes and Tools
Comprehensive Documentation
Contract Negotiation
Following a plan
OVER
www.agilemanifesto.org15
manoelpthink sharp
Processes and Tools
Comprehensive Documentation
Contract Negotiation
Following a plan
16
manoelpthink sharp
Processes and Tools
Comprehensive Documentation
Contract Negotiation
Following a plan
17
There's value on the right
manoelpthink sharp 18
BUT
manoelpthink sharp
Individuals and interactions
Working Software
Customer Collaboration
Responding to change
19
There's more
value on the left
manoelpthink sharp 20
Responding to change
manoelpthink sharp
Two Realms
21
manoelpthink sharp
Cause
In the predictable realm22
Effect
manoelpthink sharp 23
Software is "construction"
manoelpthink sharp
In the unpredictable realm24
Cause ?
? Effect
manoelpthink sharp 25
Software is Learning
manoelpthink sharp
speculations 26
Cause ?
? Effect
manoelpthink sharp
?27
!Speculation Learning
min(t)
min(t)
manoelpthink sharp
?28
!Speculation Learning
min(t)
min(t)
feedbackability
manoelpthink sharp
To increase our feedbackability we must
change our way of working.
29
manoelpthink sharp 30
Learning & Continuous Improvement
manoelpthink sharp
Individuals and interactions
Working Software
Customer Collaboration
Responding to change
Processes and Tools
Comprehensive Documentation
Contract Negotiation
Following a plan
OVER
www.agilemanifesto.org31
manoelpthink sharp 32
Working Software
manoelpthink sharp
Quality33
manoelpthink sharp 34
Waterfall Approach
manoelpthink sharp 35
silos
manoelpthink sharp
Analysis Design Development Test / QA Deploy
➔ Quality is at the end➔ Quality is a phase➔ Large batches (inventory)
Waterfall Approach36
RequirementRequirementRequirementRequirementRequirement
RequirementRequirement
Requirement
Requirement
Requirement
Requirement
Requirement
manoelpthink sharp 37
Agile Approach
manoelpthink sharp
➔ Orthogonal disciplines➔ Small batches➔ Focus
Agile Approach
Test / QA
38
Small business problem
Development
Design
Analysis
manoelpthink sharp
Fractal Structure
39
manoelpthink sharp 40
Fractal (noun)A curve or geometrical figure, each part of which has the same statistical character as the whole. They are useful in modelling
structures (such as snowflakes) in which similar patterns recur at progressively smaller scales, and in describing partly random or
chaotic phenomena such as crystal growth and galaxy formation.
www.oxforddictionaries.com/definition/english/fractal
/ˈfrakt(ə)l/
manoelpthink sharp 41
manoelpthink sharp 42
Th
e W
ho
le
Th
e P
arts
(fr
acta
ls)
manoelpthink sharp
Define Build Test
43
manoelpthink sharp
Agile Team44
manoelpthink sharp 45
manoelpthink sharp 46
Case Study 1
manoelpthink sharp
Two Agile Teams sharing the same big room
47
manoelpthink sharp 48
manoelpthink sharp 49
Team 1 (8 members) Team 2 (10 members)
manoelpthink sharp 50
Team 1 (8 members) Team 2 (10 members)
manoelpthink sharp 51
manoelpthink sharp
BUT52
manoelpthink sharp 53
manoelpthink sharp 54
manoelpthink sharp 55
manoelpthink sharp 56
Team 1 (8 members) Team 2 (10 members)
Team 3 ( 4 members)??
manoelpthink sharp 57
manoelpthink sharp 58
manoelpthink sharp 59
Team 1 (6 members) Team 2 (8 members)
Team 3 (4 members)
manoelpthink sharp
WHY?60
manoelpthink sharp
Tribal Instincts61
manoelpthink sharp 62
What can you do to solve this
situation?
manoelpthink sharp 63
Case Study 1.1
manoelpthink sharp
Define Build Test
64
manoelpthink sharp 65
Iterations
manoelpthink sharp 66
Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5
manoelpthink sharp 67
Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5Build
DefineDefine
Build
Define
Build Test
manoelpthink sharp
What are the consequences?
68
manoelpthink sharp 69
manoelpthink sharp 70
Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5Build
DefineDefine
Build
Define
Build Test
manoelpthink sharp 71
Let's make a small
improvement.
manoelpthink sharp 72
Our goal: Every iteration
(cycle) must deliver valuable
done things.
manoelpthink sharp 73
Our goal: Every iteration
(cycle) must get the fractal behaviour.
manoelpthink sharp 74
Iteration 1
End End
manoelpthink sharp 75
Iteration 1
De
fin
e
Bu
ild
Te
st
Iteration 2
De
fin
e
Bu
ild
Te
st
Iteration 3
De
fin
e
Bu
ild
Te
st
Iteration 4
De
fin
e
Bu
ild
Te
st
Iteration 5
De
fin
e
Bu
ild
Te
st
manoelpthink sharp 76
What you think about this
solution? What are the
consequences?
manoelpthink sharp 77
manoelpthink sharp 78
What's the real agile behaviour
inside an iteration?
manoelpthink sharp 79
Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5
Defin
e
Test
Build
Defin
e
Test
Build
Defin
e
Test
Build
Defin
e
Test
Build
Defin
eTest
Build
manoelpthink sharp 80
Team 1 (6 members) Team 2 (8 members)
Team 3 (4 members)
manoelpthink sharp 81
Team 1 (8 members) Team 2 (10 members)
manoelpthink sharp 82
It is not only about
changing roles
manoelpthink sharp 83
Change the Behaviour!
manoelpthink sharp
How?84
manoelpthink sharp 85
View (UI)
Control
Business Logic
Data
manoelpthink sharp 86
Waterfall Approach
manoelpthink sharp 87
Data
Business Logic
Controls
Views
Test
Week 1 Week 2 Week 3 Week 4
manoelpthink sharp 88
Agile Approach
manoelpthink sharp 89
Problem Driven
manoelpthink sharp 90
A small business problem
manoelpthink sharp
View (UI)
Control
Business Logic
Data
91
A small business problem
manoelpthink sharp 92
Vertical Slice
manoelpthink sharp
View (UI)
Control
Business Logic
Data
93
A small business problem
manoelpthink sharp
View (UI)
Control
Business Logic
Data
94
IncrementA small
business problem
manoelpthink sharp 95
A small business problem
manoelpthink sharp
User Story96
manoelpthink sharp
User's Point of View
97
From
manoelpthink sharp
salesman
98
manoelpthink sharp 99
I'm losing clients because I can't offer better prices
Problem:
manoelpthink sharp 100
Offer discounts
What do I want?
manoelpthink sharp 101
Who
Offer discounts SalesmanOffer better prices to my
clients
What Why
manoelpthink sharp 102
Who
Offer discounts SalesmanOffer better
prices for my clients
What Why
User Story
manoelpthink sharp 103
As a salesman
I want to offer discounts
So that I can offer better prices to my clients
User Story
manoelpthink sharp 104
Card
As a salesman
I want to offer discounts
So that I can offer better prices to my clients
manoelpthink sharp
Insufficient
105
manoelpthink sharp
Conversation
106
Card
Invitation
manoelpthink sharp 107
Card
User Interface
Architecture
Acceptance Criteria
Dependencies
manoelpthink sharp
Conversation
108
Card Confirmation
3Cs
manoelpthink sharp
Collaboration
109
manoelpthink sharp 110
Small business problem
manoelpthink sharp 111
Problem Driven
manoelpthink sharp 112
manoelpthink sharp 113
manoelpthink sharp 114
manoelpthink sharp 115
more than a technique for testing
manoelpthink sharp 116
It's a way of
thinking
manoelpthink sharp 117
manoelpthink sharp 118
TDD is an opportunity when Developers and Testers can work together.
manoelpthink sharp 119
one technique
to rule them all?
manoelpthink sharp 120
Source: Book Agile Testing - A Practical Guide for Testers and Agile Teams - Lisa Crispin
manoelpthink sharp 121
Individuals and interactions
manoelpthink sharp 122
People
manoelpthink sharp
Are you a person
or a resource?
123
manoelpthink sharp 124
People Resource
vs
manoelpthink sharp 125
Mechanical
vs
Organic
manoelpthink sharp 126
Mechanical
#Predictable
manoelpthink sharp 127
Organic
#Complexity
manoelpthink sharp
We can't predict the behaviours
128
manoelpthink sharp
We can't predict the
interactions129
manoelpthink sharp
We need to learn from the
unpredictable results from the
interactions 130
manoelpthink sharp 131
Learning & Continuous Improvement
manoelpthink sharp
Characteristics of a Great
Agile Team
132
manoelpthink sharp 133
Katzenbach Model
manoelpthink sharp 134
focus on individual tasks/deliveries
manoelpthink sharp 135
My part!
My part! My part!
My part!
My part!
manoelpthink sharp
Working as a Working Group is
easy
136
manoelpthink sharp 137
Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5Build
DefineDefine
Build
Define
Build Test
My part! My part!My part!
My part! My part!My part!
My part!
Your process can foster this type of behaviour
manoelpthink sharp 138
Are deeply committed to their purpose, goals, and
approach.
manoelpthink sharp 139
My part!
My part! My part!
My part!
My part!
Our part!
Our part! Our part!
Our part!
Our part!
manoelpthink sharp
Working as a Real Team
is hard
140
manoelpthink sharp 141
Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5
Defin
e
Test
Build
Defin
e
Test
Build
Defin
e
Test
Build
Defin
e
Test
Build
Defin
e
Test
Build
Our part!
Our part!
Our part!
Our part!
Our part!
Your process can foster this type of behaviour
manoelpthink sharp
An Agile Team is different from a Working Group
142
manoelpthink sharp
#Engaged#Self-organizing#Cross-functional
143
manoelpthink sharp
Cross Functional
144
manoelpthink sharp
Agile Team
145
=
manoelpthink sharp 146
Balancing Competencies
manoelpthink sharp 147
manoelpthink sharp 148
Generalist (broad)
Sp
eci
alis
t (d
ee
p)
manoelpthink sharp 149
Generalist
Esp
eci
alis
t
manoelpthink sharp
Agile Team150
manoelpthink sharp 151
StrongCollaboration
manoelpthink sharp 152
09am Answering emails
10am Supporting PO to writing acceptance criterias
11am Pairing with R2 create Unit Tests
1pm Automate functional tests
3pm Analysing the Jenkins Test Results
4pm Exploratory testing with Chew
manoelpthink sharp
"Testers are also on the developer team, because testing is a central component of
agile software development. Testers advocate for quality on behalf of the
customer and assist the development team in delivering the maximum business value."
Lisa Crispin
153
manoelpthink sharp 154
manoelpthink sharp
Hard change?
155
manoelpthink sharp 156
The Tester
Executor Mentor
FromTo
manoelpthink sharp
Pollenizer
157
manoelpthink sharp 158
Cross Pollination
manoelpthink sharp 159
Cross Pollination
manoelpthink sharp 160
manoelpthink sharp 161
manoelpthink sharp
Agile Team162
manoelpthink sharp
Agile?163
manoelpthink sharp
Agile Team?164
manoelpthink sharp
Responding to change without trauma
Delivering value more often
Continuous Improvement
165
Collaboration
manoelpthink sharp 166
manoelpthink sharp
manoel.pimentel .com.auemail
site & blog
Thanks :-)
top related