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:

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