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 »

Most New:



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

Contact Us

Request for additional information and prices

This website uses Cookies to provide a better experience
Shopping cart