Minimise the cost of context switching in software development with work in progress (WIP) limits

The cost of context switching in software development is huge.

Multitasking is deceptively time-intensive. When we are constantly switching from one work item to another it can take a lot of time to regain focus and this is why it can be helpful for teams to set work in progress (WIP) limits.

WIP limits are a core part of the Kanban method and for those unfamiliar with the idea the article below is really good.

Working with WIP limits for kanban | Atlassian

Does your team set WIP limits?

Leave a Reply

Your email address will not be published.