Abstract/Description

Collective ownership for testing starts with understanding testing. Rework your team dynamics to evolve past duplication and improve performance through whole team testing. Take home practical patterns for improving your team's collaboration on testing. Because teams who own testing have more confidence in the customer value of their results.

As the Pragmatic Programmers say, "refactoring is an activity that needs to be undertaken slowly, deliberately, and carefully," so how do we begin?

In this session, we will experience the complex interactions of an agile team focused on demonstrating customer value by answering a series a questions:
Where do testers get their ideas?
How are you planning to accomplish this proposed testing, tester?
Why not automate all the things?
Who is going to do this manual testing and how does it work?
How do we know whether we're testing the right things?

Build your own list of TODOs from these various practical collaboration approaches and begin deduping your team's testing for a better first day back at the office.

Additional Resources

About the Speaker(s)

Agilist working as part of product development teams to support and accelerate development through fast feedback. I help teams to craft more executable user stories. Product backlog creator and groomer with emphasis on progressive elaboration. Front-end Javascript development, back-end development in Python or Node. Test automator using Newman, Protractor, Javascript, Selenium, or Python. Testing teacher, unit and integration test review and advisement, exploratory testing coach. Exploratory tester. Agile coach. ScrumMaster. Experience in programming, coaching, project management, product ownership, and technical writing. Community builder, meetup founder, conference organizer, speaker, workshop facilitator, author, podcaster, and blogger. Claire Moss has always had a passion for writing, which might be a strange trait for a discrete mathematician, but that doesn’t stop her from blogging or writing software articles. After working briefly as a software programmer and technical writer during college, Claire signed on as a quality engineer after graduation. By now, Claire has been delivering and testing software for 15 years. When you find your calling, you never look back! You might say she’s a compulsive empiricist when it comes to software. Claire continues to use her evil powers for good on the job and on her blog.