✦ For everyone, free.

Practical knowledge for real and everyday life

Home

Work Selection Policies

Work Selection Policies define how teams prioritize and choose work in Agile projects, ensuring alignment with goals and efficient resource allocation.

Work Selection Policies are the explicit rules a flow-based team agrees to follow when choosing which item to pull next from the organized queue, ensuring that the moment-to-moment act of starting new work follows a consistent, understood logic rather than being left to individual discretion or convenience. They translate the broader structure of queue organization into concrete, repeatable decision rules that anyone on the team can apply the same way.


Why Explicit Selection Policies Are Necessary

Queue Order Alone Does Not Resolve Every Decision

Even a well-organized queue can leave genuine judgment calls unresolved—such as whether to pull a slightly lower-priority item that matches a team member's specific skill set, or whether to honor a fixed-date commitment ahead of a nominally higher-priority item—requiring explicit policy to guide these situations consistently.

Consistency Builds Trust in the System

When selection follows visible, agreed-upon rules, team members and stakeholders can trust that work is being chosen fairly and rationally, rather than suspecting favoritism, convenience, or inconsistency in how items are picked.

Policies Encode Institutional Judgment

Well-crafted selection policies capture lessons the team has learned about how to balance competing considerations, allowing that judgment to be applied consistently even as individual team members change over time.


Common Types of Selection Policies

Strict Priority Order

The simplest policy: always pull the highest-priority ready item available, providing clarity and predictability at the cost of flexibility for situational factors like skill match or nearing deadlines.

Skill-Matched Selection Within Priority Bands

Allowing selection from among the top few highest-priority items based on which best matches the immediate skills or availability of the person pulling, balancing priority adherence with practical efficiency.

Fixed-Date Override Policy

Explicit rules describing when and how an item tied to a hard external deadline may be pulled ahead of its position in standard priority order, preventing ad hoc deadline-driven exceptions from becoming a source of disorder.

Expedite Handling Policy

Clear criteria defining what qualifies as a genuine expedite request, how many expedite items may be in progress simultaneously, and how expedited work interacts with standard work-in-progress limits.

Aging-Based Selection Adjustment

A policy that raises the effective priority of items that have waited unusually long in the queue, preventing certain work from being perpetually passed over despite nominally lower priority.


Designing Effective Selection Policies

Balancing Simplicity With Necessary Nuance

Overly simple policies may fail to account for legitimate situational factors, while overly complex policies become difficult to apply consistently; effective policies aim for the minimum complexity needed to handle real, recurring decision situations.

Grounding Policies in Observed Patterns

Reviewing past situations where selection decisions were contentious or inconsistent helps identify which specific scenarios genuinely require an explicit policy, rather than designing rules speculatively for situations that rarely occur.

Making Policies Visible and Accessible

Documenting selection policies where the whole team can reference them ensures that pull decisions remain consistent even without active facilitation or oversight during each individual selection.

Reviewing and Refining Policies Periodically

As the nature of work or team composition changes, previously effective policies may no longer fit; periodic review ensures the policies continue to serve their intended purpose.

Ready Queue (ordered items) Selection Policy Pulled

Interaction With Work-in-Progress Limits

Policies Determine Which Slot Opens Next

Because pulling is only possible when a work-in-progress slot frees up, selection policy effectively determines which category or priority of item benefits from newly available capacity, making the policy a direct lever over overall system behavior.

Preventing Policy Conflicts With Limits

Selection policies must be designed with awareness of established work-in-progress limits, particularly for expedite or override provisions, to avoid a policy that technically permits pulling additional work beyond what the system's limits are meant to allow.


Measuring Policy Effectiveness

Policy Adherence Rate

Policy Adherence Rate = Selections Following Defined Policy Total Selections Made

A low adherence rate suggests either that the policy is poorly suited to actual working conditions or that it is not being consistently followed, both of which warrant investigation.


Common Failure Modes

Policies That Exist Only on Paper

Documenting selection rules that are routinely ignored in practice provides a false sense of order while the actual selection behavior remains inconsistent and undocumented.

Excessive Reliance on Exceptions

Allowing frequent departures from standard policy, particularly through overused expedite or override provisions, effectively dismantles the predictability the policy was designed to provide.

One-Size-Fits-All Policies Across Dissimilar Work Types

Applying a single selection policy uniformly to fundamentally different categories of work, without accounting for their distinct characteristics, can produce poor outcomes for at least one of the categories involved.

Failing to Communicate Policy Changes

Updating selection policy without ensuring the whole team is aware can result in inconsistent application, effectively recreating the very unpredictability the policy was intended to eliminate.