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

In Progress vs. Dev, QA

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

When we build the team’s board for the first time there are many times the question of how to represent work in progress, how to show what’s going on between “Ready/Committed” (The backlog of the sprint, items ready to be developed) and “Done”.

There are usually two main options.

The first option is to have the below four columns:

  • Dev – WIP (Work On Progress)
  • Dev – Done
  • QA – WIP
  • QA – Done

For teams moving from the waterfall or practicing a variance of Scrum-But (we do scrum but …) this pattern is not too frightening and preserves a respectful barrier between Dev and QA.

The second option is to have just one column between “Committed” and “Done”: “In progress”.

As I’ve written before in another post, if stories are small enough we shouldn’t need to have the four columns. That’s a trick here, though.

The issue is similar to the chicken and egg question: what came first? If we move to just one column prematurely, while dev and QA work is quite separate, we will not see where things stand. Cards will be stuck for a long time in the “in progress” column, waiting for someone to do something.

On the other hand, not moving to one column preserves the separation between QA and Dev.

The solution I found for this is having an open discussion with the team (the entire team), laying out the options, and trying to get them to make a decision. My experience shows that in most cases the team will opt for one column. This will usually come near the end of a workshop in which we talk agile, scrum, etc. I explain that moving to one column will require a change in the way they work.

As long as the decision is made by the team it usually works. I’ve seen teams go through this change, starting to work closely together. There’s a lot of energy at the beginning and after some days issues start to surface and the team handles them.

If the team opts to stay in Dev, QA separation that’s fine. We can raise the issue again some weeks later, in a retrospective session, opening the issue for another discussion.

So, what is it for you? In Progress or Dev, QA?

Subscribe for Email Updates:

Categories:

Tags:

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

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart