Embed Size (px)
DESCRIPTION
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.
Citation preview
rent Session
Presented by:
Pradeepa Narayanaswamy
Brought to you by:
340 Corporate Way, Suite Orange Park, FL 32073 888‐2
T3 Concur4/8/2014 10:30 AM
“We’re Moving to Agile: What Are Our Testers Going to Do?”
Centare
300,68‐8770 ∙ 904‐278‐0524 ∙ [email protected] ∙ www.sqe.com
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.
2/4/2014
1
We’re Moving to Agile: What Are Our Testers Going to Do?
Presented by Pradeepa Narayanaswamy@NPradeepa
AGENDAWhat is Agile Testing?
Agile Testing Goals & Mindset
Tester’s contribution in Events & Artifacts
Defect Management
Metrics
Documentation
2/4/2014
2
WHAT IS AGILE TESTING???
Agile TestingAsynchronous
D i ll l ith d l tDone in parallel with development
Design activity
Collaborative
IncrementalTesting feedback guides development
2/4/2014
3
Testing is a Design Activity
TestTest
Potentially Shippable ProductBusiness Requirement
CodeRequirement
Agile Testing
Done
Test
Testing Specialist Coding SpecialistStart
Understand mutual domains
Understand the Story/Requirement
Testing Specialist
Coding Specialist
Testing Specialist Coding Specialist
Execute domains
Test WritingEmphasis
Code WritingEmphasis
Testing Specialist
How will we test this?
Testing Specialist
How will we build this?
Coding Specialist
Coding Specialist
©Chad Albrecht
2/4/2014
4
Agile Testing Goals
Quality = Acceptance criteria + Definition of Done
Quality is measured by Customer feedback
Fix defects instead of managing themFix defects instead of managing them
Avoiding mini‐waterfall
2/4/2014
5
AGILE TESTING MINDSET
Collaboration is inevitable
End userEnd user
2/4/2014
6
Team owns Quality
Planning is always ongoing
2/4/2014
7
Communication is criticalUpfront & frequent communication over detailed documentation
Requirements are NOT set in stone!!
2/4/2014
8
Typical metrics matter least
Cross‐functional teams
2/4/2014
9
are they Cross functional?
Keep an eye on the “BIG” picture
2/4/2014
10
Testing to aid fast feedback
Failure is OK, but fail fast & learn…
2/4/2014
11
TESTERS’ CONTRIBUTION IN EVENTS
Backlog RefinementUnderstand
Requirement
Technical details
Define & Refine Acceptance criteria
Effort estimationEffort estimation
Testing related activities and time are included
Test related intricacies may be discussed/understood
2/4/2014
12
Sprint Planning Approach the planning from quality and testing perspective
Identify test scenariosy
Identify “ilities”
Challenge technical discussions from testing standpoint
Assist team identify tasks that may specifically be around testing
Daily ScrumDiscuss prior day work and plan for that day
Gets at least a daily opportunity to discuss impediments with other bteam members
Proactively find opportunities to collaborate with other team members
2/4/2014
13
RetrospectiveDiscuss
Testing pain points
Quality issuesQuality issues
Quality improvements
Identify Action items
SprintTesting related activities
Offer assistance wherever possible
Testing in parallel to developmentFast Feedback
Collaborate with other team members and teams
2/4/2014
14
TESTERS’ CONTRIBUTION IN ARTIFACTS
Product BacklogAssist the PO with the requirement and acceptance criteria
Identify user storiesIdentify user stories
Discuss test scenarios with the PO To add clarity
To determine testability of the requirement
2/4/2014
15
Sprint BacklogWork 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
IdentifyIdentifyTest scenarios
Testing related tasks
Product IncrementAs a team
Demonstrate the “DONE” work
Gather feedback for the “DONE” work from the stakeholders/customers
2/4/2014
16
DEFECT MANAGEMENT
Agile Testing = Defect Prevention
2/4/2014
17
What do you do with bugs?Fix the defects instead of managing them
Shippable vs Un shippable bugsShippable vs. Un‐shippable bugsUn‐shippable bugs means Undone work
Communicate to your PO Help understand criticality
Determine next steps
METRICS THAT MATTER
2/4/2014
18
WHAT BEHAVIOR IS THIS DRIVING??
HAWTHORNE EFFECT
2/4/2014
19
Metrics to considerMetric 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 oversprints
Development Team
Release Burndown To forecast feature completion based on team’s historical velocity over sprints
Development Team, Stakeholders, Customers
DOCUMENTATION – WHAT MATTERS??
2/4/2014
20
What to Document??Help Documents/User Manuals
Deployment/Maintenance Documents
Technical Documentation – details can be gathered from the code
Definition of Done
Other documents that are typically produced – PBI, User Story, Test cases, Bugs, Design specifications
do ‘Just Enough Documentation’
TO CONCLUDE
2/4/2014
21
Common Myths about Agile TestingNo detailed requirement documentation
No dedicated testing timeg
Automation Is the only way to get faster feedback
Agile testing is NOT possible with out it
Quality of the product is Tester’s responsibility
Testing in parallel to development is NOT possible
What is NOT Agile Testing??Quality and Testing owned by Test specialists
SeparateSeparate Verification & Validation phase
Bug fix phase
Pre release phase
Independent teamsAutomation
Regression
System
Performance
2/4/2014
22
My favorite reads and referencesAgile Testing: A Practical Guide for Testers and Agile Teams‐ Lisa Crispin & Janet Gregory
Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design –James Whittaker
Exploratory Testing Explained – James Bach
http://testobsessed.com/ ‐ Elisabeth Hendrickson
http://gojko net/ Gojko Adzichttp://gojko.net/‐ Gojko Adzic
Behavior Driven Development‐ Dan North
Google images for graphics used in the presentation
QUESTIONS????
2/4/2014
23
PRADEEPA NARAYANASWAMY@NPRADEEPA
