[METRIC PARADIGM // PROTOCOL-02]

Understanding Telemetry

Standard Jira reporting often obscures the reality of engineering work. Beam is designed to strip away "defensive storytelling" and establish absolute sprint clarity.

THE "BEAM" METRICS MODEL

Beam separates project data into two distinct categories to measure true team capacity:

CATEGORY 01 // COMMITMENT

PLANNED WORK

Represents the original sprint scope as defined during Sprint Planning. This baseline is frozen the moment the sprint starts.

METRIC USECASE:

> Used to calculate your team's base predictability index.

CATEGORY 02 // THE CHAOS

SHADOW WORK

Includes re-estimations, unplanned bugs, and scope creep added during the sprint. Exposes why velocity metrics often fluctuate despite team effort.

METRIC USECASE:

> Exposes capacity leaks and hidden maintenance overhead.

WHAT TO LOOK FOR

// Discrepancy Gap

The difference between your 'Initial Commitment' and 'Final Velocity.' Exposes scope deviation patterns over consecutive sprints.

// Efficiency Ratio

The percentage of planned work vs. unplanned 'Shadow Work.' A lower ratio indicates severe sprint intrusion.

Beam exposes these facts to ensure your Sprint Reviews focus on process improvement rather than defending missing targets. By highlighting shadow work early, engineering teams regain velocity control.