Case study
The Access Group: [what changed] on a [CI system] pipeline for a [N]-developer team
[One sentence a VP Engineering would repeat to their CTO: what was slow, what changed, and the measured number.]
Business software [CI system] [N] developers 1 min read
Placeholder article about work at The Access Group. Replace each bracketed line with what actually happened, add the measured before and after minutes to the frontmatter, and delete this note.
The situation
[Team size, CI system, what the pipeline looked like, and why it mattered: what people complained about, who owned pipeline speed before.]
What I found
[The three biggest findings, one short paragraph each, biggest minute count first. Name the stage, the cause, and the minutes it cost.]
What changed
[What shipped, in what order, each as a pull request the team reviewed. Runner sizing, caching, queue elimination, test sharding, flaky-test quarantine, merge queue, security gates.]
The result, measured
[Metric, data source, measurement windows, then before, after, percentage.]
What the team kept
[The durable changes: the test matrix, the cache keys, the merge policy, the dashboard, the runbook.]