We re Moving to Agile: What Are Our Testers Going to Do? <Discussion of an Agile Testing mindset> A Webcast by Pradeepa Narayanaswamy and Scrum.org Moderated by Ravi Verma
About Scrum Pulse Free monthly Webinar by Scrum.org o Register and view previously recorded webinars at Scrum.org/ScrumPulse o Also available for viewing on our YouTube Channel Youtube.com/scrumdotorg About Scrum.org Improving the profession of software development o Increased focus on empiricism and agility o Continuous delivery of business value o Building trust and respect between business and I.T. 1993-2015 Scrum.org, All Rights Reserved 2
Quick Guidelines Your microphones will be muted throughout We encourage questions and discussion! Tweet your questions: @scrumdotorg, #ScrumPulse You can also type your questions and comments into the webinar questions box: 1993-2015 Scrum.org, All Rights Reserved 3
About Pradeepa Narayanaswamy https://www.linkedin.com/in/pradeepanarayanaswamy pradeepa_n@yahoo.com 16 Years in the Software Development Profession 6 Years Agile Training & Coaching Organizer for DFW Scrum Masters in Computer Applications Enterprise Agile Coach and Trainer 1993-2015 Scrum.org, All Rights Reserved 4
Agenda What is Agile Testing? Agile Testing Goals & Mindset Testers Contribution in Events & Artifacts Defect Management Metrics Documentation 1993-2015 Scrum.org, All Rights Reserved 5
What is Agile Testing??? 6
Agile Testing Asynchronous Done in Parallel with Development Not Possible without Collaboration Incremental Testing Feedback Guides Development on a Daily Basis
Testing is a Design Activity Test Business Requirement Potentially Shippable Product Requirement Code
Agile Testing in a Nut Shell Test Start Testing Specialist Coding Specialist Done Understand the User Story Execute domains Test Writing Emphasis Testing Specialist Coding Specialist Understand mutual domains Testing Specialist How will we build this? Testing Specialist Coding Specialist Code Writing Emphasis How will we test this? Coding Specialist Chad Albrecht
Agile Testing Goals Quality = Acceptance Criteria + Definition of Done Quality is Measured by Customer Feedback Fix Defects instead of Managing them
Avoiding Mini-Waterfall
Agile Testing Mindset
Collaboration is Inevitable Stakeholders
Team Owns Quality
Planning is Always Ongoing
Communication is Critical
Different Modes of Communication Most Preferred CENTARE.COM Least Preferred
Requirements are NOT set in Stone!!
Cross-Functional Teams Depth of Expertise
Are they Cross-Functional?
Typical Metrics Matter Least
Keep an Eye on the BIG Picture
Testing to Aid Fast Feedback
Failure is OK, Fail Fast & Learn
Testers Contribution in Events
Planning Approach the Planning from Testing Perspective Identify Test Scenarios Identify ilities Challenge Technical Discussions from Testing Standpoint Assist Team Identify Tasks that may be Specifically around Testing
Backlog Refinement Understand Feature Technical Details Define & Refine Acceptance criteria Effort Estimation Testing Items are Included Test Related Intricacies may be Discussed/Understood
Daily 15 Minutes Discuss your progress, plan for next 24 hours Gets at least a Daily Opportunity to Discuss Impediments with other Team Members Proactively find Opportunities to Collaborate with Other Team Members
Retrospective Discuss Testing pain points Quality Issues Quality Improvements Identify Action Items
Sprint/Iteration Testing Related Activities Offer Assistance wherever Possible Learning and Mentoring opportunity Testing in Parallel to Development Fast Feedback
Testers Contribution in Artifacts
Backlog Assist the Team with the User Stories and Acceptance Criteria Discuss Test Scenarios with the Team To Add Clarity To Determine Testability
Product Increment As a team Demonstrate the DONE work Gather Feedback for the DONE work from the Stakeholders/Customers
Defect Management
Agile Testing = Defect Prevention
What do you do with the Bugs? Determine Shippability Un-shippable Bugs means Undone Work Communicate to your Product Owner Help Understand Criticality Determine Next Steps
Metrics that Matter!
Hawthorne Effect
What behavior is this Driving??
Metrics to Consider Metric Purpose Audience Working Software To gain review feedback Scrum Team, Stakeholders, Customers Sprint 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 Scrum Team, Stakeholders, Customers
Documentation What Matters??
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 Product Backlog Item, User Story, Exploratory Charters, Test cases do Just Enough Documentation
To Conclude
What is NOT Agile Testing?? Separate Verification and Validation phase Bug Fix phase Pre-Release phase Independent teams Automation Regression System Performance
Testing from Day 1 Defining Behaviors as a Team Pairing between Specialties Creating Testable Task List
Recommended Resources 46
In Summary Test in Parallel to Development Quality is Owned by the Whole Team Testing is NOT the responsibility of just the Testers Testing Feedback guides Development on a Daily Basis 47
https://www.linkedin.com/in/pradeepanarayanaswamy Pradeepa_n@yahoo.com Dallas, Texas, USA Thank You! 48
Q&A Tweet your questions @scrumdotorg, #ScrumPulse Or type your questions in the webinar questions box: 1993-2015 Scrum.org, All Rights Reserved 49
1993-2015 Scrum.org, All Rights Reserved 50
Thank You! Scrum.org/ScrumPulse @scrumdotorg 1993-2015 Scrum.org, All Rights Reserved 51