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:



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

Contact Us

Request for additional information and prices

This website uses Cookies to provide a better experience
Shopping cart