CopenhagenContext 2017

Test Management In A Scrum Setting [R08]

In this presentation we will take a dive into test planning in projects based on a SCRUM-setup, in order to investigate which parts of the test plan is important in different contexts, how we find out what the context is and of course, also see if we really need a test plan at all.

Many test managers create test plans based on “the one we used in the last project”. In some cases that test plan can be traced back to a time well before projects were run in an agile fashion, and these monsters from the past can in themselves present a risk: they are too big and too difficult to work from, when you’re inside a 2-week sprint. Essentially this leaves us with the choice of having a test plan on the side of the project, to just get the checkmark, so to speak, or seriously rewamp the test planning into the Scrum setup, discarding the bits which are no longer useful and adding as well as clarifying how we want testing to be, now that we are doing Scrump.

The questions we will seek an answer to are: - why do we test in the first place?
- who does the testing?
- what do we test and when?
- how would a true scum-isa test plan and strategy look?