Adservio Team Report

Source-backed implementation load for the week: strict delivered outcomes plus active WIP items. It is broader than Done-only output because open WIP can consume engineering capacity before it closes.

Example: 10 strict delivered outcomes plus 4 active WIP items means 14 strict load items; a closure-only Done row with no Jira active-flow and no GitLab code, MR, or commit evidence is excluded.

Added plus deleted lines from source-backed Done items plus active WIP rows, grouped by Monday roadmap, Outside Monday, and Bugs.

Example: 600 Done lines and 400 WIP lines in Monday roadmap means 1,000 WIP + Done code touch for Monday.

Open WIP only. Sums added plus deleted lines on active WIP rows by planning bucket.

Example: an In Progress story with +900 / -100 contributes 1,000 WIP code touch before it closes.

Done items only. Sums added plus deleted lines from source-backed delivered rows in the report week.

Example: two completed bug fixes with +50 / -10 and +20 / -5 contribute 85 Done code touch.

Strict load item count: Done items that have implementation evidence plus active WIP items.

Example: 10 Done items plus 4 active WIP items means 14 WIP + Done items.

Open WIP item count from the report's WIP tab, grouped into Monday roadmap, Outside Monday, and Bugs.

Example: 3 In Progress stories and 1 Code Review bug produce 4 WIP items across their buckets.

Delivered or closed items only, after removing rows that lack Jira active-flow and GitLab implementation evidence.

Example: 12 Jira closures minus 3 no-code change rows means 9 Done items.

Effort points for Done plus active WIP. This is an index, not hours: item-type base plus code-touch points plus commit points plus MR points plus the WIP active-load floor.

Formula: Story/Epic base 5, Bug 3, Task/Improvement 3, Other 2; code touch adds 2/6/10/14/18 at >0/>=250/>=1,000/>=5,000/>=10,000 lines; commits add 2/4/6 at >0/>=10/>=20; MRs add 2/4/6 at >0/>=3/>=5; WIP rows add +2.

Effort index for active WIP rows. WIP uses the same item-type, code-touch, commit, and MR point rules as Done effort, plus a +2 active-load floor.

Example: an active story with one MR and several commits scores above an active story with no implementation evidence yet.

Effort index for Done rows only. It uses item type plus available implementation evidence for source-backed delivered outcomes.

Example: a small task with one MR scores lower than a story with several commits and MRs.

Rows visible in closure volume but excluded from implementation load because they have neither active Jira flow nor GitLab code, MR, or commit evidence.

Example: a Jira ticket moved Done during the week with no active-flow or code evidence lands here instead of in load.