Agile approach to quality                  Gojko Adzic               http://gojko.net            gojko@gojko.com          ...
Plan for today●   How teams often get stuck●   Three key techniques to improve●   How they help●   Adoption strategy●   Q&A
Real problems● slow feedback● huge amount of time wasted● low visibility of stuff coming through  the pipeline● lack of sh...
Unpicking water-scrum-fall● optimise the whole  pipeline● remove information  bottlenecks● shorten feedback loops
Our job is not todevelop, test,manage,analyse....
Our job is to getthe right software  shipped faster  tomorrow than      today!
Optimise the whole pipeline●   Push work away from bottlenecks●   Kill scope creep●   Kill the telephone game●   Focus on ...
Remove information bottlenecks● Teach / share domain  knowledge● Build and publish relevant  documentation● Visualise risk
Shorten feedback loops● Decouple inspecting  different risk categories● Automate so tests are fast  and maintainable● Move...
Benefits?● Shorter time to market –  often by 3 or 4 times● Much higher levels of  quality
Three key techniques
Impact Mapping
Impact Mapping
Optimise the whole pipeline●   Push work away from bottlenecks●   Kill scope creep●   Kill the telephone game●   Focus on ...
Shorten feedback loops●   Decouple inspecting different risk categories●   Automate so tests are fast and maintainable●   ...
Collaborate on specifications
Illustrate requirements using           examples
Refine into specifications
Automate without changing
= Executable specifications
From “Agile Testing” Crispin/Gregory
Ports & adaptersFrom “Growing Object Oriented Software” Pryce/Freeman
Optimise the whole pipeline●   Push work away from bottlenecks●   Kill scope creep●   Kill the telephone game●   Focus on ...
Remove information bottlenecks●   Teach / share domain knowledge●   Build and publish relevant documentation●   Visualise ...
Shorten feedback loops●   Decouple inspecting different risk    categories●   Automate so tests are fast and maintainable●...
ACC Matrix
ACC Matrixhttp://bit.ly/accMatrix
Optimise the whole pipeline●   Push work away from bottlenecks●   Kill scope creep●   Kill the telephone game●   Focus on ...
Remove information bottlenecks●   Teach / share domain knowledge●   Build and publish relevant documentation●   Visualise ...
Shorten feedback loops●   Decouple inspecting different risk categories●   Automate so tests are fast and maintainable●   ...
Shorten feedback loops●   Decouple inspecting different risk categories●   Automate so tests are fast and maintainable●   ...
Adoption●   Get the entire team together●   Visualise the pipeline●   Choose your #1 problem●   Decide on solution togethe...
Presentasjon til temakveld for Visma Consulting:Specification by example med Gojko Adzic
Presentasjon til temakveld for Visma Consulting:Specification by example med Gojko Adzic
Presentasjon til temakveld for Visma Consulting:Specification by example med Gojko Adzic
Presentasjon til temakveld for Visma Consulting:Specification by example med Gojko Adzic
Presentasjon til temakveld for Visma Consulting:Specification by example med Gojko Adzic
Presentasjon til temakveld for Visma Consulting:Specification by example med Gojko Adzic
Presentasjon til temakveld for Visma Consulting:Specification by example med Gojko Adzic
Presentasjon til temakveld for Visma Consulting:Specification by example med Gojko Adzic
Presentasjon til temakveld for Visma Consulting:Specification by example med Gojko Adzic
Presentasjon til temakveld for Visma Consulting:Specification by example med Gojko Adzic
Presentasjon til temakveld for Visma Consulting:Specification by example med Gojko Adzic
Presentasjon til temakveld for Visma Consulting:Specification by example med Gojko Adzic
Presentasjon til temakveld for Visma Consulting:Specification by example med Gojko Adzic
Upcoming SlideShare
Loading in …5
×

Presentasjon til temakveld for Visma Consulting:Specification by example med Gojko Adzic

363 views
311 views

Published on

