Skip to main content

Michael Bolton

DevelopSense

Tester, consultant, and trainer Michael Bolton is the coauthor (with James Bach) of Rapid Software Testing, a course that presents a methodology and mindset for testing software expertly in uncertain conditions and under extreme time pressure. A leader in the context-driven software testing movement, Michael has twenty years of experience testing, developing, managing, and writing about software. Currently, he leads DevelopSense, a Toronto-based consultancy. Prior to DevelopSense, he was with Quarterdeck Corporation, where he managed the company’s flagship products and directed project and testing teams—both in-house and worldwide. Contact Michael at [email protected].

Speaker Presentations
Monday, May 4, 2015 - 8:30am
Full-day Tutorials
A Rapid Introduction to Rapid Software Testing

You're under tight time pressure with barely enough information to proceed with testing. How do you test quickly and inexpensively, yet still produce informative, credible, and accountable results? Rapid Software Testing, adopted by context-driven testers worldwide, offers a field-proven answer to this all-too-common dilemma. In this one-day sampler of the approach, Michael Bolton introduces you to the skills and practice of Rapid Software Testing through stories, discussions, and “minds-on” exercises that simulate important aspects of real testing problems. The rapid approach isn't just testing with speed or a sense of urgency; it's mission-focused testing that eliminates unnecessary work, assures that the most important things get done, and constantly asks how testers can help speed up the successful completion of the project. Join Michael to learn how Rapid Testing focuses on both the mind set and skill set of the individual tester, using tight loops of exploration and critical thinking skills to help continuously re-optimize testing to match clients' needs and expectations.

Participants are strongly encouraged to bring a Windows-compatible computer to the class.

 

Tuesday, May 5, 2015 - 8:30am
Full-day Tutorials
Critical Thinking for Software Testers

Critical thinking is the kind of thinking that specifically looks for problems and mistakes. Regular people don't do a lot of it. However, if you want to be a great tester, you need to be a great critical thinker. Critically thinking testers save projects from dangerous assumptions and ultimately from disasters. The good news is that critical thinking is not just innate intelligence or a talent—it's a learnable and improvable skill you can master. Michael Bolton shares the specific techniques and heuristics of critical thinking and presents realistic testing puzzles that help you practice and increase your thinking skills. Critical thinking begins with just three questions—Huh? Really? and So?—that kick start your brain to analyze specifications, risks, causes, effects, project plans, and anything else that puzzles you. Join Michael for this interactive, hands-on session and practice your critical thinking skills. Study and analyze product behaviors and experience new ways to identify, isolate, and characterize bugs.

Participants are strongly encouraged to bring a Windows-compatible computer to the class.
 

Wednesday, May 6, 2015 - 11:30am
Agile Testing
The New Agile Testing Quadrants: Bringing Skilled Testers and Developers Together

You want to integrate skilled testing and development work. But how do you accomplish this without developers accidentally subverting the testing process or testers becoming an obstruction? Efficient, deep testing requires “critical distance” from the development process, commitment and planning to build a testable product, dedication to uncovering the truth, responsiveness among team members, and often a skill set that developers alone—or testers alone—do not ordinarily possess. James Bach and Michael Bolton present a model which is a redesign of the famous Agile Testing Quadrants that distinguished business vs. technical facing tests and supporting vs. critiquing. Their new model frames these dynamics and helps teams think through the nature of development and testing roles and how they might blend, conflict, or support each other on an agile project. James and Michael include a brief discussion of the original Agile Testing Quadrants model, which the presenters believe has created much confusion about the role of testing in agile.