I have reworked my article against a #test / #qa column on boards and could add some more voices.
https://www.enteresc.net/why-a-test-column-on-boards-is-a-problem/
Why a test column on boards is a problem
I often see on boards columns like “Open”, “Dev” or 'In Progress' (but still just being for developers) and next to them “Test” or “QA.”. And ticket moving through it and handovers happening between columns. Developers stop working once they are done (with a first version) and testers just start once they got the ticket handed over. Sequentially working on it instead of doing it in parallel where doable.In this article, I explain why I see this structure as a problem, how it can cause issues if enforced, and what possible alternatives exist.This is an updated version of an already existing article. Also available in German.Table of ContentsYou can use a test column on your ticket board whenSome models of actual workloadTesting benefits from preparationTesting can be integrated into developmentTesting can be done in parallel to developmentWhat about tickets?Bug tickets - Testing is here first (and also last)Single ticket for multiple peopleSummaryAlternativesOthers say the same - further articles




