If you want to do good testing, you need a Test Strategy to set the directions and goals of your work.
What is the first thing you think about when someone mentions Test Strategy? A big document of 40+ pages with ton of theory, no one reads and is not up to date. Usually it represent those big Waterfall projects, where you first needed to write a Test Strategy and then start with tests cases and later with testing.
My experience and understanding is completely different. Based on a variety of different projects (domains, context, clients, goals), I can firmly say that each Agile project needs Test Strategy as a guidance how testing is done. It provides common understanding of testing processes, deliveries and expectations. During past few years, I helped many clients improve their testing by working (together with them) on a tailor based Test Strategy. In this talk I will explain what factors influence Test Strategy, why it must be tailor-made, because one strategy cannot fit all, and elaborate benefits we have noticed after defining Test Strategy and implementing it. Some of those Strategies were just a collection of few stickers on the wall and some were represented as quite long document(s). This talk will give you perspective on how to decide the Test Strategy definition and representation.