Test Strategy and Test Plan

One of the Agile (Scrum) projects needs some documentation to ensure the test team is following due processes.

Although, Agile values a ‘Working software’ over ‘Comprehensive documentation’, I think a Test Strategy (for the project) and Test Plan (for each Sprint), can be followed, to keep the project on track, minimize team conflicts and keep stakeholders informed.

It would also help and new joiner to get up to speed quickly with the testing details.

Once baseline documents are created for both, updates to the Test Plan for each Sprint and relevant metrics should be quick.