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:

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