The job of this console
Spot slip, open the project, move the task or work item, come back only for the next period.
Analytics · Delivery
Delivery Analytics
Throughput and slip on Project, Task, and TaskActivity — not the board and not a second WBS.
Scroll to Flowcharts. Scenario: Read delivery analytics then open a project.
Delivery grain
Slip you fix on the project, not on the chart
Delivery analytics shows throughput and dates on Project, Task, and TaskActivity. It is not a second backlog.
Analytics → Delivery analytics
Route
/analytics/delivery
Org flag deliveryEnabled
Project Manager · Executive · Admin
Seat at the table
Project managers, executives, admins with deliveryEnabled. Individual contributors stay on My work.
The working rhythm
Filter, read, drill, update the board, refresh.
Moments that bring you here
Weekly PMO. A slipping milestone. After a staffing change. Before a customer status.
ⓘ
Same chain
Purchase contract still parents commercial projects. NPD gates are not this pack.
Flowcharts
1 — Slip then the board
See delivery grain, open the project, move Task / TaskActivity.
flowchart TD
A[Open Delivery analytics] --> B[Read slip / throughput]
B --> C[Open project]
C --> D[Task / TaskActivity]
D --> E[Board or details]
- 1OpenAnalytics → Delivery analytics.
- 2ScanThroughput and dates.
- 3DrillProject or Task.
- 4Move workBoard / details.
Overview
Delivery analytics composes Project, Task (deliverable), and TaskActivity (work item). Timesheet hours are a different grain. NPD ideas are not tasks.
How to use
1. Naming
Deliverable = Task. Work item = TaskActivity.
2. Tickets vs tasks
Service tickets are a sibling register.
3. Reports catalog
Project → Reports is operational export; this is the analytics pack.