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:

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