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:

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