Upload
atlassian
View
479
Download
4
Embed Size (px)
DESCRIPTION
How can a team of 65 developers build and rapidly ship a high-quality product with only six QA engineers? At Atlassian, we’ve introduced the Quality Assistance model that changes the developer QA mindset, and engages developers in exploratory testing so software is developed right the first time. After all, the cheapest time to fix a bug is before it's written. Join us as we walk through the theory, history, and practice of the model, while busting some of the myths about developers and QA. Reject the tradeoff of time, scope, and quality, and finally have your cake and eat it too.
Citation preview
#atlassian
NOTES:
• Your main title goes in the large blue
font.
• If you have a title that naturally splits
into a subtitle, use the smaller green font
for the subtitle. If not, delete the subtitle
PHOTO
1. Place your photo at around the same
size as the example photo
2. (Keynote users:) Move your photo
onto the blue shape below Select both
photo and shape and then choose
“Mask with selected shape” from the
menu. Double click the photo to edit the
scale and crop position.
PENNY WYATT • SENIOR QA TEAM LEAD • ATLASSIAN • @pennozewyatt
Quality at Speed
More QA ≠ More Quality"
More QA ≠ More Quality"
Today’s Topics"
• Why? • Quality at Speed
• How? • Quality Assistance
NOTES:
• If you want to divide your talk
into chapters, use this slide for
Chapter titles
Quality at Speed
Speed
Scope Quality
Waterfall"
Development
Time Release
Bugfix
Testing
Development
Time
Release
Bugfix
Testing
Waterfall"
Development / Bugfix
Time
Release
Testing
Agile"
Development
Time
Release
Testing
Agile"
Bugfix
Development
Time
Release
Testing
Agile"
Bugfix
Rejecting the Tradeoff"
• Build it, test it, fix it, ship it • Why are devs and testers different people?
Development
Time
Release
If Devs Could Test"
“But Devs Can’t Test!”"
• Testing is a skill and a mindset • Many devs have neither • Many of them think they have both!
“But Devs Can’t Test!”"
The Enemy Within"
Half an Engineer"
Missing: Quality Mindset"
Users would never do that!
Edge case!
We can fix that later... maybe
The spec didn’t mention that.
Missing: Testing Skills"
Automation solves
everything.
Manual testing is obsolete
Works on my machine.
My part works fine.
Missing: Knowledge"
That’s configurable?
I’m not a security expert
I only learn from my own mistakes
All databases behave the same way
Development
Testing
Side-by-Side"
Bugfix
Time
Release
Is there hope?"
Development
Time
Release
Reintegrated"
NOTES:
• If you want to divide your talk
into chapters, use this slide for
Chapter titles
Quality Assistance
Quality Assistance"
• Short-term – Protect our customers • Long-term – Educate our developers
Skeptical?"
Measuring Progress"
100%
30%
15%
7% 4%
0%
20%
40%
60%
80%
100%
2009 2011 2012 2013 2014
Story Rejection Rate
Shifting a Culture"
Stage 0 of 6 – No QA"
• Automation only • Functional correctness
Coding Done
Stage 1 of 6 – QA Testing"
• QA does exploratory testing
Coding Done Testing
Stage 2 of 6 – DoTing"
• DoT = Developer On Test • Devs test each other’s stories
Coding Testing
DoTing Done
Release Testing
Stage 3 of 6 –Demos and Notes"
• DoTs test all stories • QA demo once story is done • QA writes testing notes
Coding DoTing Done Demo
Stage 4 of 6 – QA Kickoffs"
• Prevention > Detection • QA kickoff before story is started
Coding DoTing Done Demo Kickoff
Review
Stage 5 of 6 – Private Kickoffs"
• Devs do their own kickoffs • QA reviews testing notes
Coding DoTing Done Demo Kickoff
Review
Stage 6 of 6 – No More DoTing"
• DoTing creates bugs! • Still unofficial safety nets
Coding/ Testing
Done Demo Kickoff
Review
Current Process"
• All testing done by devs • Two QA input points on each story
Done Demo Kickoff Coding/ Testing
NOTES:
• Use Chrome browser
• 1 tab open, unless tabs help
illustrate
• Browser extensions & bookmarks
bar is hidden
• Screenshot fills entire screen
• You can download the “Window
Resizer” Chrome extension to set
your window at 1280x1024 so that it
fills this aspect ratio
Reintegration"
Reintegration"
NOTES:
• If you have short reminders or
highlights that you want people to
tweet, use this. • Software quality comes from people, not code. • Improvement comes from questioning
assumptions. • Constantly experiment. • Have fun!
Key takeaways: #atlassian
Thank you!
PENNY WYATT • SENIOR QA TEAM LEAD • ATLASSIAN • @pennozewyatt