Getting business people and developers to listen to testers

979 views

Published on

Presentation given at the 23rd UK Test Management forum on Wednesday 29th July 2009 about communication problems on software teams and specification workshops from a testing perspective.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
979
On SlideShare
0
From Embeds
0
Number of Embeds
208
Actions
Shares
0
Downloads
25
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Getting business people and developers to listen to testers

  1. 1. Getting business people and developers to listen to testers Gojko Adzic http://gojko.net gojko@gojko.net @gojkoadzic
  2. 2. http://www.flickr.com/photos/jcodysimms/246023851 /
  3. 3. Problems  Developers invading into testing → loss of control  Lack of documentation, so people don't know what to test → no effect  Very little influence → no respect  People feel pushed out → no job satisfaction  No clear definition of work → confusion, fear
  4. 4. http://www.flickr.com/photos/mulesafpilot/3513588967
  5. 5. http://www.flickr.com/photos/lambdachialpha/157986473
  6. 6. An experiment with four active battalions in US Army Commander expectations matched actions in only 34% of the cases L.G.Shattuck, 2000 http://www.au.af.mil/au/awc/awcgate/milreview/shattuck.pdf
  7. 7. The process is very much like a telephone game http://www.flickr.com/photos/mataniere/3107073262
  8. 8. B2 bomber crashed and $2bn went up in flames "the aircraft actually performed as it was designed. In other words, all the systems were functioning normally." Maj. Gen. Floyd L. Carpenter http://www.foxnews.com/wires/2008Jun05/0,4670,B2Crash,00.html
  9. 9. You can't help a lot when the party is already over... http://www.flickr.com/photos/biolog/3457774800
  10. 10. Problems  Developers invading into testing → loss of control  Lack of documentation, so people don't know what to test → no effect  Very little influence → no respect  People feel pushed out → no job satisfaction  No clear definition of work → confusion, fear
  11. 11. Problems Symptoms  Developers invading into testing → loss of control  Lack of documentation, so people don't know what to test → no effect  Very little influence → no respect  People feel pushed out → no job satisfaction  No clear definition of work → confusion, fear
  12. 12. Problems  Testing is decoupled from development, happens on the end  Lack of communication between business, developers and testers  Animosity between developers and testers
  13. 13. Specification workshops  Everyone in the same room to discuss and agree on what should be done  Iron out inconsistencies and gaps  Warn, suggest, discuss, convince  Communicate intent  Learn!
  14. 14. Solutions for problems  Workshops promote communication between business, developers and testers  Testers can influence the specifications same as anyone else  Everyone learns first-hand what the specification is so people know what to develop and test  People start understanding what testers do and respect it
  15. 15. • www.gojko.net • www.acceptancetesting.info • www.agiletesting.org.uk (from tomorrow)

×