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:

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