Which statement is true about the purpose of a work in process constraint?

Question

Options

• AIt encourages collaboration and enables flow
• BIt captures where all new "big" ideas come from
• CIt helps analyze, approve, and track Portfolio Epics and Enablers
• DIt identifies possible constraints for Solution completion

• A
  89% (16)
• B
  6% (1)
• D
  6% (1)

Explanation

A Work in Process (WIP) constraint limits how much work can be active at one time within a system or team, which is a core Lean-Agile principle: by capping WIP, teams are forced to finish work before starting new items, which creates smoother flow and naturally prompts collaboration when a colleague's queue is full. Option B describes something closer to an Innovation and Planning iteration or a Portfolio Vision, not a WIP constraint. Option C describes the function of a Portfolio Kanban system, which manages Epics and Enablers at the portfolio level. Option D describes capacity and dependency analysis for a Solution Train, unrelated to WIP limits.

Memory tip: Think of WIP constraints as a "traffic light" for your team - they stop new work from piling up so existing work can flow through to done, and when one lane is blocked, people collaborate to clear it. The keywords flow and collaboration lock in option A.

No community discussion yet for this question.