1. 1victo.eu 2013 What is the risk? Can we deliver? How many days?

2. 2victo.eu 2013 Actually, it is even worse: What… when… can we?

3. 3victo.eu 2013 It was known long ago… «To avoid disaster, all the teams working on a project should remain in contact with each other in as many ways as possible — e- mail, phone, meetings, memos etc.» 1975 – 1982 - 1995

4. 4victo.eu 2013 The solution? Project team builds Testing team knows the status = requirements The customer knows acceptance criteria Project sponsor knows business risks

5. 5victo.eu 2013 Status-showing bulb panel One bulb for each requirement shine red From the beginning, all lamps shine red: no requirement has been implemented, nothing has been verified

6. 6victo.eu 2013 Not all bulbs are the same Small lamps: less important requirements (lower business risk, lower risk consequences) Big lamps: higher business risks

7. 7victo.eu 2013 Risk probability Lamps on high posts denote high probability risks

8. 8victo.eu 2013 Evaluation significance Brighter lamps mean higher status significance (e.g. more thorough testing, higher test coverage needed)

9. 9victo.eu 2013 Bulb matrix Risk probability and required significance of risk estimations are omitted on this figure Time (releases)

10. 10victo.eu 2013 Bulb matrix and test design It makes basic (risk-based) test design decisions more visible, but does not solve them How much will given test cases decrease probability? With what significance?

11. 11victo.eu 2013 Bulb matrix and test execution Test execution order and prioritization Release planning Traditional test reporting hardly needed any longer Status visibility on all levels

12. 12victo.eu 2013 … and test completion criteria Test process gains emotional intelligence no more «are we ready?» questions Automatically to all levels Business criteria already build into requirement importance

13. 13victo.eu 2013 Benefits until now Risk-based testing de-mystified … connected to model-based testing … and requirements engineering … and risk management IT’S MUCH SIMPLER!

14. 14victo.eu 2013 The presenter Victo.eu bogdan.bereza@victo.eu Meet me as well at: ireb.org ireb.org.pl (PL) Software Requirements Magazine: requirementsjournal.com kravhantering.org testerzy.org.pl (PL) Gazeta testerów: gazeta.testerzy.org.pl (PL) Good Requirements conference (October 2013): breq2013.wymagania.org.pl (PL + ENG) Polish Association for Requirements Engineering pare.wymagania.org.pl

15. 15victo.eu 2013 More benefits Project management: Requirements → project tasks Requirements implementation → project estimation Requirements status → project monitoring Data for process improvement

16. 16victo.eu 2013 Tool support www.incose.org/productspubs/products/ setools/tooltax/reqtrace_tools.html Some tools are expensive A cloud solution may be worth considering for pilot project: – You pay for what you use – Scalable

17. 17victo.eu 2013 For example, ReQtest

18. 18victo.eu 2013 ReQtest example Du får gärna använda vår ReQtest kostnadsfritt under CzechTest, Bogdan! Ulf Eriksson – Product Owner/Founder www.reqtest.com/about-us