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 »

Most New:



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

Contact Us

Request for additional information and prices

This website uses Cookies to provide a better experience
Shopping cart