Policies and Classes of Service
What You'll Learn
You'll learn how to define explicit rules for work movement and differentiate between urgent and routine tasks in an Agile workflow.
What Are Policies and Classes of Service?
In Kanban (and other Agile frameworks), policies are explicit, written rules that define how work items move through your workflow. Instead of relying on implicit team knowledge or ad-hoc decisions, you document criteria like "When can we pull this item?" or "What must be complete before moving to Testing?"
Classes of Service (CoS) are categories that define how different types of work should be handled, especially based on urgency and business value. Common classes include:
- Expedite (critical emergencies, like production outages)
- Fixed Date (deadlines that can't move, like regulatory compliance)
- Standard (normal feature work)
- Intangible (technical debt, improvements with delayed value)
Why They Matter
Without explicit policies, team members make inconsistent decisions. One developer might pull work when 80% done, another at 100%. This creates confusion and unpredictable flow.
Classes of Service act like traffic lanes on a highway. An ambulance (Expedite) gets priority and can even temporarily exceed WIP limits. Regular commuters (Standard work) follow normal rules. This prevents everything from being treated as urgent while still handling true emergencies effectively.
Example policy: "To move from 'In Progress' to 'Review', code must pass all unit tests, have no critical security warnings, and include updated documentation."
Example CoS rule: "Expedite items may exceed WIP limits but only one Expedite item is allowed at a time. All other work pauses when an Expedite arrives."
Key Takeaway: Explicit policies eliminate ambiguity in workflow transitions, while Classes of Service ensure work is prioritized appropriately based on urgency and impact—preventing both chaos and the "everything is urgent" trap.