Challenges with measuring quality for agile distributed research type project


Published on

Research type product development, Distributed Agile team , Quality Assurance

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Challenges with measuring quality for agile distributed research type project

  1. 1. Challenges with Quality Assurance for Distributed Agile team, research project Chandan lal patary
  2. 2. Agenda • Problem • Pathway • Solution • Q&A 2
  3. 3. Dept.-Collaborative Production Management (CPM)– crossing the chasm – A case study px?country=IN
  4. 4. Collaborative Production Management Suite 4
  5. 5. Initial Challenges  Quality has to be built in, not bolted on and how to convert the statement into practice?  Research type project are different in nature  “Addressing quality early to prevent defects reduces the need to find and fix them later” was missing  Quality assurance for Legacy system 5
  6. 6. Product Development Org Structure 6
  7. 7. Quality “A” Team Structure  Sustainable test team structure with product portfolio  Testers identify with their product and not their role  Test specialists always provide most value to our agile project by looking for novel or unexpected risk  Encourage pair testing Team is building An “agile testing mind-set” which is  Customer-focused,  Results-oriented,  Craftsman-like,  Collaborative,  Creative,  Eager to learn, and passionate about delivering business value in a timely manner 7
  8. 8. Juran’s Principles and application for TQM “Quality cannot be tested in” “conformance to requirements” – Crosby “fitness for use” - Juran 8
  9. 9. Reduce cycle time  A culture of excellence  Standardizing the process  Automation can cut delivery times and remove some of the mundane, repetitive work, leaving your skilled resources to focus on the more difficult and valuable tasks. 9
  10. 10. Waste reduction  Lean principles, the right way to tackle bugs is by preventing them to appear altogether, and by eliminating them as soon as possible.  insufficient testing, leading to avoidable process repetition  Use automation to identify most of the waste Toyota manufacturing process Shigeo Shingo suggests that we engineer our processes to prevent defects rather than focusing on processes to find defects. This is a critical part of lean thinking that bears repeating: Use processes that prevent defects rather than relying on those that try to find them. 10
  11. 11. Smells  Smells are a good way to diagnose what is wrong with the current way things are done  Testing is still last? It has to change 11
  12. 12. Acceptance Test Driven Development • We should have well-defined, realistic, documented, agreed-upon objectives for our testing process? • work with the business stakeholders to understand their real needs and concerns 12
  13. 13. Type of test  Combine Risks based test strategy with maintainable automated regression testing at system test level  Extreme Programming (XP) has a mantra called “test everything that could possibly break.”  Create test plan with a “Big picture” and with systemic view 13
  14. 14. Quality Process Flow 14
  15. 15. Risks Based Test Strategy  Testing is all about risk  Risks based test strategy helps because the focus is on the important areas and execution is on priority order  Risks based testing supports increased quality, increased productivity and flexibility 15
  16. 16. Orthogonal Defect Classification  Root cause and improvement cycle 16 continuous
  17. 17. Hybrid Product Development Process  Improved predictability for decision making 17
  18. 18. Information radiator for Metrics and Measurement Dashboard will talk how much backlog items tested and quality of the deliverables ? How many not yet tested? 18
  19. 19. What is Agile Testing ? 19
  20. 20. Testing skills • Agile moved development from process oriented to people oriented. • Writing code, writing script • Extreme collaboration • Domain competency • Act like customer, write acceptance test • Don’t behave like test engineer, think from quality improvement point of view. • The role of QA is not „police“, and testing goes beyond „pass“ or „fail”. • 10,000 hour rule: the key to success in any field is to practice a specific activity for 10,000 hours, an idea based on a study by Anders Ericsson 20
  21. 21. Testing Issues with Agile project 21
  22. 22. Reduction of defect from Field “0” Zero defect target from field 22
  23. 23. Take Away!  Communication between tester, customer and designer than to maintain independence of the test team  Automated testing is at the heart of agility  Testing is not one person’s job; it’s the responsibility of the whole team  Run tests at multiple levels  Release often-Continuous integration-TDDContinuous improve Quality is a Journey, not a Destination 23
  24. 24. Q&A 24