Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

Accelerate Your Development Speed – Built In Quality

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

“Inspection does not improve the quality, nor guarantee quality. The inspection is too late. The quality, good or bad, is already in the product. Quality cannot be inspected into a product or service; it must be built into it.” – W. Edwards Deming.

A big number of bugs that are discovered in testing processes are easy to prevent. The fact that such bugs are discovered at the testing stage, which is usually at the end of the process, shows that the developers did not perform primary quality check of their work. This wastes the time of both testers and developers, reduces motivation and efficiency, and slows development. The costs go up significantly as a bug moves through traditional SDLC. For example, IBM estimates that if a bug costs $100 to fix in the Gathering Requirements phase, it would be $1,500 in the QA testing phase and $10,000 once in Production.

While we can’t expect to test everything and go our entire lives deploying a product that’s 100% error-free, we can make strides to safeguard software as best we can. Built-In Quality is a core principle of the Lean-Agile mindset. It helps avoid the cost of delays associated with the recall, rework, and defect fixing. The Built-In Quality philosophy applies Systems Thinking to optimize the system, ensuring a fast flow across the entire value stream, and making the quality of everyone’s job. Built-In Quality practices ensure that each solution element, at every increment, meets appropriate quality standards throughout development.

One way to drive forward Built-In Quality is to adopt the Zero Bugs approach.

Without the Zero Bugs approach, you typically have the overhead and increasing cost of fixing, as well as a culture in which people are used to bugs being a standard part of their environment which only makes the backlog of bugs grow (the broken window theory).

Zero Bugs Approach means applying a policy where the team keeps a very low (optimally zero)  threshold of open bugs. Once the threshold is reached, the team “Stops the line” and fixes the bug(s). Developers and Testers are pairing and therefore part of the bugs isn’t even reported in the bugs management tool and is fixed immediately. There is no Severity indication as a bug is a bug. Once you implement the Zero Bugs approach, you will no longer have to manage and prioritize a never-ending backlog of bugs. </

Progression bugs, which are related to new functionality, are fixed immediately as part of the Story Definition of Done. Regression bugs are negotiated with the Product Owner who decides whether to fix the issue or to obsolete it. If the fix doesn’t risk the iteration, the bug will be fixed immediately. If it might risk the iteration, then the PO prioritizes the bug vs. the team’s backlog,  and the bug will be fixed at the latest as a top priority of the next iteration.

The Zero Bugs approach is just one of many ways to install a Built-In Quality culture and to shift left quality awareness.

AgileSparks offers a 1-day Built In Quality course for tech leads that covers how leading software companies are changing their approach to quality, in order to achieve speed and continuous delivery. This course pushes the boundaries of the quality mindset and challenges the thinking about quality ownership within the team.

Subscribe for Email Updates:

Categories:

Tags:

Continuous Delivery
Agile Product Ownership
Value Streams
Enterprise DevOps
Risk-aware Product Development
Certification
The Agile Coach
QA
predictability
Process Improvement
ATDD vs. BDD
A Kanban System for Software Engineering
Lean-Agile Software Development
Jira admin
Daily Scrum
Applying Agile Methodology
SA
Presentation
GanttBan
SAFe
Webinar
RTE
Code
EOS®
Scrum.org
Manage Budget Creation
ALM Tools
Self-organization
Managing Projects
Rapid RTC
RSA
Risk Management on Agile Projects
Legacy Code
TDD
Agile Marketing
Agile Techniques
Agile Release Planning
Portfolio for Jira
Amdocs
Professional Scrum with Kanban
Coaching Agile Teams
Agile Outsourcing
Test Driven Development
Hybrid Work
Product Management
System Integration Environments
RTE Role
Agile Project Management
Scrum and XP
Keith Sawyer
SAFe DevOps
Certified SAFe
Scaled Agile Framework
Lean Agile Organization
Continuous Planning
Lean Startup
Continuous Deployment
Kanban Basics
Advanced Roadmaps
System Archetypes
agileisrael
Elastic Leadership
speed at scale
Agile for Embedded Systems
Agile Delivery
Scrum Master
Kanban Kickstart Example
Professional Scrum Product Owner
Agile Testing Practices
Nexus vs SAFe
Professional Scrum Master
Software Development
System Team
Spotify
Jira
Frameworks
WIP
Software Development Estimation
Acceptance Test-Driven Development
Agile Program
Lean Software Development
Reading List
Agile Exercises
An Appreciative Retrospective
Large Scale Scrum
ScrumMaster Tales
Video
Agile Project
Systems Thinking
Sprint Planning
Tools
User stories
Iterative Incremental Development
Agile Community
Limiting Work in Progress
Lean and Agile Principles and Practices
Agile Risk Management
Jira Plans
Introduction to Test Driven Development
Lean-Agile Budgeting
Scrum Guide
chatgpt
Atlassian
SAFe Release Planning
Continuous Integration
Games and Exercises
Releases Using Lean
Kanban 101
Agile Contracts Best Practices
Quality Assurance
Agile Israel Events
Achieve Business Agility
Lean Risk Management
LPM
Agile Israel
Risk Management in Kanban
Agile Basics
SPC
POPM
Entrepreneurial Operating System®
Release Train Engineer
Managing Risk on Agile Projects
IT Operations
AI
Nexus
Implementing SAFe
Agile India
lean agile change management
Lean Budgeting
NIT
Agile Games and Exercises
Sprint Retrospectives
Kaizen
Scrum With Kanban
Business Agility
LAB
Lean Agile Basics
Introduction to ATDD
Pomodoro Technique
Jira Cloud
Perfection Game
Change Management
Program Increment
Lean and Agile Techniques
Atlaassian
Agile Release Management
Agile and DevOps Journey
Artificial Intelligence
Agility
Effective Agile Retrospectives
Kanban
Scrum
Nexus and SAFe
Accelerate Value Delivery At Scale
Implementation of Lean and Agile
AgileSparks
Lean Agile Management
Nexus and Kanban
Development Value Streams
Built-In Quality
Agile Games
ATDD
AI Artificial Intelligence
Agile Product Development
Lean Agile Leadership
Agile Development
Scrum Primer
Continuous Improvement
DevOps
PI Objectives
Scrum Master Role
ROI
Principles of Lean-Agile Leadership
Kanban Game
Nexus Integration Team
What Is Kanban
Planning
Kaizen Workshop
PI Planning
Tips
Agile
Agile Mindset
Scrum Values
Covid19
Legacy Enterprise
Slides
Sprint Iteration
ART Success
Engineering Practices
Story Slicing
Operational Value Stream
ARTs
Product Ownership
Lean Agile
speed @ scale
The Kanban Method
BDD
LeSS
Team Flow
Agile Assembly Architecture
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart