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:

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