What is a test strategy? How do you get commitment from your stakeholders? What's the difference between a strategy and a plan? How do you manage risk? Will anyone read it anyway?

Have you ever written a document that no one read?

You might think that a test strategy is a document, but in this video, I want to move away from that idea. I want to suggest that strategy is a thought process - not necessarily a document. Now you might write stuff down and you might be required to write down a strategy for a larger, more formal project of course, but often, the strategy is more about the conversations you have with stakeholders and the other participants in your project.

I want to move away from documentation and encourage you to think about the kind of conversations you need to have and the decisions you need to make to capture whatever you call and whatever you record as a test strategy.

If you want to know more about the concepts I'm talking about in the glossary of terms videos, it will probably help you if you take a look at the leadership in test online class that I created a year or two ago, it covers some of the topics in more detail and obviously provides more of a structured approach to explanations of the concepts. It also gives you some idea of how to do some of the things I talk about. I hope you can take a look at it and get value out of it. The link is here: https://bit.ly/leadintest