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 »
Subscribe for Email Updates:

Most New:

Categories:

Tags:

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