Lean testing approach for cycle time reduction

1,530 views

Published on

Lean software testing approach for cycle time reduction

Published in: Software
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,530
On SlideShare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
23
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Lean testing approach for cycle time reduction

  1. 1. Lean Testing approach for Execution Cycle Time Reduction CHANDAN P
  2. 2. Purpose and Objectives  About Lean thinking  Systemic thinking  Lean Test Team members  Cycle time reduction steps  Incremental testing  Requirement Engineering  Gamification  Optimized the whole flow  Impact based testing  Visual dashboard  Result and collaboration
  3. 3. What are the identified factors for lean thinking?
  4. 4. System thinking
  5. 5. How lean test engineers should think?
  6. 6. What are the steps for cycle time reduction?
  7. 7. Build and test in incremental way.  What to Build? - Build-Show- change……..What to build? …….. Cycle goes on
  8. 8. Four areas to focus  The customer is the starting point. Testing should focus on adding the best value to all stakeholders. E.g. set priorities based on a product risk analysis.  Improve your test processes. Use models and methods as reference, but not as target. Use what suits best to the organization’s own processes.  Ensure teamwork. Not only within the test team but also with the other members within your projects.  Collecting and analyzing data. Improving the test process cannot be done without measuring the effect of the changes made in the process. Keeping metrics, analyzing them and taking action should become a company’s second nature.
  9. 9. Requirement Engineering:  Requirement management is a engineering subject which need to handle with care
  10. 10. Test Team Structure  Flat team with poly skill team members is more agile.
  11. 11. Leaderboard for Gamification specific for a team
  12. 12. Optimizing the flow
  13. 13. Impact based testing  Why to run all the test cases? Only affected area has to cover.
  14. 14. Project dashboard for decision making
  15. 15. Factors influences cost reduction
  16. 16. Types testing vs cost effect
  17. 17. Result
  18. 18. Extreme collaboration
  19. 19. Communication Barrier need to remove for speed
  20. 20. Key Takeaway
  21. 21. Q&A

×