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:

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