Download
agile testing isn t risking it n.
Skip this Video
Loading SlideShow in 5 Seconds..
Agile Testing isn’t Risking IT! PowerPoint Presentation
Download Presentation
Agile Testing isn’t Risking IT!

Agile Testing isn’t Risking IT!

127 Views Download Presentation
Download Presentation

Agile Testing isn’t Risking IT!

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Agile Testing isn’t Risking IT! Wednesday 7 November 2012 Eurostar 2012

  2. 1 2 6 5 3 4

  3. 1 2 6 5 3 4

  4. Agile in a nutshell Planning Meeting Team Scrum Master Sprint 2-4 wk Product Owner Scrum 24 u Retrospective Demo = Product Backlog Sprint Backlog

  5. Product Risk Analysis in a nutshell “A process or method to analyse the risks to the product, with the intention to utilize the testing effort in the most valuable way.” Classification: High Classification: Medium Classification: Low Product Risk Requirement “The likelihood that a product fails in relation to the conceivable damage when a product fails in production.”

  6. Risk & Requirement Based Testing in a nutshell Risk without requirement: Add requirement (a fault found early) Remove Risk (no worries about nothing) Requirement without Risk Add product risk (improves coverage of test) Remove Requirement (only make what is needed) MATCHING PRODUCT RISKS & REQUIREMENTS MATCHING REQUIREMENTS & PRODUCT RISKS Product Risks Requirements

  7. 1 2 6 5 3 4

  8. Merging or splitting features invalidate the PRA. Risk analysis were not translated to the Backlog which makes it difficult to utilise a risk based approach. REQ 03 ? REQ 07 SPEC A REQ 08 SPEC B SPEC C REQ 01 SPEC D REQ 05 ? SPEC E REQ 09 SPEC F REQ 10 SPEC G REQ 04 SPEC H ? SPEC I REQ 06 SPEC J REQ 02

  9. PRA isn’t updated Risk analysis were not updated every iteration, which could mean that they will be out dated within a sprint. REQ REQ PR PR REQ PR REQ REQ PR PR REQ REQ REQ PR REQ PR REQ REQ PR REQ PR REQ REQ REQ REQ REQ REQ PR REQ REQ REQ REQ REQ REQ REQ REQ REQ REQ REQ REQ

  10. PRA are done with tunnel vision Risk analysis were only done from the requirements which meant that some product risks were missed. Analyse Requirements Analyse Requirements Analyse Risk Order Requirements Order Requirements Determine Risk Analyse Risk Specify Test Cases Specify Test Cases

  11. Risk class isn’t used in planning meeting Risk analysis were done, but the outcome wasn’t taken into account in the planning meetings. 2 SP 2 SP 6 SP 6 SP 6 SP 3 SP 1 1 4 SP 4 SP 2 SP 3SP 3SP 9 SP Team Velocity = ± 14 Story Points 2 2 SP 2 SP 6 SP 8 SP 8 SP 8 SP 2SP 2SP 6 SP 2 3 2 SP 2 SP 6 SP High = 3n 3SP 3SP 9 SP 4 6 SP 6 SP 6 SP Medium = 1 n 2 SP 2 SP 6 SP 3 5 2 SP 2 SP 2 SP 4 SP 4 SP 4 SP Low = ½ n 4 SP 4 SP 2 SP 6 4 2 SP 2 SP 1 SP

  12. Testing is prioritizedbased on product risks Risk analysis were done, but the risks where prioritised using MoSCoW, which doesn’t automatically fit in a Agile environment. Sprint 1 Sprint 2 Sprint 3 M M M S S S = = = C C C = W W W

  13. 1 2 6 5 3 4

  14. Gather Risk Items

  15. Gather & Order Requirements Rank # 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 REQ 01 REQ 01 REQ 02 REQ 14 REQ 02 REQ 03 REQ 01 REQ 03 REQ 04 REQ 04 REQ 03 REQ 02 REQ 05 REQ 12 H MUST REQ 05 REQ 06 REQ 06 REQ 07 REQ 07 REQ 08 REQ 11 REQ 04 REQ 08 REQ 05 REQ 09 REQ 09 REQ 10 REQ 15 REQ 10 M SHOULD REQ 11 REQ 13 REQ 06 REQ 11 REQ 12 REQ 12 REQ 13 REQ 07 REQ 13 REQ 14 REQ 08 REQ 14 L COULD REQ 09 REQ 15 REQ 10 REQ 15

  16. Gather Product Risks PR 03 PR 02 PR 01 PR 05 PR 04 PR 06 PR 07 PR 08 PR 09

  17. Plot Risk Items

  18. Map Requirements & Product Risks 1/3 Requirements Product Risks REQ 14 REQ 01 PR 03 REQ 03 PR 02 REQ 02 REQ 12 PR 01 REQ 11 REQ 04 REQ 05 PR 05 REQ 15 PR 04 PR 06 REQ 13 REQ 06 REQ 07 PR 07 REQ 08 PR 08 REQ 09 PR 09 REQ 10

  19. Map Requirements & Product Risks 2/3 Product Risks Requirements REQ 14 REQ 01 PR 03 REQ 03 PR 02 REQ 02 REQ 12 PR 01 REQ 11 REQ 04 REQ 05 PR 05 REQ 15 PR 04 PR 06 REQ 13 REQ 06 REQ 07 PR 07 REQ 08 PR 08 REQ 09 PR 09 REQ 10

  20. Map Requirements & Product Risks 3/3 MUST H SHOULD M COULD L 20

  21. Calculate Risk Items

  22. Determine Impact & Likelihood Factors Impact factors e.g. Frequency of Use Visibility Cost of failure … Likelihood Factors e.g. Complexity Re-use Interfaces Dependencies Size … None Internal Interfaces Visibility 1 - 2 Partners > 2 Public

  23. Score & Calculate Item/Factor 23

  24. Strategy to tactic

  25. Risk class tactic Low = Effort * ½ High = Effort * 3 Medium = Effort * 2

  26. Sprint Tactic – Scope Sprint 1 Rank # 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 REQ 05 PR 01 PR 02 REQ 12 PR 03 REQ 13 PR 04 REQ 03 PR 05 REQ 04 PR 06 REQ 08 PR 07 REQ 02 PR 08 REQ 06 PR 09 REQ 07 REQ 09 REQ 01 REQ 10 REQ 11 REQ 14 REQ 15

  27. Sprint Tactic – Scope Sprint 2 Rank # 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 REQ 05 PR 01 PR 02 REQ 12 PR 03 REQ 13 PR 04 REQ 03 PR 05 REQ 04 PR 06 REQ 08 PR 07 REQ 02 PR 08 REQ 06 PR 09 REQ 07 REQ 09 REQ 01 REQ 10 REQ 11 REQ 14 REQ 15

  28. Scrum bord SPRINT 2 To Do Doing Done REQ 3 REQ 4 REQ 8

  29. Insight into Product Risk & Requirement coverage Done Doing Done Doing Done Done Doing To do To do Doing To do Doing To do

  30. Agile RRBT Gather Risk Items Plot relationship between Risk Items Calculate and Classify Risk Items Differentiate the work Lessons Learned Analyses can only be done with the backlog in place. Plan to iterate and evolve your analyses in sync with the sprints. Don’t use the backlog as your only starting point for your analyses. The result of your analyses is essential in the planning meeting. Order your testing effort in the small. Recap B.W.F.P.M. BRONNEBERG TEST MANAGER / CONSULTANT REQUIREMENT & QUALITY MANAGEMENT BRAM.BRONNEBERG@CGI.COM WWW.BRAMBRONNEBERG.NL @BRAMBRONNEBERG +31 6 55 11 35 10