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:



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

Contact Us

Request for additional information and prices

This website uses Cookies to provide a better experience
Shopping cart