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.

Agile2015: Explore with Intent - Self-Management


Published on

Hands-on talk at Agile 2015 in Washington DC

Published in: Software
  • Be the first to comment

  • Be the first to like this

Agile2015: Explore with Intent - Self-Management

  1. 1. Explore with Intent - Exploratory Testing Self- Management Maaret Pyhäjärvi Email: <> | Twitter: maaretp
  2. 2. Testing as Performance (Exploring) vs. Testing as Artifact Creation
  3. 3. Explore with Intent Mission Charter Other Charters Details INTENT LEARNINGS
  4. 4. Notetaking “Same” tool Physical Notebook Rapid Reporter MindMup
  5. 5. Let’s Test
  6. 6. Observations!
  7. 7. An Example of Notes • Details published on my blog 06/2015 – while-testing-experiment-of-way-to.html • Use the tool that suites you best – Paper+pen  Mindmup as I taught myself to think with more structure
  8. 8. Learning about a Feature Getting Started
  9. 9. Learning about a Feature Setting up for Testing
  10. 10. Learning about a Feature Remembering Connections
  11. 11. Learning about a Feature Reading the Spec
  12. 12. Learning about a Feature Coming up with Connections
  13. 13. Learning about a Feature Focus to Actually Start
  14. 14. Learning about a Feature Software Talks
  15. 15. Observations from Learning about a Feature • I chose my focus – Specification first vs. Experiencing the feature first • Found and logged bugs – Jira, stopped and wrote a proper report that slowed me down • Ended up with open questions – Work done creates more work There’s no right / wrong focus
  16. 16. Exploratory Testing: Better tests, better testers! • An approach, not a technique • Find unknown unknowns • Disciplined • Test is a performance, not artifact – Artifacts support human memory – Many forms: e.g. checklists and automation • Exploratory performance testing, Exploratory test automation, Exploratory regression testing Test-related learning Design of new tests Test execution Result interpretation 16
  17. 17. Exploratory Testing: Frame of Management ”A day’s work” Vision (“Sandbox”) Current Charter Other Charters Details Bug Reports Perception of quality and coverage Quality ReportDebriefing Tester Test Manager Past Results Obstacles Outlook Feelings ? # xCharter backlog of the future testing Out of budget Next in importance! #, ?, x, + 20:20:60 Session sheets of the past testing Idea of exploration Metrics summary Coachin g 17 Playbooks Coverage outlines
  18. 18. Exploration Skills Source: Adapted from James Bach, Jon Bach, Michael Bolton. Exploratory Testing Dynamics. v.2.2. 2009 Self- managemen t Developing ideas Examining product Done To Do Issues Coverage All sources available Best use of time – effective and efficient work Making models Tool support – creative solutions Risk-based testing – scientific approach Keeping one’s eyes open 18
  19. 19. Question, Thoughts? Feedback?