Abstract: One of the primary transformation points for companies and teams adopting agile is the goal of "moving left." The testing team has the largest journey to make in this process. As we've reviewed agile adoptions across projects one of the most common points of risk has been moving the testers from a paradigm of reacting to requirements toward developing testing expectations without detailed documentation. When a group has to make that journey together it becomes both easier and more difficult at the same time.
The twenty minute test plan was specifically designed/resurrected for teams being challenged to build out just in time test planning and estimates as part of the initial sprint planning. Within twenty minutes (on average) a team can rapidly plan, build, and estimate a thorough test plan based on nothing more than their knowledge of user value and the product itself. The method works equally well when a team likes to collaborate in a room or break out into individual sessions. The tool focuses on getting down what you know and what you already know to do so you can rapidly look for gaps AND share the work in an efficient and effective manner.
This will be an active working session emphasizing "doing" over "listening." The typical schedule is as follows:
10 minutes - Problem statement and background of the method
10 minutes - Breaking out into teams and signing into a website hosted on AppSpot
20 minutes - Teams will build out a test plan using the tool covering an area of a project they have not tested prior
5 minutes - Break out for reviews and comments
15 minutes - Teams will exchange plans and start testing using each other's work
15 minutes - Overview of the whole process and final Q&A
Learning Outcomes: - Test planning without requirements or designs
- Extracting user value statements from stories
- High level test estimating
- High level coverage estimation
