Successfully reported this slideshow.

Agile2015: Explore with Intent - Self-Management

0

Share

Loading in …3
×
1 of 19
1 of 19

More Related Content

Related Books

Free with a 14 day trial from Scribd

See all

Related Audiobooks

Free with a 14 day trial from Scribd

See all

Agile2015: Explore with Intent - Self-Management

  1. 1. Explore with Intent - Exploratory Testing Self- Management Maaret Pyhäjärvi Email: <maaret@iki.fi> | 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 – http://visible-quality.blogspot.fi/2015/06/blog- 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?

Editor's Notes

  • I’m Maaret and I am a tester. This morning someone on twitter labeled me as Chix0r. To me that label is kind of important because I’ve spent 20 years trying out ideas on how get great at being a tester. It probably has a meaning to you too, and yours might be different than mine. I advice people to go see a great lady, Keila Banks do her 15 minute keynote at Oscon this year. Oh, btw, she is 13 and already she knows labels should belong to _you yourself_.

    Are there testers in the room? Testing is too important to be left just for testers.
    We testers don’t break software, we break illusions about the software and this talk works on your illusions about deep testing you think can be automated.

    Agile is the best thing that has happened to me. But testing is still testing and agile a context. I’m still a people person. I was never in a silo, I was never obedient, never without power.

    Me: CD without automation. 1 to 9 ratio of mutual love and respect “We may not agree but we can still treat each other with kindness and respect”. I do not code (as a general rule) but for the best of my team, I will work in a mob. Serendipity and perseverance. Me holding space. Deep testing requiring skill.

    Insights into automation, finding out that secondary key was a shortcut, automating a check on all keyboards.



    TIMINGS:
    75 minutes
    -> 15 minutes into introducing the idea
    -> 45 minutes into exercise: 30 for mob, 15 for observations
    -> 15 minutes into example and closing
    ----- Meeting Notes (04/08/15 11:04) -----
    label
    are you tester? too important
    agile is context
    my work: 1:9 CD w/O automation, love&respect, deep testing
  • Need 3-4 volunteers + an empty seat for anyone to join in (then someone else will leave)
    4 minute rotation
    Observations from the audience
  • Talk about the experience.
  • 5 years of experience –point.
  • ×