Agile Support Center Setup for Testing Departments
•
0 likes•430 views
Presentation Bernd Beersma and Erik Bits on ExpoQA 2014
Recommended
Recommended
More Related Content
Similar to Agile Support Center Setup for Testing Departments
Similar to Agile Support Center Setup for Testing Departments (20)
Recently uploaded
Recently uploaded (20)
Agile Support Center Setup for Testing Departments
- 1. Madrid, 26th to 28th May 2014 Setting up an Agile Support Center For Test and Maintenance Departments
- 2. Madrid, 26th to 28th May 2014 e: bernd.beersma@2b4qa.nl m: +31(0) 6-11010659 tw: @bbeersma
- 3. Madrid, 26th to 28th May 2014 e: erik.bits@2b4qa.nl m: +31(0) 6-11738416 tw: @erikbits
- 4. Madrid, 26th to 28th May 2014 PLANNED IN PROGRESS DONE Functionality vs Characteristics Testing vs Checking Increasing Test Effort Product Backlog Sprint 1 Waterfall versus Agile
- 5. Madrid, 26th to 28th May 2014 Waterfall versus Agile
- 6. Madrid, 26th to 28th May 2014 Waterfall versus Agile Individuals and interactions Over Working software Over Over Customer collaboration Responding to change Over Process and tools Comprehensive documentation Contract negotiation Following a plan
- 7. Madrid, 26th to 28th May 2014 Benefits caused by Agile Earlier involvement of testers in the project Flexible approach Boundaries between test & development vanish Joint quality awareness
- 8. Madrid, 26th to 28th May 2014 Risks caused by Agile Lack of documentation Changing requirements, flexible approach Testing ‘what is’ instead of ‘what is expected’ Joint quality responsibility
- 9. Madrid, 26th to 28th May 2014 Risks caused by Agile Focus on functionality Limited knowledge of test automation Increasing test effort
- 10. Madrid, 26th to 28th May 2014 Increasing test effort
- 11. Madrid, 26th to 28th May 2014 1. 2. 3. 4. 5. Limited knowledge of TA within the teams Scope creep from ICT & Process to ICT Increasing test effort We need test automation Backlog sprint 1 Focus on functionality
- 12. Madrid, 26th to 28th May 2014 Agile Support Center Iteration 0 Agile Support Center Sprint 1 Sprint 3Sprint 2 Ticket Ticket Maintenance Departement Regression Sprint 2 Regression Sprint 1 Checklist Single Point of Communication (ASC) TicketsTicketsTickets Hardening
- 13. Madrid, 26th to 28th May 2014 Ticket = mini-testplan
- 14. Madrid, 26th to 28th May 2014 Ticket = mini-testplan
- 15. Madrid, 26th to 28th May 2014 1. 2. 3. 4. 5. Limited knowledge of TA within the teams Scope creep from ICT & Process to ICT Increasing test effort We need test automation Definition of Done Focus on functionality
- 16. Madrid, 26th to 28th May 2014 PLANNED IN PROGRESS DONE Functionality vs Characteristics Testing vs Checking Increasing Test Effort Product Backlog Waterfall versus Agile
- 17. Madrid, 26th to 28th May 2014 Testing versus Checking
- 18. Madrid, 26th to 28th May 2014 Functionality versus characteristics Functionality is still important, Characteristics are increasingly important……
- 19. Madrid, 26th to 28th May 2014 9126 Maintainability Portability Efficiency Functionality Reliability Usability ISO 9126
- 20. Madrid, 26th to 28th May 2014 25010 Maintainability Portability Performance Efficiency Security Compatibility Functional Suitability Reliability Usability ISO 25010
- 21. Madrid, 26th to 28th May 2014 ISO 25010
- 22. Madrid, 26th to 28th May 2014 1. 2. 3. 4. 5. Awareness is created, but what about execution? Not all tests can be automated, still manual tests Shift from functionality to characteristics Limited knowledge of characteristics in the teams Backlog sprint 2 Synchronization between ASC and Scrum team
- 23. Madrid, 26th to 28th May 2014 Agile Support Center SecurityTest Sprint 1 SecurityTest Sprint 2 Performance Test Sprint 1 Tickets Aut. Regression Testing Performance Testing Security Testing Test Environment Other Agile Support Center Iteration 0 Sprint 1 Sprint 3Sprint 2 Ticket Ticket Maintenance Departement Regression Sprint 2 Regression Sprint 1 Checklist Single Point of Communication (ASC) TicketsTicketsTickets SecurityTest Sprint 1 SecurityTest Sprint 2 Performance Test Sprint 1 Process: ☑ The SPOC brings the characteristics to the attention ☑ determine initial test capacity ☑ determine initial planning ☑ adjust / calibrate the planning according to sprint backlogs ☑ Preparation of the detailed planning based on the Agile tickets ☑ Periodic evaluation and adjustment
- 24. Madrid, 26th to 28th May 2014 1. 2. 3. 4. 5. Awareness is created, but what about execution? Not all tests can be automated, still manual tests Shift from functionality to characteristics Limited knowledge of characteristics in the teams Synchronization between ASC and Scrum team Definition of Done
- 25. Madrid, 26th to 28th May 2014 PLANNED IN PROGRESS DONE Functionality vs Characteristics Testing vs Checking Increasing Test Effort Product Backlog Waterfall versus Agile
- 26. Madrid, 26th to 28th May 2014 3 Good reasons for an ASC
- 27. Madrid, 26th to 28th May 2014 Reuse of knowledge Reuse of Testware Central Testware management Flexibele Resourcing Efficient use of available time For Whom (what’s in it for me)? Reuse of Tooling Available Time Available Knowlegde Available Resources Available Fundings
- 28. Madrid, 26th to 28th May 2014
- 29. Madrid, 26th to 28th May 2014