We re Moving to Agile: What Are Our Testers Going to Do?

Transcription

1 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

2 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 Scrum.org, All Rights Reserved 2

3 Quick Guidelines Your microphones will be muted throughout We encourage questions and discussion! Tweet your #ScrumPulse You can also type your questions and comments into the webinar questions box: Scrum.org, All Rights Reserved 3

4 About Pradeepa Narayanaswamy 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 Scrum.org, All Rights Reserved 4

5 Agenda What is Agile Testing? Agile Testing Goals & Mindset Testers Contribution in Events & Artifacts Defect Management Metrics Documentation Scrum.org, All Rights Reserved 5

6 What is Agile Testing??? 6

7 Agile Testing Asynchronous Done in Parallel with Development Not Possible without Collaboration Incremental Testing Feedback Guides Development on a Daily Basis

8 Testing is a Design Activity Test Business Requirement Potentially Shippable Product Requirement Code

9 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

10 Agile Testing Goals Quality = Acceptance Criteria + Definition of Done Quality is Measured by Customer Feedback Fix Defects instead of Managing them

11 Avoiding Mini-Waterfall

12 Agile Testing Mindset

13 Collaboration is Inevitable Stakeholders

14 Team Owns Quality

15 Planning is Always Ongoing

16 Communication is Critical

17 Different Modes of Communication Most Preferred CENTARE.COM Least Preferred

18 Requirements are NOT set in Stone!!

19 Cross-Functional Teams Depth of Expertise

20 Are they Cross-Functional?

21 Typical Metrics Matter Least

22 Keep an Eye on the BIG Picture

23 Testing to Aid Fast Feedback

24 Failure is OK, Fail Fast & Learn

25 Testers Contribution in Events

26 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

27 Backlog Refinement Understand Feature Technical Details Define & Refine Acceptance criteria Effort Estimation Testing Items are Included Test Related Intricacies may be Discussed/Understood

28 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

29 Retrospective Discuss Testing pain points Quality Issues Quality Improvements Identify Action Items

30 Sprint/Iteration Testing Related Activities Offer Assistance wherever Possible Learning and Mentoring opportunity Testing in Parallel to Development Fast Feedback

31 Testers Contribution in Artifacts

32 Backlog Assist the Team with the User Stories and Acceptance Criteria Discuss Test Scenarios with the Team To Add Clarity To Determine Testability

33 Product Increment As a team Demonstrate the DONE work Gather Feedback for the DONE work from the Stakeholders/Customers

34 Defect Management

35 Agile Testing = Defect Prevention

36 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

37 Metrics that Matter!

38 Hawthorne Effect

39 What behavior is this Driving??

40 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

41 Documentation What Matters??

42 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

43 To Conclude

44 What is NOT Agile Testing?? Separate Verification and Validation phase Bug Fix phase Pre-Release phase Independent teams Automation Regression System Performance

45 Testing from Day 1 Defining Behaviors as a Team Pairing between Specialties Creating Testable Task List

46 Recommended Resources 46

47 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

48 Dallas, Texas, USA Thank You! 48

49 Q&A Tweet your #ScrumPulse Or type your questions in the webinar questions box: Scrum.org, All Rights Reserved 49

50 Scrum.org, All Rights Reserved 50

51 Thank You! Scrum.org, All Rights Reserved 51