Importance of " Better Test Strategy"

What is the best strategy to be used for testing? This is very common question going around every testesrs mind the recent days. Todays Best Strategy can be the worst Tomorrow. The best strategy is the created based on the current situation of the project. The strategy, is the way or approach in which the testing will be taken forward. Do we need a template to do this. Frankly speaking NO. However, to have a checklist of items to be concentrated, we need to have a document which can be reviewed and updated. Test strategy, here would cover Plan for tests( type of tests), Plan to mitigate the RISK, Plan for Automation, Plan for resource. This what we follow in todays world. Is the list above makes the strategy complete? I dont think so. Strategy is far more than the list above or the template what we follow. Strategy should start from the day projects is kicked off. Some of the Important points -Review strategy,( this includes the Plan review) -Issues reporting startegy -Intermittent issues finding startegy -Critical issues identifying Strategy -Strategy to help developers to FIX issues with providing proper Logs etc...this should be well define as to what will be the Scope. This list can go on. We need to uncover such areas where startegy should be very strong and well defined. However, this is some thing done on real time and its difficult to produce during the intial stage of the Project. Hence, proper strategy and planning on case to case basis can really change the way of working. Due course of time we can see a tremendous improvement in the practices we follow. Can we say the that "Strategy followed is the BEST". There is always another path followed when it comes strategy. There is always a scope for improvement even for the BEST strategy. Hence, there is no BEST strategy possible, we can only make a Better startegy in real world. Its high time we start thinking within what we are stuck when it comes to Strategy