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


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 »
Agile Testing

Agile Testing Lecture

More and more organizations want to become more agile these days. When the theory hits the shores of reality, few organizations can get to an idealistic agile feature team that does all testing within sprints, has no need for release-level testing processes, and where everything is fully automated continuous deployment style. Usually the testing organization is in the eye of the storm and perceived as the main bottleneck. In the lecture we will focus on how we manage the testing processes across release lifecycle in complex environments when it is not realistic to finish all required work within a sprint, how to visualize and reduce testing batch sizes within sprints/releases, practical suggestions on how to deal with the testing bottleneck, how to deal with the mindset issues and last, how to run stabilization/hardening periods using Flow-based thinking.

Read More »

Agile Testing Reading List

Agile Testing/QA Reading List Engineering Higher Quality Through Agile Testing Practices The Agile Coach From Quality Assurance to Quality Assistance | Inside Atlassian No QA?

Read More »
Subscribe for Email Updates:

Most New:



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

Contact Us

Request for additional information and prices

This website uses Cookies to provide a better experience
Shopping cart