The document discusses the importance of Quality Assurance (QA) in Agile development, emphasizing that QA should be integrated within Scrum teams rather than seen as a separate function. It outlines the various testing quadrants and the role of team collaboration in ensuring quality, stating that every team member is accountable for quality and testing can occur at any point. The presentation encourages automation and shares best practices for developing effective testing strategies across agile teams.

1. Agile and QA... ma che ciazzecca? Better Software 2010 Firenze, May 5 th -6 th Stefano Fornari, Funambol CTO

2. Agenda Do we need QA in scrum?

3. QA vs Testing

4. Agile testing

5. QA in our team

6. Q&A

10. QA vs testing Quality assurance is an effort to prevent defects from entering the system

11. QA vs testing Quality assurance is an effort to prevent defects from entering the system Testing is any activity to discover defects in the system

12. Test at the end It is hard to improve the quality of an existing product

13. Mistakes continue unnoticed

14. The state of the project is difficult to gauge

15. Feedback opportunity are lost

16. Testing is more likely to be cut Development Test Delivery

17. Without test, there is no value delivered If it's not tested, it's not done

18. If not done it's not accepted

19. If it's not accepted, there's no value delivered

20. Agile development Iterative and incremental development

21. Cross-functional teams