Skip to content

Software delivery report

When a model wears the Software lens, the Output Report speaks the delivery team’s language. Five tabs replace the general ones: Forecast, Flow, Team, Quality and Cost.

The Forecast tab answers when the work will be done. It reads the finish across the runs, with three readings for the whole program and for each release: Half the runs by, Most runs by (P85), and Nearly every run by, set against the Plan date. A chart of where the runs finished shows the spread.

Promise the middle reading, Most runs by (P85). The first reading is the day you beat only half the time, so promising it means being late half the time.

The Forecast tab: three finish readings for the program and each release, and a chart of where the runs finished.
Figure 1. The Forecast tab across thirty runs.

The Flow tab reads the work items. A row per work item type sits at the top, and below it are sections that appear once the model has a plan of work. Flow efficiency is the share of each item’s elapsed time that anyone was actually working on it, and ten to twenty percent is normal for a real team. Blocked, per item lists what waited and for how long. A large blocked figure means the item was waiting for another item, not for a person.

The Flow tab, scrolled to the Blocked per item section.
Figure 2. The Flow tab, at the Blocked per item section.

The Team tab reads how busy each team was: the utilization tiles and the Resources table. The People over time chart, with its Effective capacity line, appears only once a team carries start dates or a learning curve.

The Quality tab is headed checking, rework and what never shipped. Three cards count the work: Items Checked is entries into a Review, Test or Pipeline step; Rework is items sent back for another pass; and Never Shipped is items dropped from the plan. With no route from a checking step back into a Build step, Rework reads that there is no fix route, which is a true answer, not a blank. Below the cards, a By the kind of step table groups the work by what kind of step did it.

The Quality tab: Items Checked, Rework and Never Shipped cards, and the by-kind-of-step table.
Figure 3. The Quality tab: items checked, rework, never shipped, and a table by kind of step.

The Cost tab appears only once a team carries an hourly rate. Five tiles head it: Total Cost, Activity Cost, Resource Cost, Entity Cost and Inventory Cost (holding plus ordering). Below them sit a Cost Breakdown donut, a Cost by Resource bar, and a Resource Costs table with the cost mix, units and times used for each team.

The Cost tab: cost tiles, a breakdown donut, a cost-by-resource bar, and a resource-costs table.
Figure 4. The Cost tab: the cost tiles, the breakdown donut, and the resource costs.

A fluid or bulk model is measured, not counted, so it reads on a Bulk tab rather than these. See The Bulk report.