Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Placebo test management

75 views

Published on

A presentation about the need of a test plan in Agile environments.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Placebo test management

  1. 1. The Master Test Plan
  2. 2. Why do people want test plans?
  3. 3. Test Management Eddy Bruin How to please management about how testing is done Ray Oei
  4. 4. Impressive looking index. Follow all ‘conventions’.
  5. 5. Put in nonsense to check if someone actually read it
  6. 6. Why do you not want a test plan?
  7. 7. What do you want to communicate about your testing?
  8. 8. The Agile manifesto Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
  9. 9. The 7Basic Principles of the Context-Driven School 1.The value of any practice depends on its context. 2.There are good practices in context, but there are no best practices. 3.People, working together, are the most important part of any project’s context. 4.Projects unfold over time in ways that are often not predictable. 5.The product is a solution. If the problem isn’t solved, the product doesn’t work. 6.Good software testing is a challenging intellectual process. 7.Only through judgment and skill, exercised cooperatively throughout the entire project, are we able to do the right things at the right times to effectively test our products.
  10. 10. Test management Treatments Placebo Fake, but it will please (temporaraly) Trojan Horse Virus A cure in disguise Antibiotics A complete treatment
  11. 11. Utilize agile ‘standard’ practices
  12. 12. Utilize agile ‘standard’ practices
  13. 13. TMap style testplan with CDT/RST/HTSM content
  14. 14. TMap style testplan with CDT/RST/HTSM content
  15. 15. Talk the old language, do something new
  16. 16. Talk the old language, do something new Chance of failure Impactoffailure
  17. 17. Some principles • Let the team own the test management • Quality assistance • Have a lightweight test framework • Communicate the framework to teams and stakeholders • Show them the options, let the teams choose • Show transparency and show results • Scientific method http://www.slideshare.net/adorepump/im-an-agile-test-managerdo-i-really-exist-presentation
  18. 18. Session Based Test Management Be Transparent
  19. 19. Session Based Test Management Be Transparent •Make stakeholders aware they influence quality •Test sessions (SBTM) •Smiley board on quality of features •Involve more people in testing •Bug hunts •User sessions •Tell the test story
  20. 20. Slack management
  21. 21. Example of change
  22. 22. Test management overview Features All acceptance criteria checked (or not!) Epics Links to documentation Notes Warning! Open issues
  23. 23. Some practices • Mindmaps • Slack management • Test ideas • Risk analyses • Nightmare headline game • Product risk analyses • Create a learning culture • Walk in sessions • Gather tester and let them present what they did and want to do • Session Based Test Management • Be transparent
  24. 24. Hey, we just met you And this is crazy So here’s our twitter So tweet us maybe?! @eddybruin Big thanks to … You! eddy@loopforward.nl ray.oei@avg.com @rayoei

×