“Quality is something of value to
someone.”
—Jerry Weinberg
Slide 9
Slide 9 text
What’s
“Quality”
Slide 10
Slide 10 text
• Customer needs
• Feature
fi
t
• Solves the scenarios we know about
• Secure
• Performant
• Works well in production
• Plays nicely with our craptistic data
Slide 11
Slide 11 text
“Please, God,
make it stop
hurting so bad.”
Slide 12
Slide 12 text
Cut Risk
Slide 13
Slide 13 text
No lawsuits
Slide 14
Slide 14 text
“Quality”
also means
“Enough information to make my
next decision.”
Slide 15
Slide 15 text
Business Quality
is not the same
as
Technical Quality
Slide 16
Slide 16 text
Where do conversations about
Quality
happen?
Slide 17
Slide 17 text
ALL THE TIME
Slide 18
Slide 18 text
Ideation
Release Planning/Design
Iteration Planning
Building
UAT
Slide 19
Slide 19 text
Ideation =>
Validate assumptions
“Should we build this?”
Slide 20
Slide 20 text
Release Planning
=>
Are scope and basic function right?
What integrations?
What User Acceptance criteria?
What scenarios and data needed?
Slide 21
Slide 21 text
Iteration Planning =>
Do we know “Why?”
Do we know (sort of) “How?”
Good acceptance criteria?
Good data?
Slide 22
Slide 22 text
Building =>
Pair up
More test scenarios?
Clarity of value and “how?”
Slide 23
Slide 23 text
UAT =>
“Here’s all the stuff we know’s
tested. Let me go gonzo.”
Slide 24
Slide 24 text
The Thing
Slide 25
Slide 25 text
Appliance
manufacturer
Slide 26
Slide 26 text
Wants to create model
con
fi
gurations for future years.
Currently done on paper.
Or Excel.
Slide 27
Slide 27 text
e.g.
foreach model:
how many units do I build with
speci
fi
c con
fi
gurations?
Slide 28
Slide 28 text
No content
Slide 29
Slide 29 text
System must take in to account
• Model production rules
• Inventory rules
• Capacity restrictions
Slide 30
Slide 30 text
Risk:
Signi
fi
cant revenue loss if ratios
are off.
Slide 31
Slide 31 text
Ideation
Slide 32
Slide 32 text
Stakeholder
:
“I want to create, edit and view
future years’ model con
fi
gs
.
I want to use it on web and
mobile.”
Slide 33
Slide 33 text
Help business understand
total cost
(actual plus opportunity)
Slide 34
Slide 34 text
Is this feasible,
Or should we just start drinking
now?
Slide 35
Slide 35 text
Quality feedback
for
Ideation
Slide 36
Slide 36 text
• Riskiest part of biz idea?
• Biggest value for biz idea?
• Customer audience?
• Target platform(s)?
• Integrations with existing systems?
• Architectural impacts?
Slide 37
Slide 37 text
“Our basic con
fi
g system’s data
access is unstable, and we have
data consistency/accuracy
errors.”
Slide 38
Slide 38 text
“You’re asking for a wide range
of mobile device support—that
explodes our testing and
development effort.”
Slide 39
Slide 39 text
“You said you want to scale to
support concurrent access by
all of China.
“We currently have six people
who do this task.”
Slide 40
Slide 40 text
Desired outcome:
Stakeholder makes informed
decision
Slide 41
Slide 41 text
Load and Security are
business value concerns
Slide 42
Slide 42 text
Considerations
• What platforms?
• What’s reasonable load?
• How secure?
• What’s biz value?
• What happens if info is leaked?
Slide 43
Slide 43 text
Outcomes
• Drop mobile
• Use existing security
• Reasonable load expectations
Slide 44
Slide 44 text
Release
Planning
&
Design
Slide 45
Slide 45 text
At this point we’re starting to think
about
what
and
how
Slide 46
Slide 46 text
Initial design ideas
• Use central data mart
• Pull existing inventory data
• Kendo UI for grid
Slide 47
Slide 47 text
Elaborate and specify UAT
criteria
Slide 48
Slide 48 text
Discuss infrastructure needs
Slide 49
Slide 49 text
Mitigate known issues
Slide 50
Slide 50 text
Considerations
• Business scenario
s
• Acceptance criteria
• Infrastructure / integration points
• Data and environment needs
• Performance needs
• Security
Slide 51
Slide 51 text
Outcomes
• Concerns of perf on client systems
• NOT testing Kendo Grid
• Signi
fi
cant test data requirements
• Comfortable with security approach
Slide 52
Slide 52 text
Iteration
Planning
Slide 53
Slide 53 text
We’re Gonna
Do Some
Stuff!
Slide 54
Slide 54 text
Do we know enough to start
building and testing?
Slide 55
Slide 55 text
Timeline / dependencies for this
iteration
Slide 56
Slide 56 text
• Why are we building this?
• Do we have test data yet?
• Environments ready?
Slide 57
Slide 57 text
Considerations
• Test data
• Scenarios
• Automated vs. exploratory
(initial)
Slide 58
Slide 58 text
Outcomes
• Most, not all, test data ready
• What’s not ready can be tested later
• Dependencies in place
• Good to move forward
Slide 59
Slide 59 text
Building
Slide 60
Slide 60 text
Let’s Build
Stuff!
Slide 61
Slide 61 text
Advantages of Dev/Tester Pairing:
• Immediate feedback
• Shared knowledge
• Cross pollination
• Great test coverage
Slide 62
Slide 62 text
Dev-Tester Collaboration Example
• “This use case isn’t clear!”
• “What about this edge case?”
• “Now I understand REST!”
Slide 63
Slide 63 text
Considerations
• What isn’t clear?
• Did we miss something?
• Tests in the right place
• Integration, Unit, JS in UI, functional
Slide 64
Slide 64 text
Outcomes
• Little or no overlap of tests
• New use cases discovered, resolved
• Added to test data
• BUILT AND SHIPPED WORKING STUFF!
Slide 65
Slide 65 text
UAT
Slide 66
Slide 66 text
Total focus on Quality
• No wasted effort
• UAT focuses only on gaps
• Earlier efforts pay off
Slide 67
Slide 67 text
Considerations
• Understanding of test coverage
• Ensure meets the need
• Delivers VALUE and solves problems
Slide 68
Slide 68 text
Outcomes
• Comfort in quality and value of system
• New ideas for more feature work
Slide 69
Slide 69 text
Ship it and
go home!
Slide 70
Slide 70 text
Wrapping
Up
Slide 71
Slide 71 text
Push conversations
EARLY
Slide 72
Slide 72 text
Answer
“Why are we building this?”
“What’s important to know?”