This document discusses how testers can be effective in agile teams using Scrum. It begins by distinguishing quality assurance (QA) from quality control (QC) and outlines how testers can focus on helping teams achieve "done" by collaborating in backlog grooming and preventing bugs. The document recommends that testers work with rather than against developers by pairing, writing automated tests, and participating in code reviews. It also advocates for exploratory testing and emphasizes the importance of collaboration between testers, developers, analysts and product owners.

1. Effective Quality
Assurance
-- Excel as an Agile tester
- Srinivas Chillara

2. Srinivas Chillara
- Consultant, Coach and Trainer
- Blogs at http://ceezone.wordpress.com
- Deeply interested in Software
-- Quality
-- Process
- Helped many companies with Scrum and TDD
Adobe, Cisco, Nokia, Sungard, Yahoo!, Zensar

3. This talk is about
Achieving Success in software projects
By the way, we shall cover:
0. Difference between QA and QC
1. How testers can be effective in Scrum teams
2. Collaboration
3. How testers can excel

4. A Simple view of Scrum
Scrum is a framework for management and workers to execute complex projects.

5. Testers in great teams
1. Testers focus on helping team
get to ‘done’ by DoD
2. Contribute to Backlog grooming
3. Prevent bugs and integrate with team

6. Root of Problems faced by testers
THINKING THAT QA is same as QC
LACK OF UNDERSTANDING OF TESTING
Example: Tester to Dev ratio should be 1:3
ASSUMING THAT TESTING IS EASY
Testers are usually lower down the pecking order

7. Who is the enemy?

8. What can be done to improve effectiveness
By testers
1. Work with the others, not against
2. Let management know that testers are effective if they
take up wider responsibility for quality
By Others
1. Understand testing activities better
2. Involve testers early as possible -- which means all the
time!

9. What needs to change
For testers to be effective
1. Management understanding and measurement
of testers (bug counts anyone)
2. Rebalancing tester’s role from problem finder
towards problem preventer
3. Learn from Scrum: Prioritise your activities

10. A few words about code coverage
Code coverage is important, but NOT the holy
grail
FALSE (100% coverage == no bugs)
See: http://googletesting.blogspot.in/2014/07/measuring-coverage-at-google.html

11. Effective testers
Collaborate, collaborate, collaborate
1. Test at their workstations
2. Pair Program
3. Start by writing automated tests
4. Create input data (and options)
5. Teach developer how to unit test
6. Learn about new approaches …

12. Learn to collaborate
Work with developers, analysts and PO
1. Help developers prevent defects
2. Understand and Explain Code coverage
3. Participate in code reviews
4. Learn a scripting language

13. Learn Exploratory testing
"Exploratory testing is an interactive process of concurrent
product exploration, test design and test execution -- To
the extent that the next test we do is influenced by
the result of the last test we did, we are doing
exploratory testing.” --- J Bach (2001)

14. Effective Quality Assurance
-- Excel as an Agile tester
QUESTIONS?
- Srinivas Chillara
Scrum coach and consultant
http://ceezone.wordpress.com
Connect with me on LinkedIN