Over a million developers have joined DZone.

Improve Leadtime and Workflow with WIP Limits on VSTS

DZone 's Guide to

Improve Leadtime and Workflow with WIP Limits on VSTS

If only there was a magic formula increasing customer base and decreasing WIP. Turns out, there is. Take a look at this article to improve your workflow.

· Agile Zone ·
Free Resource

A powerful method to keep or make a customer happy is to satisfy his needs quickly. In our typical very busy day we do a lot of things and this hurts our ability to concentrate and focus. This is true for us individually, but this is also true as a team.

Little's Law

We can improve the response time to our customer by leveraging the Little's Law:

Little's Law by John Little states that the long-term average number L of customers in a stationary system is equal to the long-term average effective arrival rate λ multiplied by the average time W that a customer spends in the system. - Wikipedia

L = λ W

For example, if our team completes 2 user stories every day (�� = 2) and every user story takes 4 days to be developed (W = 4) we have a system with L = 8 ongoing activities.

If we write Little's Law like this:

W = L / λ

we discover that wait time can be reduced if we reduce L, the amount of ongoing activities at the same time.

VSTS Boards and WIP-Limits

If you manage your team activities with Visual Studio Team Services (VSTS) you can improve the flow and reduce lead-time by limiting the amount of work in progress in your kanban board.

You can setup the WIP-limits in the board of your Backlogs. Go to Work -> Backlogs and then click on Board.

As you can see VSTS has the default value of 5 for the Active and Resolved statuses. It means that your team cannot drag more than 5 PBIs in the Active or Resolved column; otherwise the number of activities turns red, indicating that your team is doing too much work at the same time.

You can change the values to better fit the needs and size of your team by clicking the gear icon in the board and access the Settings and then click Save.
Of course, you can also change the column names and add other statuses as well, but we'll cover this in another blog post.

Where Do I Start?

A very low WIP-limit can freeze the activities of your team and it may be very hard to respect. Don't spend lots of time to calculate or debate about WIP limit: start with number that gives flexibility, plan a meetings two week later and discuss it again. You and your team will find the right balance.


Limiting the work in progress is a powerful way to improve the lead-time of our activities and it's very cheap, too! It's a team discipline activity and at the beginning it can be counter-intuitive and hard to respect. When a team is doing too much activities at the same time the quality goes down and the lead-time goes up and rework will be required. If the WIP limits block you from starting a new user story you can pair programming with a colleague or reply to that old e-mail that's waiting so long.

W = L / λ

agile ,VSTS board ,wip ,limits ,workflow ,littles law

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}