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

Popular posts from this blog

Delivering a project within budget

 Here are some tips for delivering a project within budget: Set a realistic budget Define the project's scope and necessary resources, and create a budget that's realistic. Cost estimate Segment the project into smaller tasks and milestones to plan how to use resources and provide clarity. Divide the project plan Break down the project into tasks to avoid late deliverables and over-budget projects. Monitor progress Regularly track the project's progress to identify and prevent cost overruns. Use progress reports to compare actual costs to the budget. Anticipate and revise changes Communicate with stakeholders to identify and assess risks, and assign owners to each risk. Consider different scenarios Estimation can be difficult for complex projects with many potential outcomes. Tracking: Tracking time spent on tasks, Tracking expenses per project, and Using project management software. Use Historical Data Your project is likely not the first to try and accomplish a specific o...

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...

Bucket System project estimation

 The Bucket System is an Agile estimation technique that uses predefined buckets to group tasks or user stories by size, complexity, or effort.  Each bucket represents an estimate range, such as small, medium, or large.  The Bucket System is a group activity that helps align the team's understanding of work effort and complexity.  It's a good technique for quickly estimating a large number of items with a medium to large group of people. The effort of small, medium, or large bucket size arrived by team based on T-shirt sizing, PERT estimation or Planning Poker. Each bucket represents a level or an estimate range (e.g., small, medium, large). The team compares user stories to one another and places them into the appropriate buckets. This process is a group activity, promoting discussions and aligning the team's understanding of work complexity and effort. To use the Bucket System: Set up a row of cards, or buckets, with values in the Fibonacci sequence or other metho...