I am of the opinion that the Test Strategy should be created as a one off document and not for evey project.

I have been using the Test Strategy to communicate to those interested (upper management, project managers, test managers, testers and other interested parties) the strategic direction of our Test Organization.

As a Test Manager I refer back to this document while defining my Test Plan and take out of the strategy the things (building blocks) that I need (particular phases, techniques, tools, roles etc. ) for my particular project.

Doing it this way I can reduce the test planning effort by eliminating the Test Strategy as a project document and refer to it only. This way I speed up the process of creating the Test Plan as the thought process is “do I need this building block” as opposed to “which building blocks do I need”.

When you realise there is a building block missing then the Strategy can be updated and it becomes available for other Test Managers in your organization alike.