Close this search box.
Close this search box.
Close this search box.


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 Marketing

What Is Agile Marketing

This ISN’T Agile Marketing

First, a couple of clarifications and myth-busting. Agile Marketing isn’t reactive marketing. Agile Marketing isn’t about how you react in a Marketing/PR crisis (ask United about those) or real-time opportunity (you can ask Oreo about those). I don’t mean that you can not/shouldn’t deal with those when you’re doing Agile Marketing, but it isn’t what Agile Marketing is about.

Agile Marketing also isn’t “We just get things done without any real process.” Being super-responsive and saying “yes we can” all the time isn’t Agile Marketing. (Especially if it means unsustainable pace).

Finally, Agile Marketing also isn’t Scrum, Daily Scrums/Standups, Sprints, Scrum Masters, Kanban Boards. It

Read More »

Continuous Integration Best Practices in Agile Environments – Ben Reich

Continuous integration is always an issue when implementing agile practices. As with most agile practices there is a vast body of knowledge around best practices in continuous integration. We will discuss the issues surrounding CI and its implementation in different types of scenarios. We will cover different planning techniques and organizational solutions for solving these issues.

Read More »
Breadth – Going Wider Toward Business Agility

Continuous Delivery / DevOps Reading List

Let’s deploy to production – YouTube Transforming Software Development – YouTube What Team Structure is Right for DevOps to Flourish? | Matthew Skelton Powering

Read More »
Subscribe for Email Updates:

Most New:



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

Contact Us

Request for additional information and prices

This website uses Cookies to provide a better experience
Shopping cart