Lean testing
Download as PPTX, PDF0 likes584 views
The document discusses lean software testing approaches to increase customer value and reduce execution cycle times. It describes implementing a lean mindset to optimize workflow and remove impediments to reduce production to release cycles from 15 to 10 months. This includes empowering teams, using risk-based and impact-based testing strategies, focusing on areas with the most changes, and creating dashboards to provide visibility. The goal is to improve defect removal efficiency to over 90% and reduce regression cycle times by 50% through these lean testing approaches.
Lean testing
- 1. Lean Software Testing for Increasing Customer Value and Reducing Execution Cycle Time Chandan patary Agile Coach , Global Program Manager, ABB
- 2. Abstract: • Is our test team doing the right work ? • How can we achieve below target? • Reduce cycle time from 15 months production to release cycle to 10 months • Improve Defect removal efficiency from 75% to greater than 90% • Reduce regression cycle time by 50% • What we have done? • Lean Mindset and Think Beyond • Flow optimization and Cycle time reduction steps • Empowered team • Requirement Engineering • Increase engagement through gamification • Risks based test strategy • Team dashboard • Coverage , have we done enough? • Impediments and remove the blockings.
- 3. Change our thinking process?
- 4. Think Beyond • See the whole. • Focus only on value adding activities • Constant customer Value generation
- 5. How can we help Stream to flow and flow…. • Constantly optimize the flow , remove the impediments from the system • Make several tasks parallel and do constant handshake
- 7. What did we do to reduce the cycle time?
- 8. Empowered Team to take action
- 9. Gamifying work: -How we have implemented Fun, play and work
- 10. Requirement Engineering: Are we solving the right puzzle ?
- 11. Expectation from Our Lean test engineers
- 12. Impact Based Testing to reduce regression cycle time • Where are the most changes? get the data from code churn report? • Assess the areas impacted and functionalities? • Concentrate testing towards that area
- 13. Quality Coverage: Have we done enough?
- 14. Dashboard: Are we able to see everything ?
- 16. Key Takeaway
- 17. Source : a) http://www.cutorcopy.com/developer-vs-tester/ b) http://pacgenesis.com/blog/over-the-wall/ c) https://stevenbarbour.wikispaces.com/Optical+Illusions d) http://themarketplace.net.au/about_questions.php e) http://www.leansimulations.org/2011/08/video-how-to-read-value-stream- map.html f) Movie 300 g) http://angry-birds.en.softonic.com/ h) http://www.gobizkorea.com/catalog/product_view.jsp?blogId=mediana&objId=759251
- 18. Q & A