Skip to main content

Defect Leakage

Defect leakage occurs on the Customer or End User side after the delivery of the application.

Once the application has been released to the client, if the end user gets any kind of defect using the application, it is called "Defect leakage".

Formula for Defect Leakage:

Defect Leakage = Number of Defect found during next phase / ( Number of Defects found during testing + Number of Defects found during next phase) * 100

For Example, During the UAT production site, 50 defects were detected by the end users and 150 defects were detected throughout the QA process, including both the test site and the production site. Therefore, the defect leakage would be:

Defect Leakage = (50/150)*100

Defect Leakage =33 %

Reasons for Defect Leakage:

  • Absence of stringent test cases walkthrough and review process.
  • Environment differences.
  • Missing test cases to cover appropriate condition.
  • Poorly designed test case due to misunderstood requirements.
  • Incorrect deployment in UAT or production.
  • Use of incorrect test data.

The ways to avoid high-leakage defects are:
  • Test the product like an environment in the real world.
  • Verify sensitive content and fields
  • Choose a specific area, and perform a detailed analysis and test.
  • Find components which are susceptible to high leakage of defects.
  • Perform rigorous testing on tiniest components.
  • Consider a rewrite if things are truly bad.
  • Take a closer look at the whole system.

For example for the project running in Sprint we can find the defect leakage as below:

Defect Leakage = (Post sprint defect count */ Defect detected during sprint) *100



Comments

Post a Comment

Popular posts from this blog

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - archite
Post a Comment
Read more

Lessons learned from sprint retrospective meeting

Scenario: Team Missed Sprint Goals Challenge: A development team consistently missed its sprint goals, leading to frustration and a drop in morale. Team members felt overwhelmed by the workload and struggled to communicate effectively. Retrospective Insights: During the retrospective, team members openly discussed their challenges and frustrations. They identified bottlenecks in communication, unclear priorities, and unrealistic expectations. The team realized that individual workloads were not evenly distributed, causing burnout for some members. Lessons Learned: Effective Communication Matters: The team recognized the importance of clear communication. They committed to regular stand-up meetings, where everyone shared progress, blockers, and priorities. Balancing Workloads: The retrospective highlighted the need to distribute tasks more evenly. They decided to monitor workloads and adjust assignments accordingly. Setting Realistic Goals: The team acknowledged that setting achievable
Post a Comment
Read more

Risk Register

A project risk register is a tool project managers use to track and monitor any risks that might impact their projects. Risk management is a vital component of project management because it's how you proactively combat potential problems or setbacks. Risk Description Impact Risk Response Risk Level Risk Owner Automation Testing Software licence delay Delay in starting testing and project schedule impact As we have one licence. Planned to start automation testing in 2 shifts. Planned to get one more licence in 2 weeks’ time. High IT team Frequent Disruption in dependency API services Delay in development of integration and unit testing Dependency API service is down, and the team is working on resolving the issue. Continuously working with API team High External Team/ Project Manager There is chance of new requir
Post a Comment
Read more