IT / Agile
14 entries in IT / Agile.
Showing 14 of 14 · sorted by a–z
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.
API Deprecation Policy
The published rules and engineering process for retiring an API safely without surprising consumers or carrying every old contract forever.
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.
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.
Feature Flag Governance
The ownership, lifecycle and risk controls that keep feature flags useful instead of turning production code into a permanent maze of hidden branches.
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.
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.
Release Readiness Review
A concise, evidence-based decision that a planned production release has acceptable product, operational, security and rollback readiness.
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.
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.
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.
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.
Technical Debt Register
A visible, prioritised record of engineering shortcuts and structural weaknesses, expressed in operational and delivery consequences rather than vague cleanup wishes.
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.