As more and more organizations transition to agile, many still do not understand how testing fits into agile teams. Does it simply mean placing a tester on every team? Or does it mean doing away with the role of testers? Pradeepa Narayanaswamy explains the importance of working in cross-functional teams that integrate development and testing. Pradeepa shares her insights into the keys of agile testing including understanding the agile testing mindset and goals. She discusses the responsibilities of a tester in an agile team and describes the diverse skill sets required in those teams. Pradeepa also shares her ideas on how to manage defects, what to measure, and what to document. She concludes by describing what is NOT agile testing and debunks certain agile testing myths. Review these important basics and align your testing with concepts that may have been overlooked, forgotten, or misunderstood in your teams.
2. Pradeepa
Narayanaswamy
Centare
As a senior agile consultant and coach specializing in agile testing, Pradeepa
Narayanaswamy is a self-proclaimed “agile passionista” who strongly believes in the
agile principles used in transforming organizations to build superior quality products.
Pradeepa has held many roles including developer, test specialist, and quality
assurance and testing lead. She has worked with and led testing teams of various sizes
and recognizes the benefits of agile testing to help teams effectively perform testing
in parallel with development. Pradeepa coaches and mentors development teams,
helping them embed agile testing techniques and succeed with building high quality
products.
17. 2/4/2014
15
Sprint Backlog
Work with the Product Owner to add more details to
acceptance criteria
C ll b i h h b ddCollaborate with other team members to add more
technical details/considerations
User stories can be detailed against the requirement
IdentifyIdentify
Test scenarios
Testing related tasks
Product Increment
As a team
Demonstrate the “DONE” work
Gather feedback for the “DONE” work from the stakeholders/customers
21. 2/4/2014
19
Metrics to consider
Metric Purpose Audience
Working Software To gain review feedback Development Team,
Stakeholders, Customers
d ’ d lSprint Burndown Team’s progress during a
sprint
Development Team
Velocity Trend Team’s throughput over
sprints
Development Team
Release Burndown To forecast feature completion
based on team’s historical
velocity over sprints
Development Team,
Stakeholders, Customers
DOCUMENTATION – WHAT MATTERS??