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
Presentasjon til temakveld for Visma Consulting:Specification by example med Gojko Adzic
1. Agile approach to quality
Gojko Adzic
http://gojko.net
gojko@gojko.com
@gojkoadzic
2. Plan for today
● How teams often get stuck
● Three key techniques to improve
● How they help
● Adoption strategy
● Q&A
3.
4.
5.
6.
7.
8.
9.
10.
11. 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
13. Our job is not to
develop, test,
manage,
analyse....
14. Our job is to get
the right software
shipped faster
tomorrow than
today!
15. 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
17. Shorten feedback loops
● Decouple inspecting
different risk categories
● Automate so tests are fast
and maintainable
● Move from confidence to
evidence
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. Shorten feedback loops
● Decouple inspecting different risk categories
● Automate so tests are fast and maintainable
● Move from confidence to evidence
34. 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
36. Shorten feedback loops
● Decouple inspecting different risk
categories
● Automate so tests are fast and maintainable
● Move from confidence to evidence
39. 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
41. Shorten feedback loops
● Decouple inspecting different risk categories
● Automate so tests are fast and maintainable
● Move from confidence to evidence
42. Shorten feedback loops
● Decouple inspecting different risk categories
● Automate so tests are fast and maintainable
● Move from confidence to evidence
43. Adoption
● Get the entire team together
● Visualise the pipeline
● Choose your #1 problem
● Decide on solution together
● Treat it as an experiment
● Rinse & Repeat!