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:

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