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 »
Agile Testing

Agile Testing Lecture

More and more organizations want to become more agile these days. When the theory hits the shores of reality, few organizations can get to an idealistic agile feature team that does all testing within sprints, has no need for release-level testing processes, and where everything is fully automated continuous deployment style. Usually the testing organization is in the eye of the storm and perceived as the main bottleneck. In the lecture we will focus on how we manage the testing processes across release lifecycle in complex environments when it is not realistic to finish all required work within a sprint, how to visualize and reduce testing batch sizes within sprints/releases, practical suggestions on how to deal with the testing bottleneck, how to deal with the mindset issues and last, how to run stabilization/hardening periods using Flow-based thinking.

Read More »
Agile

Agile Testing Reading List

Agile Testing/QA Reading List Engineering Higher Quality Through Agile Testing Practices The Agile Coach From Quality Assurance to Quality Assistance | Inside Atlassian No QA?

Read More »

Most New:

Categories:

Tags:

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

WELCOME

to our new website

WELCOME

to our new website

This website uses Cookies to provide a better experience
Shopping cart