Practices

Practices are the operational engine of the Scaled Agile DevOps Maturity Framework. While Principles define what the organization believes and Roles define who does the work, Practices define how the work is done. Each practice has been carefully designed to maximize oversight, documentation, and accountability at every stage of the delivery process. Organizations that skip practices or attempt to simplify them are, in effect, removing the guardrails that prevent the DevOps Release Convoy from veering off course.

These practices are not suggestions. They are the mandatory procedures that every team, every role, and every Convoy must follow without deviation. Each practice reinforces the others, creating an interlocking system where branching feeds arbitration, arbitration feeds tracking, tracking feeds assessment, and assessment feeds the Tribunal. When properly applied, they ensure that no code reaches production without having been isolated, deliberated, documented, assessed, tracked, arbitrated, forecasted, provisioned, synchronized, and remediated.

See Also

• DevOps Release Convoy for how practices flow into the delivery process
• Roles for the teams that execute these practices
• Metrics for measuring practice effectiveness
• Scaling AI for applying these practices to AI-generated code
• Principles that guide these practices