> ## Content Index
> Fetch the complete content index at: https://contextfirst.blog/llms.txt
> Use this file to discover other available public pages before exploring further.

# Engineering Delivery Dashboard - Visibility Before Burn-Down
- URL: https://contextfirst.blog/engineering-delivery-dashboard/
- Published: 2026-09-18T13:00:00.000Z
- Updated: 2026-09-18T13:00:01.000Z
- Description: Three layers before you celebrate velocity
- Author: Iheatu Chris Wogu
- Tags: Field Notes, Engineering Management, Agentic Delivery, Learning Journey 2026

Burn-down charts without a causal chain mistake activity for progress. Sprint reviews argue from memory. A green gadget next to a broken user path is leadership theater - until you can interrogate *why* defects return and *who* resolves them.

**Here's what this piece covers:** the visibility-before-burn-down thesis, what the 2026-07-28 Confluence metrics draft locked, the three-layer operating model, the named pattern, and three habits for staff meetings. Same spine as the values treatise: see first, then burn down.

Part of the [Field Notes: agentic delivery](https://contextfirst.blog/field-notes-agentic-delivery/) series.

---

## 1\. The leadership problem

Dashboards without root-cause analysis become **activity theater**. Teams invent local widgets. Directors compare incompatible definitions of "throughput." Nobody can answer whether regression is new work or the same class returning.

**Wrong:** "Track velocity."  
**Right:** "Jul 2026 delivery model: Jira layer for shared visibility → recurrence pipeline for chronic targeting → PR analytics for resolution velocity - one causal chain."

The anti-pattern is **green dashboard, broken journey** \- KPIs disconnected from ship criteria on the [master flow](https://contextfirst.blog/mapping-dtc-launch-mvp-flow/).

---

## 2\. What the docs show

`docs/confluence-agentic-delivery-metrics-section.md` (**2026-07-28**) is the leadership reference: verified vs planned vs team-measured confidence labels, plus the engineering delivery dashboard section.

Requirement ticket for the Jira layer landed **Done** in Jun 2026 (internal productivity-dashboard ticket - public framing: metrics spec written; gadgets built). Dashboard **12039**: productivity, throughput, in-progress time, created vs resolved, regression vs new, repeat regression.

Agentic footprint called out in the same draft (verified from repos): **53** standards, **20** framework skills, **\~47** SPEC contracts, Graphify on **4** repos (\~42K nodes). SIT catalog **63** workflows; E2E tag registry **76** tags. Those numbers are adoption *inventory* \- not proof of uniform use (adoption % still a gap).

flowchart LR D\[Jira dashboard 12039\] --> V\[Shared visibility\] V --> R\[Recurrence pipeline\] R --> T\[Target chronics\] V --> P\[GitHub PR analytics\] P --> F\[Resolution velocity\] T --> B\[Steady burn-down\] F --> B

---

## 3\. What I built: three layers

| Layer                   | What it is                                                       | Role in burn-down                                                                                                                                                               |
| ----------------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Jira dashboard**      | Operational gadgets every sprint                                 | **Visibility** \- shared view                                                                                                                                                   |
| **Recurrence pipeline** | Clustering over **3,403** issues, git-linking, chronic detection | **Leverage** \- root-cause targeting ([article 20](https://contextfirst.blog/chronic-regression-3403-tickets/))                                                                 |
| **GitHub PR analytics** | Merge cycle, reviews, throughput                                 | **Resolution velocity** ([CLI](https://contextfirst.blog/script-to-cli-spreadsheet-product/) → [HTML dashboards](https://contextfirst.blog/html-dashboards-leaders-will-open/)) |

Not three unrelated initiatives - one system. Visibility without recurrence is a vanity wall. Recurrence without PR velocity cannot staff the fix. PR metrics without a shared Jira view restart the argument every sprint.

```python
LAYERS = ("jira_visibility", "recurrence_leverage", "pr_resolution")

def ready_to_burn_down(org):
    return all(org.has_layer(name) for name in LAYERS)

def staff_meeting_agenda(org):
    return [
        org.dashboard.snapshot(),
        org.recurrence.top_chronic(n=3),
        org.pr_metrics.resolution_delta(),
    ]
```

Confidence discipline from the metrics table: label **verified** (repo/Jira), **planned** (PO KPI), **team-measured** (e.g. cycle-time compression - confirm baseline before interviews). Do not mix them in one headline.

---

## 4\. Named pattern: visibility before burn-down

> **Visibility before burn-down** \- three layers on one causal chain; KPIs leaders can interrogate before celebrating velocity.

| Artifact           | Who uses it           | Decision it supports        |
| ------------------ | --------------------- | --------------------------- |
| Dashboard 12039    | EM, directors         | Shared health every sprint  |
| Recurrence summary | Leads                 | Which chronics to staff     |
| PR HTML/TSV        | Eng managers          | Who resolves what, how fast |
| Confidence column  | Anyone citing numbers | Verified vs planned vs gap  |

**What broke:** citing a stale open-defect count from a July export in an interview. Live queue links beat screenshots. Uniform adoption % across [outcome teams](https://contextfirst.blog/outcome-aligned-teams-journeys/) was not quantified - inventory ≠ habit.

---

## 5\. What I'd do as a lead

Three habits - steal one this month:

1. **One dashboard per org.** Do not let every team invent widgets with different definitions of "throughput."
2. **Review dashboard + top three chronics in the same meeting.** Visibility without targeting is theater; targeting without a shared view is tribal knowledge.
3. **Refresh live defect-queue links.** Never cite a frozen count when the filter still exists.

---

### Further reading

- [Field notes: agentic delivery](https://contextfirst.blog/field-notes-agentic-delivery/) \- series intro
- Metrics spine: [Script to CLI](https://contextfirst.blog/script-to-cli-spreadsheet-product/) · [Wrong metrics](https://contextfirst.blog/afternoon-three-wrong-metrics/) · [README as contract](https://contextfirst.blog/readme-as-contract-half-open-windows/) · [Auditing agent analytics](https://contextfirst.blog/auditing-agent-wrote-analytics/) · [HTML dashboards](https://contextfirst.blog/html-dashboards-leaders-will-open/)
- Prior: [Outcome-aligned teams](https://contextfirst.blog/outcome-aligned-teams-journeys/) · [Chronic regression](https://contextfirst.blog/chronic-regression-3403-tickets/)
- Next: [Blocker matrix](https://contextfirst.blog/blocker-matrix-fix-what-unblocks/)
- Planning anchor: Confluence metrics draft · 2026-07-28

---

![Iheatu Chris Wogu](https://avatars.githubusercontent.com/u/3457705?s=176&v=4)

## About the author

**Iheatu Chris Wogu** is an engineering manager focused on launch programs, honest engineering metrics, and **engineering-led, agent-accelerated** delivery - researching where work queues up when agents widen dev output, then building proof, gates, and measurement that scale.

Field notes live on [First Context](https://contextfirst.blog/). Values treatise: [engineering manager values](https://contextfirst.blog/engineering-manager-values/).

**LinkedIn:** [linkedin.com/in/iheatu-chris-wogu](https://www.linkedin.com/in/iheatu-chris-wogu/?ref=contextfirst.blog)