Presentasjon til temakveld for Visma Consulting.
Om temaet:
Specification by example er relevant for testere, arkitekter og utviklere. Det handler om å unngå funksjonelle gap og inkonsistens mellom spesifikasjoner og tester. Ved å utvide spesifikasjoner med eksempler lager man en ”single source of truth” for både utvikling og test, og ved å automatisere spesifikasjonene muliggjør man automatisert akseptansetestin

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
363
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Presentasjon til temakveld for Visma Consulting:Specification by example med Gojko Adzic

  1. 1. Agile approach to quality Gojko Adzic http://gojko.net gojko@gojko.com @gojkoadzic
  2. 2. Plan for today● How teams often get stuck● Three key techniques to improve● How they help● Adoption strategy● Q&A
  3. 3. Real problems● slow feedback● huge amount of time wasted● low visibility of stuff coming through the pipeline● lack of shared understanding● different risk checks are tightly coupled
  4. 4. Unpicking water-scrum-fall● optimise the whole pipeline● remove information bottlenecks● shorten feedback loops
  5. 5. Our job is not todevelop, test,manage,analyse....
  6. 6. Our job is to getthe right software shipped faster tomorrow than today!
  7. 7. Optimise the whole pipeline● Push work away from bottlenecks● Kill scope creep● Kill the telephone game● Focus on valuable work ● Get a shared understanding of risk ● Get a shared definition of quality ● Kill synchronisation work, several sources of truth ● Drop software that did not succeed
  8. 8. Remove information bottlenecks● Teach / share domain knowledge● Build and publish relevant documentation● Visualise risk
  9. 9. Shorten feedback loops● Decouple inspecting different risk categories● Automate so tests are fast and maintainable● Move from confidence to evidence
  10. 10. Benefits?● Shorter time to market – often by 3 or 4 times● Much higher levels of quality
  11. 11. Three key techniques
  12. 12. Impact Mapping
  13. 13. Impact Mapping
  14. 14. Optimise the whole pipeline● Push work away from bottlenecks● Kill scope creep● Kill the telephone game● Focus on valuable work ● Get a shared understanding of risk ● Get a shared definition of quality ● Kill synchronisation work, several sources of truth ● Drop software that did not succeed
  15. 15. Shorten feedback loops● Decouple inspecting different risk categories● Automate so tests are fast and maintainable● Move from confidence to evidence
  16. 16. Collaborate on specifications
  17. 17. Illustrate requirements using examples
  18. 18. Refine into specifications
  19. 19. Automate without changing
  20. 20. = Executable specifications
  21. 21. From “Agile Testing” Crispin/Gregory
  22. 22. Ports & adaptersFrom “Growing Object Oriented Software” Pryce/Freeman
  23. 23. Optimise the whole pipeline● Push work away from bottlenecks● Kill scope creep● Kill the telephone game● Focus on valuable work ● Get a shared understanding of risk ● Get a shared definition of quality ● Kill synchronisation work, several sources of truth ● Drop software that did not succeed
  24. 24. Remove information bottlenecks● Teach / share domain knowledge● Build and publish relevant documentation● Visualise risk
  25. 25. Shorten feedback loops● Decouple inspecting different risk categories● Automate so tests are fast and maintainable● Move from confidence to evidence
  26. 26. ACC Matrix
  27. 27. ACC Matrixhttp://bit.ly/accMatrix
  28. 28. Optimise the whole pipeline● Push work away from bottlenecks● Kill scope creep● Kill the telephone game● Focus on valuable work ● Get a shared understanding of risk ● Get a shared definition of quality ● Kill synchronisation work, several sources of truth ● Drop software that did not succeed
  29. 29. Remove information bottlenecks● Teach / share domain knowledge● Build and publish relevant documentation● Visualise risk
  30. 30. Shorten feedback loops● Decouple inspecting different risk categories● Automate so tests are fast and maintainable● Move from confidence to evidence
  31. 31. Shorten feedback loops● Decouple inspecting different risk categories● Automate so tests are fast and maintainable● Move from confidence to evidence
  32. 32. Adoption● Get the entire team together● Visualise the pipeline● Choose your #1 problem● Decide on solution together● Treat it as an experiment● Rinse & Repeat!

×