FREE Test Strategy Product Description Document
Please click on this link to download FREE template
One of the most important project documentation milestone to achieve on any project, has to be the sign-off of a Test Strategy document. This typically contains the testing methodology and acceptance criteria, vital if you want to define the end point for a project and the starting point for maintenance and support to begin.
If your running a software house, getting a clear end to a project is one of the keys to profiatable software development.
A significant proportion of the IT projects I have troubleshooted over the years have delivered systems but have never offcially reached the point where they can close the project. Many software houses unaided by an agreed Test Strategy have ended up providing at best free maintenance and support under the guise of “Bug Fixing” or at worst provided a never ending stream of free system upgrades as no one can agree what received and delivered requirments add up to acceptance. This problem of project closure and protecting against consequential profitabilty errosion is a common problem expereinced by smaller softwarehouses and a document of this kind can really help.
However, I have seen some softwarehouses get round the problem of not having a Test Strategy Document in there project document dleiverables check list through the addition of a cluase in the SOW or Service Contract which states that “if the system has been introduced into a live commercial enviroment then the system will have been deemed to have been accepted”.
This entry has been viewed 21432 times.