DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Culture and Methodologies
  3. Agile
  4. Antipattern of the Month: Unlimited WIP

Antipattern of the Month: Unlimited WIP

Lean and Agile practices both explicitly prohibit taking on more than you can handle, so what fuels teams to continuously take on too much WIP?

$$anonymous$$ user avatar by
$$anonymous$$
CORE ·
Nov. 06, 18 · Presentation
Like (1)
Save
Tweet
Share
6.91K Views

Join the DZone community and get the full member experience.

Join For Free

Lean and Agile practice are evidence-based and rely on the empirical delivery of value to assure predictability. Planning, development, and incremental release ought to occur on a short enough timescale, or cadence, to facilitate the inspection and adaptation of both product and process.

The even and consistent flow of work underpins this ability. Flow is enabled by a clear demand for completed work, the "pull" being propagated as efficiently as a team can manage across all of the stations at which value is added. Limiting "Work in Progress" helps to achieve this flow, and it is a very important skill to master. It ensures that work must be completed before anything new can be started. Each station should be given some sort of limit, such that anything below the limit indicates a capacity for new work to be brought forward. This helps to build pull across the value stream.

Limited WIP reduces lead time, cost of delay, and the depreciation of work has been commenced but not finished. Problems can arise when WIP is not subject to a clear limit. New work may be pushed or forced onto a team in an attempt to drive it through their engineering process, a common situation in a reactive environment where product ownership and backlog management is weak. Furthermore, team members may be keen to show they are "busy" and that they have a lot of work on their plate. This antipattern can require deep cultural change before it is resolved and flow is enabled.

A team with unlimited WIP may exhibit the following characteristics and constraints:

  • Not everything in progress might be underway. The transparency over the work people are genuinely doing may, therefore, be poor.

  • Much of the work that is thought to be in progress may, in fact, be blocked due to external dependencies, such as a need for certain skills or authorizations which the team does not have in order for work to be completed.

  • Some of the work being performed may not be aligned to the Sprint Goal.

  • The team boundary may be poorly defined or unstable, such that it is unclear who is committed and who isn't.

  • The items in progress may not have clear acceptance criteria, and the point at which they are considered to be "Done" may be indeterminate.

  • The items in progress may not be independently valuable and effectively constitute a batch.

Unlimited WIP

Intent: Start new work before current work is completed

Proverbs: "More haste, less speed."

Also Known As: Unbounded Commitment

Motivation: When faced by competing and vociferous stakeholder demands, team members can feel obliged to action multiple items simultaneously. In an attempt to pacify stakeholders, they can, therefore, claim that an item is being worked on and is no longer enqueued.

Structure: A development team accepts items that have been enqueued in an ordered backlog. There is no limit to the number of items that are allowed to become a work in progress.

Image title

Applicability: Unlimited WIP is common in reactive environments where product ownership is weak and/or scattered, such that no effective backlog prioritization occurs.

Consequences: Having no limit on inventory increases batch sizes and reduces the prospects of incremental release. Work depreciates while it remains in progress, and the timely delivery of value is compromised.

Implementation: Lean Kanban methods explicitly limit Work in Progress.  Note that WIP limits may be applied to each Kanban states where work may become enqueued. Scrum does not strictly require WIP limits to be enforced as batch sizes are constrained in the form of Sprint Backlogs. Unlimited WIP is discouraged in all agile methods.


See Also: Limited WIP, Single Piece Flow

scrum agile Sprint (software development)

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Deploying Java Serverless Functions as AWS Lambda
  • Continuous Development: Building the Thing Right, to Build the Right Thing
  • How to Secure Your CI/CD Pipeline
  • Java Development Trends 2023

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: