Some Observations from the Innovation Chasm
•Download as PPTX, PDF•
0 likes•672 views
From my experience, there is a large number of testers that belong to the ‘late majority’; a conservative crowd that is skeptical, out of touch with the latest developments and not eager to learn about them. There are several factors that keep these testers from becoming an ‘early majority’ or even ‘early adopters’. To discuss these factors I will introduce a model of the field of software testing in which the gaps between academia, thought leaders, the industry and the testing practitioners become visible.
Recommended
Recommended
More Related Content
Similar to Some Observations from the Innovation Chasm
Similar to Some Observations from the Innovation Chasm (20)
Recently uploaded
Recently uploaded (20)
Some Observations from the Innovation Chasm
- 1. Some Observations from the Some Observations from the Innovation Chasm Joris Meerts, 24 October 2014 Innovation Chasm Peers with Beers Joris Meerts, 24 October 2014
- 2. Some Observations from the Innovation Chasm Joris Meerts, 24 October 2014 about me • Joris Meerts • Software tester since 2007 • Capgemini • Context-driven school • www.testingreferences.com • Member of the Dutch Exploratory Workshop on Testing (DEWT) • @testingref
- 3. Some Observations from the Innovation Chasm Joris Meerts, 24 October 2014 technology adaption lifecycle
- 4. Some Observations from the Innovation Chasm Joris Meerts, 24 October 2014 testing innovation impacts • methods • models • practices • tools • standards • regulations
- 5. parties influencing the testing practitioner Some Observations from the Innovation Chasm Joris Meerts, 24 October 2014
- 6. academia • William Howden - Reliability of the Path Analysis Testing Strategy (1976) • Richard Hamlet - Theoretical Comparison of Testing Some Observations from the Innovation Chasm Joris Meerts, 24 October 2014 Methods (1989) • Elaine Weyuker - The Evaluation of Program-Based Software Test Data Adequacy Criteria (1988) • Lee J. White - A Domain Strategy for Computer Program Testing (1980) • Luc Bougé - Test sets generation from algebraic specifications using logic programming (1986) • Jefferson Offut - Criteria for Generating Specification-based Tests (1999)
- 7. academia • Richard A. Kemmerer - Testing Formal Specifications to Some Observations from the Innovation Chasm Joris Meerts, 24 October 2014 Detect Design Errors (1985) • Robert M. Hierons - Testing from a Z specification (1997) • John Goodenough, Susan Gerhart - Toward a Theory of Test Data Selection (1975) • Thomas J. Ostrand, Elaine Weyuker - Theories of program testing and the application to revealing subdomains (1980) • Jeremy Dick, Alain Faivre - Automating the Generation and Sequencing of test cases from model-based specifications (1993) • Deepinder Sidhu, Ting-Kau Lung - Formal Methods in Protocol Testing: a Detailed Study (1989)
- 8. Some Observations from the Innovation Chasm Joris Meerts, 24 October 2014 governing bodies • Over 1.000 testers signed the petition against ISO 29119. • The other 99% doesn’t even know we have standards. • Or couldn’t care less.
- 9. Some Observations from the Innovation Chasm Joris Meerts, 24 October 2014 thought leaders • Worked in testing for over 40 years. • Wrote several important books on testing. • Received Testing Excellence Award in 1999. • Dorothy who?
- 10. Some Observations from the Innovation Chasm Joris Meerts, 24 October 2014 independent study groups • E.g. peer workshops, meetups • Some are considered as ‘elitist’ • Often invitation only
- 11. Some Observations from the Innovation Chasm Joris Meerts, 24 October 2014 certifying bodies • Such as ISTQB, iSQI, TMap • Control education in software testing • As such have a large impact on testing • Just about as innovative as the dodo
- 12. Some Observations from the Innovation Chasm Joris Meerts, 24 October 2014 vendors • Such as Microsoft, HP, IBM, Atlassian • Pushing new products • Tool- & technology-driven innovation • ‘Gartner-style’ predictions
- 13. • Such as Sogeti, Atos, Ordina, CGI, Accenture and many others • Closest to the tester • Not hiring for innovation • Not willing to pay for innovation • Creating ‘islands’ of knowledge Some Observations from the Innovation Chasm Joris Meerts, 24 October 2014 service providers
- 14. (accommodating) innovation requires skills and tools • teaching / coaching / guidance • networks for the exchange of information • ability to challenge, experiment, persevere • ability to perceive, abstract • ability to tell compelling stories • different roles; researcher, critic, observer, reporter, chronicler Some Observations from the Innovation Chasm Joris Meerts, 24 October 2014
- 15. Some Observations from the Innovation Chasm Joris Meerts, 24 October 2014 thank you for listening joris.meerts@capgemini.com @testingref www.testingreferences.com
Editor's Notes
- The majority of the testers are in the late majority or are laggards. It seems that innovation in testing is unable to cross the chasm. In this presentation I will try to investigate why this is so.
- If there is innovation in testing we should be able to notice it in these aspects.
- These are the parties that influence the testing practitioner, along with the degree to which they influence the practitioner. Other parties may be identified, such as companies where testing is done in house.
- The academia do not influence the practitioner at all. Research and innovation may be going on in the universities and articles are published, such as the articles listed in these two slides. But it is not likely that the practitioner reads any of them. Furthermore the articles seem to describe a wholly different sort of software testing.
- It can be argued that standardization does not have a lot to do with innovation. Apart from that discussion it seems that the majority of testers is blissfully unaware of there being standards in our field.
- I met Dorothy Graham in 2010. I think she has made important contributions to our field. Yet when I tell the story about how I got in touch with her to the testers that I work with on a day-to-day basis, usually they do not seem to know who she is.
- It seems that most training courses provided by the certifying bodies are not striving for innovation.
- By ‘Gartner-style’ predictions I mean predictions that are made by combining of any popular technology (that would pop up in a report on trends in IT) with the word ‘testing’. Usually these predictions echo through the field without anyone actually trying to find out what ‘cloud testing’ or ‘mobile testing’ actually means to testing.
- By ‘islands’ of knowledge I mean that service providers do indeed try to build knowledge in specific areas of testing but have a hard time making that knowledge accessible to practitioners that either want to use it or contribute to it.
- Since service providers are closest to the tester they should try to accommodate innovation. It can be argued that service providers have no incentive to innovate because, for example, increased efficiency in testing actually means that there is less work and so less money to be earned. I think that competition among service providers means that service providers need to innovate in order to stay in the market, now perhaps more than ever.