Using Real World Agile Practices in Testing Projects SoftTeC 2010

1. Using Real World Agile Practices in Testing ProjectsSoftTeC 2010 July 3rd Bangalore Shankaranarayanan G A

2. Agenda • Agile Manifesto • Agile Testing Group (ATG) • Agile Testing • Modes of Operation • Challenges and Best Practices – from ATG • Guidelines • Summary • Q&A Mode of Presentation – Spirit of Sports in Testing!

3. The Agile Manifesto • “In AGILE we value… Individuals & interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan • “That is, while there is value in the items on the right, • we value more for the items on the left.”

4. Agile Testing Group Collaborative Creation Definition Focus Areas ATG: Agile Test Group (Practitioners) OPG: Organizational Process Group TPE: Test Process Evangelists

5. Agile Testing Modes of Operation Co-located Teams • Mode 1 – Ideal Agile, • Mode 2 – Separate Integration Test Sprint Distributed Teams • Mode 3 – Parallel Test Sprint • Mode 1B – Ideal Agile Variant

6. regression test acceptance test Agile Testing – Mode 1A– The ideal Mode test issues develop stories daily scrums test stories fix issues Product Backlog Product Backlog sprint retrospective sprint showcase plan sprint select sprint backlog Sprint Backlog Courtesy: reused from tsg®

7. What is this picture about? – One word description Interlock Courtesy: www.nassjograppling.se

8. QA- Dev Interlock Project Context: Storage Domain No Spec Documents Exists; Co-located team – 10-12 members • Why this Practice came into existence? • To bring in clarity on scope for current sprint • Eliminate known risks that could pop-up later in the sprint • It acts like a mutual sign-off for accountability • To reduce dismissed/ invalid defects percentage • Attributes of this Practice: • QA initiates a 1 hour Face-to-Face meet – week 1; • Multiple interlocks per QA if required • Initiated and concluded through emails • Tracked on xl worksheet by PM/TM (Scrum Master) • Developer  end user scenarios  includes in design & unit tests • Tester  Scopes test approach test bed setup  test cases

9. Agile Testing – Mode 2 Integration Test Sprints Final Regression Test NFT (e.g. security, performance) Acceptance Test Test Prep Integration Test Dev Sprint 1 Dev Sprint 2 Dev Sprint 3 Test Sprint Dev Sprint 4 Dev Sprint 5 Test Story V2 Regression Test v2 Develop stories v2 OPERATIONAL SOFTWARE Courtesy: reused from tsg®

10. What catchphrase you can think of? Red Flag Courtesy: www.nassjograppling.se

11. QA Confidence Score Project Context: Storage Domain Applied to System Test Sprints; Co-located team – 16 members; QA: Dev =1:1 • Why this Practice came into existence? • Defect density was not declining • To Reduce re-opened defects percentage • Re-testing was very cumbersome due to large compatibility matrix required • To monitor Unstable Features • Attributes of this Practice: • Scoring by QA/Testers - Weekly • Development lead uses to analyze stability of the product: • Red / Yellow Flag = Revert Changes + RCA • Green Flag = Freeze Changes

12. QA Confidence Score - Usage

13. Agile Testing – Mode 3 – Parallel Test Sprint Developing v2 (includes tdd + continuous regression test) Debugging v1» v1.1 v1 v2 Sprint 1 Sprint 2 Spri V1.1 V2.1 Test 1 Test 2 T Specialist Testing (e.g. security, performance) OPERATIONAL SOFTWARE Test Prep v1 Story Test V1 Story Re-test V1.1 Acceptance Test Regression Test Courtesy: reused from tsg®

14. You really don’t know until its delivered! Code Courtesy: http://static.cricketnext.com

15. Test Impact Summary with Check-In email Project Context: SaaS model, HCM Domain Large Multi-Location Distributed Teams; USA, India, Russia, China • Why this Practice came into existence? • Direct and frequent interaction was not feasible • To reduce the dismissed defect percentage • Featuresmissed by testers • Missed verification of bug fixed • Attributes of this Practice: • A web based UI integrated with the CM tool sends email to relevant testers/distribution list • Developer highlights the details and areas of code change with impacted functionalities • It also contains testing scope and defects fix details

16. Check-In email @ tester’s inbox • Generated by Check in Email Generator: • Subject: check in: [main][Module ABC] Performance Enhancements to Module ABC - The enhancements/refactoring introduced will improve the performance in the following areas of ABC Module for the customers. • Check in Information: • Message identifier: Performance Enhancements to Module ABC - The enhancements/refactoring introduced will improve the performance in the following areas of ABC Module for the customers. • When Opening a Module ABC Manager Form • When Opening Executive Review Entries For a Module ABC Template • Location: Main • Product area: Module ABC • Bug #: ABC-1XX4 • <http://jira.projectabc.com/browse/ABC-1XX4> — ABC forms take 5-10 minutes to load and this is unacceptable to customer Impacted Test Scenarios: 1) Open a Variable Manager Form with large number of entries and/or huge configuration XML and notice the improvement in response time by more than half. 2) Open Executive Reviwe for ABC Template with large number of forms/entries and notice the improvement in response time by many times. 3) Testing will also be collaborated with Performance Team with daily runs of ABC LoadRunner Test Cases and bench marking of the results. Reviewed By: Project Manager, Peer, Module Lead (for XXXX Refactoring part) Subversion Revisions: 8XX1X <http://cvs.project.com/viewXX/svn?vXXXeX=XXv&revXXon=8XXX4> Changed Paths in Revision 8XX4X Details: This contains all the paths of code where changes were made.

17. regression test acceptance test Agile Testing – Mode 1B – The ideal Mode Variant test issues develop stories daily scrums test stories fix issues Product Backlog Product Backlog sprint retrospective sprint showcase plan sprint select sprint backlog Sprint Backlog Courtesy: reused from tsg®

18. Analogy to Agile Teams? Collaboration Courtesy: http://www.carsonnewmaneagles.com

19. Collaboration Tool for Distributed Teams Project Context: e-commerce Application Distributed Teams - USA, India, 35 members, • Why this Practice came into existence? • Bloated inboxes - email was not effective for search, accessibility and inbox space optimization. • static documents or document management systems are difficult to update, track, and access, and they prevent simultaneous access • Support various media sources. • Attributes of this Practice: • Onsite-offshore communication medium • A dashboard to reflect the overall Test Health • Take notes during their stand ups and discussions in sprint meetings • No technical details are conveyed in emails and hence this tool acts as knowledge base for the sprint

20. Collaboration Tool Screens

21. Agile Testing Guideline – a Glimpse

22. Summary • QA- Dev Interlock • QA Confidence Score • Test Impact Summary with Check-In email • Collaboration Tool for distributed teams Take Charge, Lead the Change Be Creative Problem Solvers! “Are you a Creative Agile Tester?”

23. Successful Customers Happy People Innovative Solutions Our Mission Shankaranarayanan G A Shankaranarayanan_ga@mindtree.com www.mindtree.com www.mindtree.com © 2010 MindTree Limited