In any of the traditional software developement life cycle model, testing team is either seen as a bottleneck or sole guardian of quality. Both of the perceptions have enough potential to cause significant damage to the Project and the Project Team. When the testers are seen as bottleneck; the tesing team is isolated from the developement team resulting in lack of team work. On the other hand when testers are seen as the sole guardians for the quality it causes even a bigger damage because no tester can produce quality, a tester can only guide through the route to quality based on the definition of quality in that specific context.
In a traditional methodology the tasks or responsibilities are divided among the analysts, designers, programmers and testers. Each group has its own set of grievance – requirements not available, test plan not available, configuration management not in place and such. Each group has a complete focus over its own deliverable but nobody has the focus on the product or project to be delivered.
SCRUM tries to resolve many of these issues. In Scrum we do not have an analyst responsible for business or a developer responsible for code, or tester responsible for testing. All that we have is a TEAM responsible for “what can be done with the available resources in order to best deliver the project“. Then each member of the scrum identifies what best can he or she do in order to deliver the project.
With the help of this tutorial we shall put forward the how Agile Testing can be useful in managing an unpalnned testing effort. How the same efficient human resoures work better with the same limited resources – a frame of mind to beat the chaos.

1. Introduction to Agile Testing - a frame of mind.
2. WWH (What, Why and How) of Agile Testing or expectations of Agile Testing.
3. Difference between Ideal Scrum and Practical Scrum.
4. Implemeting Agile Testing in the organization.
5. Dynamic Test Planning - higher degree of Quality of deliverables.
6. Sprint Planning – better control over the project budget.
7. Reporting Structure – better control over project progress.
8. Building stress free relationship between various stakeholders.
9. Testing Team – suitable for Agile Testing.
10. Developing an Agile Testing community.
11. Case Study.

The key learnings of this tutorials will be to –

1. Understand the Agile Testing as a frame of mind; not a model.
2. Develope a framework that would help in the most chaotic conditions for testing with in a project.
3. Appriciate the relevance of Agile testing to act as a key differentiator.
4. Improve the maturity level of Testing within the organization.