Presentation is loading. Please wait.

Presentation is loading. Please wait.

© 2008 MindTree Consulting© 2010 MindTree Limited CONFIDENTIAL: For limited circulation only Using Real World Agile Practices in Testing Projects SoftTeC.

Similar presentations


Presentation on theme: "© 2008 MindTree Consulting© 2010 MindTree Limited CONFIDENTIAL: For limited circulation only Using Real World Agile Practices in Testing Projects SoftTeC."— Presentation transcript:

1 © 2008 MindTree Consulting© 2010 MindTree Limited CONFIDENTIAL: For limited circulation only Using Real World Agile Practices in Testing Projects SoftTeC 2010 July 3 rd Bangalore Shankaranarayanan G A

2 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only 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! Slide 2

3 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only The Agile Manifesto “That is, while there is value in the items on the right, we value more for the items on the left.” comprehensive documentation processes and tools over contract negotiation following a plan over “In AGILE we value… Working software Responding to change Customer collaboration Individuals & interactions Slide 3

4 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only Agile Testing Group Slide 4 ATG TPE OPG ATG: Agile Test Group (Practitioners) OPG: Organizational Process Group TPE: Test Process Evangelists Collaborative Creation Key Focus Testing Guidelines Tester Focus Templates & Checklists Scrum Architecture Definition Focus Areas

5 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only Agile Testing Modes of Operation Co-located Teams 1. Mode 1 – Ideal Agile, 2. Mode 2 – Separate Integration Test Sprint Distributed Teams 3. Mode 3 – Parallel Test Sprint 4. Mode 1B – Ideal Agile Variant Slide 5

6 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only Agile Testing – Mode 1A– The ideal Mode sprint showcase fix issues daily scrums Sprint Backlog plan sprint Product Backlog develop stories regression test test stories acceptance test select sprint backlog sprint retrospective test issues 1A: Co-Located Teams Testing within the same sprint Courtesy: reused from tsg® Slide 6

7 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only What is this picture about? – One word description Interlock Courtesy: Slide 7

8 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only QA- Dev Interlock Slide 8 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 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 s  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 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 s  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 Week 1Week 2Week 3Week 4 Project Context: Storage Domain No Spec Documents Exists; Co-located team – members Project Context: Storage Domain No Spec Documents Exists; Co-located team – members

9 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only Dev Sprint 4 Dev Sprint 5 Agile Testing – Mode 2 Integration Test Sprints Dev Sprint 1 Dev Sprint 2 Dev Sprint 3 Test Sprint OPERATIONALSOFTWARE TestStoryV2 Develop stories v2 RegressionTestv2 FinalRegressionTest AcceptanceTest TestPrep NFT (e.g. security, performance) Integration Test Courtesy: reused from tsg® Slide 9

10 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only What catchphrase you can think of? Slide 10 Red Flag Courtesy:

11 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only QA Confidence Score Slide 11 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 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 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 Week 1Week 2Week 3Week 4 Project Context: Storage Domain Applied to System Test Sprints; Co-located team – 16 members; QA: Dev =1:1 Project Context: Storage Domain Applied to System Test Sprints; Co-located team – 16 members; QA: Dev =1:1

12 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only QA Confidence Score - Usage Slide 12

13 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only OPERATIONAL SOFTWARE Agile Testing – Mode 3 – Parallel Test Sprint v1 Test 1TTest 2 V1.1 v2 V2.1 RegressionTest AcceptanceTest StoryRe-testV1.1 StoryTestV1 TestPrepv1 Sprint 1SpriSprint 2 SpecialistTesting(e.g. security, performance) Developing v2 (includes tdd + continuous regression regression test) test) Debugging v1» v1.1 Courtesy: reused from tsg® Slide 13

14 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only You really don’t know until its delivered! Code Courtesy: Slide 14

15 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only Test Impact Summary with Check-In Slide 15 Why this Practice came into existence? Direct and frequent interaction was not feasible To reduce the dismissed defect percentage Features missed by testers Missed verification of bug fixed Why this Practice came into existence? Direct and frequent interaction was not feasible To reduce the dismissed defect percentage Features missed by testers Missed verification of bug fixed Attributes of this Practice: A web based UI integrated with the CM tool sends 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 Attributes of this Practice: A web based UI integrated with the CM tool sends 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 Week 1Week 2Week 3Week 4 Project Context: SaaS model, HCM Domain Large Multi-Location Distributed Teams; USA, India, Russia, China Project Context: SaaS model, HCM Domain Large Multi-Location Distributed Teams; USA, India, Russia, China

16 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only Check-In tester’s inbox Slide 16 Generated by Check in 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 — ABC forms take 5-10 minutes to load and this is unacceptable to customer Generated by Check in 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 — 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 Changed Paths in Revision 8XX4X Details: This contains all the paths of code where changes were made. 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 Changed Paths in Revision 8XX4X Details: This contains all the paths of code where changes were made.

17 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only Agile Testing – Mode 1B – The ideal Mode Variant sprint showcase fix issues daily scrums Sprint Backlog plan sprint Product Backlog develop stories regression test test stories acceptance test select sprint backlog sprint retrospective test issues 1B: Distributed Teams Testing within the same sprint Courtesy: reused from tsg® Slide 17

18 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only Analogy to Agile Teams? Collaboration Courtesy: Slide 18

19 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only Collaboration Tool for Distributed Teams Slide 19 Why this Practice came into existence? Bloated inboxes - 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. Why this Practice came into existence? Bloated inboxes - 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 s and hence this tool acts as knowledge base for the sprint 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 s and hence this tool acts as knowledge base for the sprint Project Context: e-commerce Application Distributed Teams - USA, India, 35 members, Project Context: e-commerce Application Distributed Teams - USA, India, 35 members, Week 1Week 2Week 3Week 4

20 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only Collaboration Tool Screens Slide 20

21 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only Agile Testing Guideline – a Glimpse Slide 21 Release Planning Test Planning Bring out Clarity of user stories and Scope of Testing Define “Doneness” Criteria Identify Metrics to be monitored Sprint Planning Expand the understanding of stories focusing on End user and non-functional stories Keep Quality Debt to Zero Sprint Execution Ensure “Doneness” Criteria is met. Include both Confirmatory and Exploratory Testing Unearth Quality Risks upfront Metrics Collection Sprint Review Provide QA confidence Score Bring to Table any Quality Debt issues Discuss any defect backlog that requires immediate fix Test Metrics Analysis Retrospective Identify Testing Related Obstacles and how to overcome them Discuss and Initiate any Process Improvements Wait Times Proactively utilize time for next sprint KT and Resource ramp up Initiate Process Improvement, focus on 1 or 2 areas

22 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only Summary 1. QA- Dev Interlock 2. QA Confidence Score 3. Test Impact Summary with Check-In 4. Collaboration Tool for distributed teams Take Charge, Lead the Change Be Creative Problem Solvers! “Are you a Creative Agile Tester?” Slide 22

23 © 2010 MindTree Limited CONFIDENTIAL: For limited circulation only Slide 23 Successful Customers Happy People Innovative Solutions Successful Customers Happy People Innovative Solutions Our Mission Shankaranarayanan G A © 2010 MindTree Limited


Download ppt "© 2008 MindTree Consulting© 2010 MindTree Limited CONFIDENTIAL: For limited circulation only Using Real World Agile Practices in Testing Projects SoftTeC."

Similar presentations


Ads by Google