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

Blog

Agile Testing

Accelerate Your Development Speed – Built In Quality

“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 makes quality 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 Zero Bugs approach, you typically have the overhead and increasing cost of fix, 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 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 the 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.

Read More »
Agile Testing

Test-First Reading List

ATDD (Acceptance Test Driven Design /Development) / BDD (Behavior Driven Development) / SBE (Specification by Example) Step Away from the Tools | Liz Keogh, lunivore

Read More »
Subscribe for Email Updates:

Most New:

Categories:

Tags:

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

Contact Us

Request for additional information and prices

This website uses Cookies to provide a better experience
Shopping cart