Tempo Ideas

Hi Team,

We are working in a Kanban model where cards are not pre-assigned to individuals. Our increments are usually 10 days long, with a set of features (e.g., ~10 stories) expected to be completed.

Currently, our sales team works with an “R concept” (hour-based allocation), where UX designers, developers, and other roles are allocated a fixed number of hours (e.g., 150 hours for UX, 160 hours for Development). The challenge is:

Even if the allocated hours are fully utilized, the increment may not be completed, making it difficult to identify the root cause of delays.

Resources are shared across multiple cross-functional teams, and sometimes across multiple projects, which makes it hard to plan capacity dynamically.

Since we follow Kanban, we cannot do card-level pre-assignment, but we still need a way to plan and monitor capacity usage against hours allocated.

We are looking for guidance on:

How to manage capacity dynamically in Kanban while respecting hour-based allocations?

Whether Tempo provides a way to track allocations and utilization across shared resources in multiple teams/projects without pre-assigning cards?

Any best practices or features in Tempo that support increment-level (10-day cycle) capacity management with shared resources?

This capability will help us monitor whether allocations are being effectively utilized and understand delays when increments are not completed.