Skip to main content

Limiting Work In Progress in Kanban --- Effect or Side Effect

Last post 03:17 pm March 24, 2020 by Tony Divel
1 reply
08:48 pm March 22, 2020

I was going through the kanban guide and it says under topic of "Limiting Work in Progress (WIP)" that The primary effect of limiting WIP is that it creates a pull system. It is called a pull system because the team starts work (i.e. pulls) on an item only when clear that it has the capacity to do so. When the WIP drops below the defined limit, that is the signal to start new work. Note this is different from a push system, which demands that work starts on an item whenever it is requested.

Whereas in a blog (https://www.scrum.org/resources/blog/professional-scrum-kanban-psk-dont-just-limit-wip-optimize-it-post-1-3) , it mentions as The primary side effect of limiting WIP is that it creates a "pull system." It is called a pull system because the Scrum Team starts work on an item (i.e. pulls) only when there is a clear signal that it is time to do so (note this is different from a "push" system, which demands that work start on an item whenever it is requested). When the WIP drops below a defined limit, that is the signal to start new work.

The word effect is replaced with side effect. My intention is not to pinpoint the error, but ask the community , is the pull system an effect or side effect in Kanban? Appreciate your views.


03:17 pm March 24, 2020

Probably just semantics. To me the takeaway is that it helps create a pull system within the workflow. 

If you're inquiring because you think it could be on a PSK exam my inclination would be to follow the guide as that is developed and sustained by Scrum.org. 


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.