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

Most New:

Categories:

Tags:

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