Combining requirements engineering and testing in agile.

1,414 views

Published on

Agile Testing Days Berlin, november 2012

Projects that use agile have small, multidisciplinary teams. When every discipline has its own specialist in the team, the team becomes bigger and bigger leading to more communication, coordination and more need for documentation. Combining programming and testing is not a wise decision but combining requirements engineering and testing is very well possible. It even turns out that a lot of communication, documentation and coordination is not necessary. So a lot of time and effort can be saved. During his presentation Jan Jaap tells why testers are excellent requirements engineers (and vice versa) and what the advantages of combining requirements engineering and testing can be. He also addresses what testers should do to get this combined role. With agile becoming more and more popular this can be a possible future for testers.

The idea of combining requirements engineering and testing started with a vision. By now we have enough practical experience to show that is actually works! During the presentation Jan Jaap shares vision and practical experiences.

Published in: Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,414
On SlideShare
0
From Embeds
0
Number of Embeds
320
Actions
Shares
0
Downloads
42
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Combining requirements engineering and testing in agile.

  1. 1. Combining requirementsengineering and testing in agileA possible futureSlide share: http://www.sysqa.nl/expertise/presentaties/Jan Jaap Cannegieter –Vice President SYSQA B.V. jcannegieter@sysqa.nl @jjcannegieter
  2. 2. Agenda• The essence of requirements engineering• The outline of the idea• Combining the requirements and testing tasks• Consequences of combining requirements engineering and testing in an agile project• Consequences for testers © SYSQA Almere 2
  3. 3. The essence of requirementsengineering
  4. 4. Requirements process Requirements process Requirements Requirements Requirements development validation management - Stakeholders - Correct - Explanation - Needs - Complete - Traceability © SYSQA Almere - Requirements - Consistant - Verification
  5. 5. Levels of requirements Non- Functional functional Business requirements User requirements System requirements © SYSQA Almere
  6. 6. Waterfall versus agile Business requirements Userrequirements Systemrequirements Waterfall Agile © SYSQA Almere 6
  7. 7. Requirements in agileProduct Product Sprints vision backlog User Business requirementsrequirements Systemreq., User story 1 User story 2 design, € build, test User story 3 User story 4 Systemreq., User story 5 design, € build, test © SYSQA Almere Product owner Scrum team (+ requirements engineer) 7
  8. 8. Outline of the idea
  9. 9. Tester in an agile team Traditional Agile Requirements User Requirements User engineer engineering © SYSQA Almere Developer Tester Developing Testing
  10. 10. Tester in an agile team Traditioneel Agile Requirements User engineer User Developing © SYSQA Almere Developer Tester
  11. 11. Tester in an agile team Traditioneel Agile Requirements User engineer User Developing © SYSQA Almere Developer Tester
  12. 12. RE-tester andrequirements tasks
  13. 13. Product backlog grooming“One of the lesser known, but valuable, guidelines inScrum is that five or ten percent of each sprint mustbe dedicated by the team to refining (or “grooming”)the product backlog. This includes detailedrequirements analysis, splitting large items intosmaller ones, estimation of new items, and re-estimation of existing items.”Jef Sutherland – The scrum papers © SYSQA Almere 13
  14. 14. RE – tester and documentationUser story• System requirement• System requirement• System requirement © SYSQA Almere 14
  15. 15. RE-tester and testing tasks
  16. 16. Scripted versus exploratory testing Pure Vague Freestyle Scenario’s Charters Roles exploratoryscripted scripts © SYSQA Almere Image by Jon Bach 16
  17. 17. RE – tester and documentationUser story• System requirement • Test point • Test point • Test point• System requirement • Test point • Test point • Test point • Test point © SYSQA Almere• System requirement • Test point • Test point 17
  18. 18. RE - tester and documentation © SYSQA Almere 18
  19. 19. Or mindmaps19 © SYSQA Almere
  20. 20. Consequences
  21. 21. Effort Backlog grooming: Refining user storiesStartSprint into system requirements Requirements validation management Requirements Endsprint Effort requirements engineering © SYSQA Almere
  22. 22. Effort tester Effort Execution Test Test preparation © SYSQA Almere Test design Start End sprint sprint
  23. 23. Effort RE-tester Effort Effort RE-tester © SYSQA Almere Start End sprint sprint
  24. 24. RE-tester and knowledge
  25. 25. Knowledge (and time)Knowledge Testing Requirements engineering © SYSQA Almere Start End sprint sprint 25
  26. 26. Knowledge RE-testerKnowledge Requirements engineering - testing © SYSQA Almere Begin End Sprint Sprint 26
  27. 27. RE-tester and techniques
  28. 28. Techniques – an overviewRequirements eng. Testing• Use cases • Boundary analysis• Class diagram • Dataflow test• Activity diagram • Control flow test• Status diagram • Cause and effect graphing• Entity relation diagram • Decision table• Dataflow diagram • State-transition test © SYSQA Almere• Problem frames • Equivalence class test• User stories • Test charter: test points 28
  29. 29. Techniques – system requirements Shall <process> Provide The <details When? <whom?> with system Should <object> about Condition? the ability to <name> object> <process> Will Be able to © SYSQA AlmereOn request of the client the system shall show the delivery status of an ordered book 29
  30. 30. Techniques – system requirementsDoes © SYSQA AlmereOn request of the client the system shall show the delivery status of an ordered book 30
  31. 31. Techniques – system requirementsDoes the system show the delivery status of an ordered book on request of the clientPriority 1 © SYSQA Almere shall 31
  32. 32. Will RE-testing be the future?
  33. 33. Advantages and disadvantages © SYSQA Almere 33
  34. 34. Advantages and disadvantages € © SYSQA Almere 34
  35. 35. Advantages and disadvantages € © SYSQA Almere 35
  36. 36. What does this mean for you?
  37. 37. Can you do it? © SYSQA Almere 37
  38. 38. What does this mean for you? © SYSQA Almere 38
  39. 39. Slide share: http://www.sysqa.nl/expertise/presentaties/Jan Jaap Cannegieter –Vice President SYSQA B.V. © SYSQA Almere jcannegieter@sysqa.nl @jjcannegieter 39
  40. 40. 40 © SYSQA Almere

×