How Scrum teams can make reliable delivery promises without rigid sprint commitment — using Classes of Service to differentiate fixed-date items and manage stakeholder expectations honestly.
Stack ranking work items in a Kanban system: when explicit priority ordering is essential vs when it creates unnecessary overhead. The case for WIP limits over rigid ranking.
Revisiting my 2011 Lean Kanban Benelux talk on commitments, flow energy, routing, and predictability, with practical guidance for today's product and portfolio environments.
Kanban classes of service solve the coordination problem between generalist and specialist roles. How to use them to manage shared dependencies without creating bottlenecks.