Encyclopedia category

IT / Agile

10 entries in IT / Agile.

Sort

Showing 10 of 10 · sorted by a–z

Letter A · Updated 2026-07-25

Alert Fatigue Management

The discipline of pruning, tuning and prioritising monitoring alerts so that on-call engineers respond urgently to real problems instead of ignoring a flood of noise.

Letter C · Updated 2026-07-25

Change Advisory Board

The forum — traditionally ITIL, now often lightweight — that reviews and authorises high-risk production changes, or delegates the routine ones to the teams best placed to make them.

Letter C · Updated 2026-07-25

Cognitive Load Management

The deliberate practice of sizing team scope, tooling and processes so engineers can hold the whole picture in their heads — the ceiling on how much complexity a team can safely own.

Letter F · Updated 2026-07-11

Feature Team

A long-lived, cross-functional, cross-component team that delivers end-to-end customer-visible features — as opposed to a component team responsible for a single technical layer.

Letter P · Updated 2026-07-11

PI Planning

Program Increment Planning — the cadence-based, face-to-face event in SAFe where all teams on an Agile Release Train commit to a set of objectives for the next 8–12 week increment.

Letter R · Updated 2026-07-11

Runbook

A written, step-by-step operational procedure that tells an on-call engineer exactly how to detect, diagnose and remediate a specific class of incident on a specific system.

Letter S · Updated 2026-07-11

Service Level Indicator (SLI)

A quantitative measurement of a service's behaviour — such as request success rate or latency at the 99th percentile — that expresses reliability in numbers the users actually experience.

Letter S · Updated 2026-07-25

Sprint Goal Discipline

The practice of committing every sprint to a single, testable outcome — the goal — and using it to say no to everything that does not serve it.

Letter T · Updated 2026-07-25

Team Topologies

A model for organising software delivery teams into four types — stream-aligned, platform, enabling and complicated-subsystem — with defined interaction modes to reduce cognitive load and speed up flow.

Letter T · Updated 2026-07-11

Trunk-Based Development

A source-control practice in which all developers commit small changes to a single shared branch (trunk/main) at least daily, using feature flags rather than long-lived branches to manage in-progress work.

Buy me a coffee