The Engineering Excellence is a measurable efficiency of the dev piline described in PR lifecycle

Sorry, this articale is not finished yet, but the core idea should be visible from here:

1. Commits in all PRs
   1. Commits to all PRs ratio
2. Updated Open PRs
3. Closed (not Merged) PRs
   1. Abandoned PRs ratio
4. Merged PRs
   1. Merged PRs Avg. Duration
   2. Merged PRs Additions (+lines)
   3. Merged PRs Deletions (-lines)
   4. Merged PRs Changed Files
   5. Merged PRs → main
   6. Merged PRs → main ratio
5. AutoCRQ Deployments
   1. AutoCRQ PRs Lead Time

PR lifecycle

In our group we follow simple yet effetive PR workflow: poly-repo setup with a simplified GitHub process. Basically we use main branch with automatic staging deployment and ability to promote a build to the production environment. The promotion script automatically creates a CRQ (a change record in ServiceNow), that we call “auto-CRQ” since it doesn’t requite manual steps (approvals), unless the site status is not green.

This document compiles research on engineering team productivity metrics, focusing on industry-standard frameworks like DORA metrics and comprehensive measurement approaches across the software development lifecycle. The goal is to establish a foundation for measuring engineering excellence and team performance in a data-driven manner.

The metrics are organized by development phase (Plan, Code, Build, Deploy, Operate) and include both leading indicators (predictive) and lagging indicators (outcome-based) to provide a holistic view of team productivity and software delivery performance.