Exciting news! Michael Bolton – a Rapid Software Testing guru is coming to Poland! He will run a 3-day hands-on Rapid Software Testing course before TestingCup (on May 23-25). This training has been praised by testers all over the world and it will be the first ever RST public class in Poland.
- Are you a tester interested in learning skills and approaches that will help you to become a better tester?
- Are you a developer (or a team of developers) who would like to sharpen your testing skills?
- Are you struggling to determine the role of testers and testing in an Agile team, or in a DevOps context?
- Are you finding it difficult to get the time or resources or attention you need need to test effectively?
- Are you overwhelmed by or uncertain about approaches to test planning, design and execution?
- Are you working in an environment where some people aren’t following “the rules”? Or following them too closely for comfort?
- Are you having trouble finding the right balance between planning, documentation, and testing?
- Are you finding that “industry best practices” are infeasible and a poor fit for your organization?
- Would you like to connect—or reconnect—with your passion for learning and discovering problems in order to help defend the value of your organization’s products and services?
- Do you want to get very good at software testing?
Rapid Software Testing addresses these issues and more.
Michael Bolton is a consulting software tester and testing teacher who helps people to solve testing problems that they didn’t realize they could solve. He is the co-author (with senior author James Bach) of Rapid Software Testing, a methodology and mindset for testing software expertly and credibly in uncertain conditions and under extreme time pressure. Michael has 25 years of experience testing, developing, managing, and writing about software. For almost 20 years, he has led DevelopSense, a Toronto-based testing and development consultancy.
Michael is aligned with the Context-Driven School of Software Testing, a community of people who believe that testing should respond first and foremost to the needs of the organization and the project, rather than to “best practices” that may not be best at all in the given context. You can read more about these ideas here.