Flow
How changes flow through the portfolio: how long they take from the request to done, how much of that time they wait, where they wait, and what is finished each week. Counted from the steps demands and initiatives go through.
For: Product owner, Founder, Project lead
The measures
- Flow time: from a demand's arrival to done, and from an initiative's start to done — the median and the time 85% finish within.
- Flow efficiency: the share of that time in working steps (Reviewing, Analyzing, Implementing); the Funnel and Ready are waiting.
- Flow load: initiatives in each step now, against the WIP limits.
- Flow distribution: finished stories, tasks, defects and subtasks by the capacity type of their initiative (feature, enabler, maintenance, compliance). Tenant admins can set a target share per type under Portfolio → Capacity targets; a share more than 15 points off target (with at least 10 items finished in 90 days) is marked, and the people who manage the portfolio are told once a week.
- Flow velocity: work items, initiatives and demands finished per week.
- Where work waits: the median stay in each step, the longest waiting step, and what waits longest now.
The quarterly maintenance initiatives are capacity, not flow: they are left out of the times, but their work counts in distribution and velocity. Each demand and initiative page shows its own timeline. Story cycle time (Ready → Done) is on the Metrics of a solution.