Rapid Software Testing

A Context-Driven Methodology

You are here: Home / Events / Online: Rapid Software Testing Applied with James Bach

by on

Online: Rapid Software Testing Applied with James Bach

Location: Online (North American Time Zones)
Date: Jun 6, 2021 to Jun 8, 2021

This online seminar applies Rapid Software Testing Methodology to testing a specific product.

Course description of Rapid Software Testing Applied

The class consists of ten webinars and four work assignments. All student work, videos, and class materials are provided to students when the class is complete. We use a MatterMost chatroom server for communication, a TikiWiki server to share classwork, and Zoom for the presentations. This is not a passive lecture experience.

There is a lecture in the morning and afternoon, during which you will interact with James and peer advisors in the chatroom. Each day there is a 90 minute homework assignment which is integral to the class experience, followed by an hour-long webinar where James reviews selected student work and bug reports.

Note that the second day has a different schedule and includes four webinars. So, the overall agenda looks like this:

      
DAY 1 (All times in Pacific Time)
9:00am-10:30am Webinar
10:30am-12:30pm Student Work Assignment
12:30pm-1:30pm Webinar
1:30pm-2:00pm Break
2:00pm-3:00pm Webinar

DAY 2
9:00am-9:30am Webinar
9:30am-10:30am Student Work Assignment
10:30am-11:30am Webinar
11:30am-1:30pm Student Work Assignment
1:30pm-3:00pm Webinar
3:00pm-3:30pm Break
3:30pm-4:30pm Webinar


DAY 3
9:00am-10:30am Webinar
10:30am-12:30pm Student Work Assignment
12:30pm-1:30pm Webinar
1:30pm-2:00pm Break
2:00pm-3:30pm Webinar

The registration price is $500.

REGISTER HERE before the course fills up!

Contact Erica to be placed on the waiting list for next course.

About James Bach

I started in this business as a programmer. I like programming. But I find the problems of software quality analysis and improvement more interesting than those of software production. For me, there's something very compelling about the question "How do I know my work is good?" Indeed, how do I know anything is good? What does good mean? That's why I got into SQA, in 1987.
Today, I work with project teams and individual engineers to help them plan SQA, change control, and testing processes that allow them to understand and control the risks of product failure. I also assist in product risk analysis, test design, and in the design and implementation of computer-supported testing. Most of my experience is with market-driven Silicon Valley software companies like Apple Computer and Borland, so the techniques I've gathered and developed are designed for use under conditions of compressed schedules, high rates of change, component-based technology and poor specification.