One of the participants in a course asked me about test strategies for agile projects.
Drawing on my extensive testing background I responded that I had heard of them and that I had also heard they were probably a good idea.
But I think he may have wanted a more extensive answer. He is doing test strategies on both waterfall and agile projects and his team are still using a long-winded document with a lot of cutting and pasting from previous projects.
He understands that strategy is more about the creation of the strategy than the publishing of a document and is comfortable with the idea that he collaborates and thinks before documenting the outcomes. But he is looking for a more effective way to document the test strategy and maybe have a template or approach that works for his agile projects.
Can anyone give him better advise than my sage comment “I have heard it is a good idea to have one.”?
Posted by James King