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?

Categories:

Tags:

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

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