Please upgrade your browser!

Bookmark and Share

How To Write A Test Plan

Writing an Agile Test Plan

 

In agile, documentation is a tool to achieve a goal, and not an end in itself. And that goal is working software.  In addition, responding to change is favored over following a plan. So a key agile principle is to only document information that is needed.

Agile testing focuses on short iterative sprints with only a few requirements. Therefore, it is only natural that Agile test plan documentation is less extensive than with legacy testing, Instead, in Agile you need to create a test plan for each sprint, usually only a page or two in length. Basically, and Agile test plan needs no more than:

  • Introduction that lists basic information such as test scope and test objectives.
  • Test strategies, processes and steps.
  • Team roles and responsibilities.

Download the FREE whitepaper Scaling Agile Across Project Teams and Department by clicking on the image to the right. This step by step guide provides information on using a Test Management Platform, like Zephyr Enterprise Edition to develop and communicate Agile test plans.