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 »

Most New:



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

Need more information?

Please leave your details and one of our advisors will contact you. Want to group tickets?


to our new website


to our new website

This website uses Cookies to provide a better experience
Shopping cart