Agile QA 2.0

777 views

Published on

This is the talk that I gave at the 2013 Agile Central Europe Conference in Krakow, Poland, Apr. 15-16.

Published in: Technology, Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
777
On SlideShare
0
From Embeds
0
Number of Embeds
30
Actions
Shares
0
Downloads
24
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Agile QA 2.0

  1. 1. Agile QA 2.0@aceconf@mattphilip
  2. 2. Why this talk?1.  Agile QA 1.0 nevermade it past “staging”
  3. 3. Why this talk?1.  Agile QA 1.0 nevermade it past “staging”2.  Call-to-action toreinvigorate the stateof the practice
  4. 4. Why this talk?1.  Agile QA 1.0 nevermade it past “staging”2.  Call-to-action toreinvigorate the stateof the practice3.  Work together tocome upwith better ways
  5. 5. So what havewe learned?-- Barry Boehm (1981)
  6. 6. Eliminate the need for massiveinspection by building quality into theproduct in the first place.-- Edwards Deming (1982)So what havewe learned?”“
  7. 7. Handoffs are waste.-- Mary Poppendieck (2003)So what havewe learned?
  8. 8. Move testing to thefront of thedevelopment process-- Agile Testing (2009)So what havewe learned?”“
  9. 9. Kanban doesn’t mean a return towaterfall.-- David Anderson (paraphrase, 2013)So what havewe learned?
  10. 10. So of course what do our card walls look like?
  11. 11. How did this happen?We simply repeat the same processthat weve always doneQAs aren’t assertive enough to ask for changeWe figure that, if we don’t, the QAwont have anything to do (resourceefficiency)#1#2#3
  12. 12. But why is thisa problem?End-‐of-‐cycle testing (mini waterfalls)#1 Creates too long a feedback loop#2 Virtually ensures that our testing efforts aremisaligned with value #3 Reinforces gatekeeper role (oppositional)#4 Creates inefficient test suite
  13. 13. But why is thisa problem?Limitsoptions tocheckingthroughGUICreates inefficient test suiteWhichleads tothis
  14. 14. So how dowe remedythese problems?
  15. 15. Remedies Bring QA Forward#1 Bring QA forward* QA and devs collaborate to determine theright places to test
  16. 16. Remedies QA and devs collaborate to determine theright place to test#1 Bring QA forwardManyhereSomehereA fewhere
  17. 17. Remedies Bring QA Forward#1 Bring QA forward* QA and devs collaborate to determine theright places to test* Specify acceptance tests up-front(Acceptance-Test-Driven Development)
  18. 18. Remedies Acceptance-‐Test-‐Driven DevelopmentDevelopmentIterationsDevelopmentEngineWrite Story and ScenariosBusiness ShowcaseStory TestingStory Planning SessionBA / QA Signoff on Dev BoxDaily BA/QA demoTesterDevBATesterDevTester BADevTester BADevBABusinessTesterStartHereSystemTestingImplement FunctionalityBABusinessImplement AutomatedAcceptance TestsDevEnd Development IterationStart DevelopmentIteration#1 Bring QA forward
  19. 19. Remedies Bring QA Forward#1 Bring QA forward* QA and devs collaborate to determine theright places to test* Testing efforts are aligned with businessneeds and risk* Specify acceptance tests up-front(Acceptance-Test-Driven Development)
  20. 20. Remedies Re-‐start by mapping your done list to the wall#1 Bring QA forward#2 Map done list to the wall * Simple value-stream* Lets the team take a conscious role indefining its wall
  21. 21. Remedies Include QA in Work-‐In-‐Progress Limits#1 Bring QA forward#2 Map done list to the wall#3 Include QA in WIP limitsExpandthis…… toinclude this* Encourages whole-team approach
  22. 22. Where do our biggest handoffs occur?Here?Here?
  23. 23. Other considerations Quality AdvocacyQuality Advocacy* Consultative* Service provider* Enabling and informing (not gatekeeping)* Big picture-oriented* Polyskilled and skill sharer* Courageous
  24. 24. Other considerations Integrated QA:QA is nowhere – and everywhereQuality AdvocacyIntegrated QA * Remove Test/QA as a separate column altogether* QA provides real-time, zero-cycle-time feedback* Decouples what from who,decreases bottleneck* Commits devs and testerstoward same goal:working, tested software
  25. 25. So do we have a place forany kind of end-of-cycle testing?
  26. 26. Other considerations Exploratory Testing as First-‐Class PracticeQuality AdvocacyIntegrated QAExploratory testing* Not simply “clickin’ around” buthighly-skilled discipline* Anyone with the right skill, independence can do it* Model it on the wall
  27. 27. So what are yougoing to do starting Wednesday?
  28. 28. References§  Alister Scott, http://watirmelon.com/2013/02/28/the-new-qa-the-quality-advocate/§  Barry Boehm, Software Engineering Economics§  Martin Fowler, http://martinfowler.com/bliki/TestPyramid.html§  InfoQ, http://www.infoq.com/articles/David-Anderson-Kanban§  Deming Institute, http://deming.org/mphilip@thoughtworks.com@mattphilip

×