Rapid Software Testing for Managers - NEW
A course about a mission-focused, credible, and accountable
approach to test management that is very fast, very inexpensive,
and that delivers excellent results.
- A new test manager?
- An experienced test manager, being pressured to make testing faster and less expensive?
- Finding that traditional, "best-practice" approaches to testing are making testing slower and more expensive than your clients demand?
- Being asked to manage a test group for an organisation that's moving to Scrum or other Agile methodologies?
- A project manager with responsibility for managing or directing an offshore oursource testing group?
- Managing an offshore or outsource testing group, and trying to provide the best value for your clients?
- Struggling with measuring and managing the performance of your test team?
- Finding it difficult to report the status of testing on your project?
- Having trouble setting the right balance between planning, documentation, and testing?
- Trying to figure out how to recruit, select, or train a skilled and diversified test team?
- Want to get very good at managing the software testing effort?
Rapid Software Testing for Managers is designed to help you solve these problems. Based on the Rapid Software Testing course and methodology, and on the practices developed by James Bach, Dr. Cem Kaner, and Michael Bolton, this class answers key questions about how to staff, plan, and run testing projects more quickly, less expensively, and entirely accountably.
The skills presented in this class are applicable in any kind of test project, from agile to traditional, but will be especially valuable in those projects where time and resources are scarce.
How Is This Course Different?
Rapid Software Testing for Managers is a one- or two-day class, available for individuals or small groups, in which we will explore test management, your organisation's context and how to respond to it. We'll do the work through experiential exercises, puzzles, and scenarios, along with short presentations, conversation, and some actual testing and reporting. The goal of the course is to teach you how to respond with the management action appropriate to your context while recognizing the near-universal situation: testing is almost always done under extreme time pressure and conditions of uncertainty.
While the target audience for this course is primarily test managers and test leads, we welcome peers of test managers such as development managers and project or program managers, and higher managers interested in testing.
What Will I Learn?
Whether you're experienced or new to test management, we'll explore the challenges of the role and how to work around them i.e.
- Plan and prepare a test project when product information is incomplete or unreliable
- Estimate and negotiate for the resources you need
- Design and defend a rapid, risk-based test strategy
- Plan incrementally and apply exploratory testing approaches
- Establish a productive relationship with programmers
- Be an effective advocate for testability, testing, and quality
- Supervise testers and be accountable for their work
- Create a diversified team and guide its members toward building skill
- Report project status to indicate progress and prompt the right questions
The course is designed to be modular, responding to the issues you're facing in your organisational context. Classes are typically structured as follows:
Rapid Testing Basics
- Project realities that necessitate rapid testing
- The rapid testing mindset
- Thinking like a tester and thinking like a test manager
- Using heuristics to guide testing
- Using risk to focus testing
- Exploratory vs. scripted testing
Evolving a Test Plan
- Using the Context Model to analyze a test situation
- Negotiating the mission, process, and resources
- Analyzing risk with heuristics
- Test cycle dynamics
- Testing throughout the lifecyle
- Managing testers every day
Key Challenges in Rapid Test Management
- Accountability: how an exploratory approach is accountable
- Repeatability: nine reasons to repeat, one big reason not to repeat
- Documentation: concise documentation is more rapid
- Status: using a dashboard
- Staffing: recruiting and developing rapid testers
- Automation: an agile and diversified approach
- Developer Relations: how to be the good guy, not the bad guy
- Metrics: the value of inquiry metrics; the dangers of control metrics
- Estimation: how to deal with an understandable request to predict the future.
- Enoughness: how you know when you've done enough testing and have enough quality
- Outsourcing: how to work in environments where you are offering or obtaining outsourced testing services
What is Rapid Software Testing (see also below)?!
Rapid Software Testing is a complete methodology designed for a world of barely sufficient resources, information and time. It's an approach to testing that begins with developing personal skills and extends to the ultimate mission of software testing: lighting the way of the project by evaluating the product. The approach is consistent with and a follow-on to many of the concepts and principles introduced in the book "Lessons Learned in Software Testing: a Context-Driven Approach" by Kaner, Bach, and Pettichord.
The rapid approach isn't just testing with a speed or sense of urgency; it's mission-focused testing that eliminates unnecessary work, assures that everything necessary gets done and constantly asks what testing can do to help speed the project as a whole.
- One important tool of rapid testing is the discipline of exploratory testing—essentially a testing martial art. Exploratory testing combines test design, test execution, test result interpretation and learning into a simultaneous, seamless process that finds a lot of problems quickly. Read more about exploratory testing here.
- September 27th to 28th 2012: Two full days (lunch and refreshments are included).
- Professional training venue (up to 24 participants)
- Ballerup, Copenhagen (DEN).
Related training - You might be interested in joining PGT and Michael Bolton at:
- Michael Bolton.
- Preférable prefaced by Rapid Software Testing.
- Training and materials will be in English.
- 7.800 DKK - Early Bird - until July 1st 2012 (or until sold out)
- 8.600 DKK - Nominal.
- Click on 'Registration' (above) or
- Send an email to Training@PGT.dk or
- Call us on (+45) 31 63 02 00.
About Rapid Software Testing
What People Are Saying About Rapid Software Testing
Many thanks to my clients who are willing to share their experiences. For understandable reasons, some of them have asked that I use discretion in identifying them.
"The Rapid Software Testing course that I attended in June definitely surpassed my expectations. As an experienced tester I was becoming rather disillusioned of the so called "Tried and True" methods of software testing and was really looking for something that resembled, well, reality. So now, instead of spending my time writing test cases, writing reports that no one reads and chasing down Product Specs and Feature Specs I test. What an amazing concept—have the tester do testing! It has freed up an enormous amount of time and, therefore, the testing is far more productive. Potential "show stoppers" are being found earlier on in the test schedule and test coverage has also improved greatly. More time is spent on important matters and less time trying to hit a number target (i.e. 90% testing complete, 95% pass rate, etc.). The focus has returned to the task at hand (testing) and there is less focus on reporting (counting). That also allows for the tester to move into a more co-development role to assist with the implementation of new features and functionality. I'm happy, the Devs are happy, the customer is happy and the boss is happy—Thanks Michael!"
Blair Burke, B.Sc., Software Tester, Print Audit, Inc. - September, 2010
"Recently I finished a three day training course on Rapid Software Testing with Michael Bolton in London UK. This course was very effective and had elements related to learning, questioning and thinking all along. It reinforced my belief that testing is not a 'phase' performed towards the end or a '100% automated suite' as claimed by many Agile shops. Software testing is much more than that and it is extremely important for the successful delivery of any project... Overall this training and all the discussions we had during the course was an amazing experience. I would highly recommend this training to anyone interested in learning rapid software testing." More...
Anand Ramdeo, London, UK
"You'll be happy to know that my team has been actively meeting to implement changes for improvement, especially with the dashboard concept and that many of my folks are more engaged with their assignments because of their new outlook on the value they can add."
Leslie Berth, Milwaukee, WI
"Last week I took Rapid Software Testing from Michael Bolton. The three days of stuffing my brain in the beautiful downtown campus of the University of Toronto was loads of fun...If you don't go to play each day, or you don't think you can break the rules, or you simply want to become a better tester, give Rapid Software Testing a try. I think you will find, as I did, that it is three days well spent!"
Michael Hunter (The Braidy Tester), Microsoft , "This is your Brain on RST"
"I thoroughly enjoyed your class on Rapid Software Testing. The more time I have to think about the class the more I find value in it. It has really changed my approach and ideologies around testing. The only thing left now is to get everyone in my office on the same page... Before I thought testing was just a stepping stone to move into development but now that I have more of an appreciation for testers, I think I'm going to stick with it and try to get others to realize how important testers are to software development."
James Swanson, Minneapolis, MN
"We are already starting to put into practice what you taught us—here is a mini case study. Four of the group sat down last Friday and tested another product. Dan (name changed for confidentiality --MB) guided and made suggestions. None of the 4 knew the product under test. The product test lead spent half the day being a live oracle. Results: Another 50 defects. Several were crashes (buffer overrun—thanks Perlclip!). Many UI and usability defects. By the afternoon the team was starting to find more specific defects in what the product should do, but wasn't doing. However, by this time they were getting very baked. This sort of testing is really hard work! However, the product lead was amazed by what was found, and the defects found per hour invested was—once again—orders of magnitude more effective than the testing that was currently going on with the product. We are going to cycle this much more frequently, and the same four are going to dig deeper on the same product later this week as well."
A test manager at a commercial utility software company, somewhere in Canada
"The training was a great exposure to a lot of different concepts and methods of attacking problems, and the rapid testing strategy looks to be very useful. On Thursday a support issue came into the group that fell in one of my feature areas, so I replied. I did a little work before lunch, and while out at lunch I thought that this would be a time to try some of the rapid testing methods. Took about 10 minutes, noted steps and thoughts as I was going, and arrived at a cause and possible solution much quicker than I would have in the past."
A recent student.