The document discusses testing in agile projects through a case study. It presents four case examples of companies using agile methodologies and discusses both benefits and challenges of testing in agile projects. Specifically, it notes that agile practices like incremental development help ensure quality at the end of each iteration. However, agile also demands discipline from teams and individuals and can be difficult for testers accustomed to more traditional roles. The document concludes that in agile, testing is a function all team members contribute to rather than a separate role.

1. Testing in Agile Projects – Case Study Armands Baranovskis Sanda Linde TietoEnatorAlise

2. Page 2 We are Agile – we don’t need testing!

3. Page 3 Agile Principles Incremental development Delivering a series of (useful, usable) deliveries Iterative development Allowing requirements to evolve and be added to Responding quickly to new business priorities People-oriented development People’s qualities rather than heavy process Allowing the agile team to manage themselves Daily interactions between developers and the business Technical excellence and built-in quality Personal responsibility, craftsmanship and simplicity Lean approach Measure progress by delivered product Minimize waste

4. Page 4 Case 1

5. Page 5 Case 2

6. Page 6 Case 3

7. Page 7 Case 4

8. Page 8 We are Agile – we don’t need testing!

9. Page 9 Do we?

10. Page 10 How agile does it?

11. Page 11 Agile versus Waterfall

12. Page 12 Benefits Quality of the product is insured at the end of every iteration All team members gain significant business knowledge All team members are multifunctional Both, project team and client, have more impact on the product and the outcome Satisfied client due to transparency and trust Less is more

13. Page 13 Problems Historical stratification among roles Agile is especially hard for testers: Why should I test something that isn’t ready? Why should I do someone else's job? How can I test without documentation? Agile demands high individual and team discipline and initiatives

14. Page 14 Testing is a function, not a role.

15. Thank you. Armands Baranovskis Sanda Linde TietoEnator Alise www.alise.lv