Past Presentations
You can find an extensive list of presentations and courses that I've taught, including the slides and speaker notes for many of them, here.
Let's meet!
Highlights from my schedule appear below. If you notice that I'm in your part of the world, drop me a line if you'd like to get together. If you'd like to engage my services and worry that I'm not available, please note that my clients' schedules are subject to change, so mine is too. Please drop me a line in any case.
January 3-6, 2012
Calgary, Alberta, Canada
Rapid Software Testing class (three days) with an extra free day for which the client chooses the agenda.
January 9-10, 2012
Toronto, Ontario, Canada
Rapid Testing training and consulting in Rapid Testing with a corporate client.
January 16-18, 2012
Helsinki, Finland
Rapid Software Testing: a three-day public class, organized by Altom. Information is here; registration here.
January 27-29, 2012
Melbourne, Florida
Workshop on Teaching Software Testing
January 30-February 3, 2012
Palm Bay, Florida
Writing work with Cem Kaner and Becky Fiedler.
February 13-17, 2012
Orcas Island, Washington
In-person development work on the Rapid Software Testing class with James Bach.
March 8-14, 2012
Utrecht, Netherlands
Pencilled-in engagement teaching Rapid and exploratory approaches with a corporate client.
March 15-16, 2012
Munich, Germany
Two days of presentation and particpation in an in-house testing conference for a corporate client.
March 26, 2012
Halifax, Nova Scotia, Canada
A three-day Rapid Testing class, with a free fourth day based on the client's agenda.
April 10-12, 2012
Oslo, Norway
A public offering of Rapid Software Testing.
April 13, 2012
Oslo, Norway
Work for a corporate client.
April 16-19, 2012
Orlando, Florida
A tutorial and a keynote at the STAR East conference.
April 25
Toronto, Ontario, Canada
Corporate in-house training and consulting.
April 30-May 2, 2012
London, UK
Rapid Software Testing public class organized by Electromind.
May 3-4, 2012
London, UK
The UK's first public offering of Rapid Software Test Management, again organized by Electromind.
May 7, 2012
Stockholm, Sweden
I'll be presenting the first keynote and a half-day tutorial at the inaugural Let's Test Conference in Sweden. Alas, I'll only be able to stay the first day of the conference, which runs from May 7 through May 9, 2012.
May 8-11, 2012
Trondheiim & Brønnøysund, Norway
The Norwegian Testing Cruise. So far as we know, this will be the the first boat-based and northernmost testing conference in history.
May 21-23
Utrecht, The Netherlands
A public course Rapid Software Testing class in the Netherlands.
May 24-25
Utrecht, The Netherlands
A public class of Rapid Software Testing for Managers.
June 12-14
Cary, NC
Private training and consulting in Rapid Software Testing for a corporate client.
June 25-29, 2012
Atlanta, Georgia, USA
Private training and consulting in Rapid Software Testing for a corporate client.
July 10-12, 2012
Cary, NC
Private training and consulting in Rapid Software Testing for a corporate client.
July 16-18, 2012
San José, California, USA
Participating in the CAST conference.
September 10-12, 2012
London, UK
A public class of Rapid Software Testing, organized by ElectroMind.
when we hear another common software development question: “Why did it take you so long to find that bug?”
>> I have seen testers some ocasions being asked — A typical PM question
“Why did you miss that bug” – it was so obvious?”
I have also seen people making references to that fact that tester missed the bug because there was not test case related to that bug – meaning requirement traceability was incomplete. A few enlightened souls go the the extent of saying – “requirements were vague and confusing AND there was no test case too hence (poor) tester missed the bug”
Michael – it will be great if you can write about “Missed bugs from test” and reactions of “non tester” community about this
Shrini
Last week a tester who reports to me said, “No user who has common sense would do that” when I showed her a bug that I found while testing. The reason why I was shocked is, I had shown her a crash of the application!
I had to say, “No user who in your opinion lack common sense and yet pays for the testing you do, matter ,and hence we need to take this into consideration”
I am not sure if that convinced her but what *might* have convinced her is, “You must understand that there are many people like your manager who might lack common sense but are paying you for the work you do and want to pay you more if you could spot such no-common sense resultant bugs”
I think that’s working!
Comments such as “No user would do that” are seen leading to some kind of rupture among developers and testers and once such differences creep up,lot of time is lost filling the gaps between them.
I beleive total isolation of testers and developers from each other will help solving such situations. Keeping aside whether an enduser would ever do that or not,its more important to curtail such arguments/comments (though there could be some situations which a developer might be able to Justify),I have seen that only ONE point of contact between developers and testers will allow for better and effective moderation.