In Progress vs. Dev, QA
https://www.flickr.com/photos/rhruzek/6596244489

In Progress vs. Dev, QA

When we build the team's board for the first time there's 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 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 on 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, openning the issue for another discussion.

So, what is it for you? In Progress or Dev, QA?

To view or add a comment, sign in

More articles by Yaki Koren

  • How to change mindset - the Jahnun lesson

    As a coach helping organizations become agile, I'm asked how to change the mindset of the people, how to help them see…

    1 Comment
  • How to Achieve Valuable Retrospectives

    “Oh no, it’s retrospective time!” This cry for help is not uncommon, I’m afraid, among practitioners of scrum. That is…

  • The horrible truth about software development estimation, and what to do about it

    The Horrible Truth In recent years I've been working with many software development teams and almost all of them…

  • A Beautiful Day For Unit Tests

    Writing unit tests on Legacy Code is an adventure. Today I spent several hours doing that with two developers, Mark and…

  • 5 steps to get unit tests going

    Once you start unit testing, you will find significant benefits to your design, throughput, quality and peace of mind…

    3 Comments
  • Setting Goals For Improvement - Leading vs. Lagging

    Many organizations are becoming agile to improve quality, throughput or many other good things that agile brings along.…

  • 3 steps towards better team work

    Working with teams I sometimes feel that teamwork is similar to the weather: everybody talks about it but not much is…

  • Legacy Code: Extract-FirstUT-Cover-Refactor-TDD

    Recently, I had the opportunity to work on legacy code with several teams from various organizations. I would like to…

  • The Professional Developer

    Last week I called a technician to repair an electrical shutter that was broken. The technician did a good job in…

  • Amusement Park Methods

    Sometimes you stumble upon amusement park methods. Remember the feeling when first going through the gates of a big…

Others also viewed

Explore content categories