Test plans have a bad reputation. There’s no beating around the bush. And perhaps they are deserving of a bad reputation. But software development has changed. We are Agile now! Test plans need to change as well. Do we need them at all? Perhaps not. If you do need a test plan, it needs to be Lean and easy and efficient- and fast to write.
From a different angle, to write a traditional test plan today as if “Testers” are the only guardians of quality is circa 1995; old and no longer true.
We will review the biggest complaints about test plans to modernize and make them more useful. You need to make an informed decision about needing a test plan or not. Then, to choose the most streamlined template possible that meets your organization’s need. We will start with traditional test plans and layout the needs for them but find more efficient ways to communicate this information. We will review a few smaller, sample test plans.
The goal is to optimize and minimize what you may have to write for a test plan and make it as Lean as possible while communicating the essential information.
