The document discusses perceptions of testing before and during agile development. It identifies problems that can arise during the transition to agile such as role confusion and resistance to change. The document compares traditional vs agile testing and notes that in agile, testing tasks are done in parallel with development from the start of each sprint. It outlines the roles of various team members in agile and emphasizes that quality is a team responsibility involving continuous feedback. The document also lists types of testing used in agile and benefits such as more testing time and less manual testing.
2. Perceptions-Before we go
Agile
A tester cannot program
A tester is not required in
planning
A testers work starts after
functional development
K.Swarnalatha, PMP,CSM
12/3/2013
3. Problems/Questions while
adapting agile
Confusion about new role
Resistance to change
Trying to bend the rules and
principle’s of agile
If developers are writing tests,
what do the testers do?
I’m a QA Lead/manager, and our
company is implementing agile
development. What’s my role now?
The Toughest Change: Organization
Culture
K.Swarnalatha, PMP,CSM
12/3/2013
5. Scrum Master’s Approach
Does Agile Solve all the
problems?
It reveals the problems.
It is people who need to
solve them!
K.Swarnalatha, PMP,CSM
12/3/2013
6. The way the testing changed
Sprints mark the start of the
testing
Testing Task is like any other
task
Work in Parallel with
Developers
K.Swarnalatha, PMP,CSM
12/3/2013
8. Quality
Team is responsible for
Quality.
Continuous Feedback
Quick and maximum
communication
K.Swarnalatha, PMP,CSM
12/3/2013
9. Types of Testing
Test Planning
Unit Testing
Acceptance Testing
Functional Testing
Regression Testing
Test Automation
K.Swarnalatha, PMP,CSM
12/3/2013
10. Benefits of Agile Testing
More Testing Time
Continuous Testing
Deliver Value to the Testing
Face to Face communication
Self Organize
Less Manual Testing
Develop Competency
The aim is same – Change is good
K.Swarnalatha, PMP,CSM