Transitional steps of testers when move from traditional software development environment to agile software development environment: change from mindset to approach

1. XP DAY
Transitioning from a
Traditional Tester to an Agile
Tester
Tu BUI

2. Traditional vs. Agile Organization

3. Traditional vs. Agile Development

4. Traditional vs. Agile Tester Role

6. Traditional vs. Agile Testing Approach
AGILE TESTING TRADITONAL TESTING
Agile Testers are integrated, full-fledged
members of the development team and
participate in planning, estimation and all
team activities
Testing is performed by a separate
organization or group with one or more
teams of QA engineers reporting to a QA
manager
Agile Testers work hand-in-hand with
development and product management
QA team may work with other groups but
with limited interactions and well-established
boundaries
Business requirements are written in piece
at a time to accommodate changing
business needs
QA and development received detailed
business requirements and schedule up
front
Developers often take the lead on code-
level tests while agile testers focus on
acceptance test automation and building
regression test plans
While developers write code, testers write
test plan and test cases to support
predefined business requirement

7. Traditional vs. Agile Testing Approach
AGILE TESTING TRADITONAL TESTING
Throughout the release addition test
scenarios are uncovered through exploratory
testing
When development is presumed complete,
the application is delivered to QA for testing
Agile testing is continuous and feedback is
provided during all stages of development
QA completes a cycle of tests and reports
defects back to development
Agile testing allow a fluid, continuous
process with defects fixed as they are found
When testing is complete, development fix
defects and delivers another revision to QA.
Agile testers are expected to radiate
information and provide complete visibility
into all test-related activities for the benefit of
the larger group
Traditional QA team s often keep test design,
implementation and progress specifics within
the QA “wall”
Quality Software is always ready to be
delivered
The process of test and fix repeats until
time runs out

8. Traditional vs. Agile Testing Approach
AGILE TESTING TRADITONAL TESTING
Testing is conducted immediately and
continually as soon as possible, with the
smallest feature(s) available. Test-
driven development is employed.
Testers usually wait on a specific build
or release and then begin testing once
most features are implemented.
Testing is planned as part of the sprint
and the release. Developers automate
unit tests.
Functional and nonfunctional testing is
conducted iteratively within the team
and in collaboration with the product
owner.
One phase of testing usually builds on
the next—unit, then integration, then
system, then acceptance.
Bug identification and repair is in hours
rather than days or weeks.
There is significant wait time between
bugs being identified and bugs getting
fixed.

9. Traditional vs. Agile Testing Approach
AGILE TESTING TRADITONAL TESTING
Developers and testers operate as one
team and interact continuously and
collaboratively. The testing voice is equally
represented.
Testers are less a part of the development
team. Testers may be more distant in
interaction and communication with
developers and may have less of a voice.
Testers and developers are part of a
homogeneous team accountable for quality
delivery of the system under test.
Testers are accountable for testing.
Developers are accountable for developing.
Testing is continuous and all quality steps
are planned and executed iteratively by the
agile team.
While the goal is always to have quality built
in at every step in the lifecycle, in practice,
much of the checking (quality steps) occurs
during the backend testing cycle.
Automation is a must have, particularly for
unit tests, as it supports continuous
integration.
Automation is not a necessity because most
testing of new development is done
manually.

10. Traditional vs. Agile Tester
Competencies

11. Traditional vs. Agile Bug fixing process

12. Traditional vs. Agile Quality Metrics

13. Traditional vs. Agile Quality Metrics

14. Traditional vs. Agile Testing Mindset

15. Agile in the facts

16. Agile in the facts

17. Agile in the facts

18. Thank you!
Q&A