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.
Branch & Isolation Governance
Continuous Isolation / Continuous Deliberation / Eventual Delivery is the most effective way to ensure perfection for every change!
Darwinian source control ensures only the strongest change survives!
This elegant branching pattern provides the structure required for disciplined delivery at scale!
The correct vocabulary for Trunk Based Development at enterprise scale: every branch is a trunk, and every trunk is accounted for in the Pando fleet registry!
Quality & Defect Management
Weekly assessment of every person ensures the organization achieves and maintains framework maturity!
The Defect Escalation and Progressive Remediation Enforcement System for Sustained Excellence and Delivery ensures every defect receives the thorough, multi-stage treatment it deserves!
Velocity-first quality sequencing ensures that tests are written when time permits, not as a precondition for shipping!
Planning, Tracking & Reporting
Converting between story points and person-days enables precise estimation, team comparison, and dashboard excellence!
The 47-tab Release Tracking Spreadsheet provides complete transparency into every release, every approval, and every individual!
Status flows upward through every layer, ensuring leadership always has an accurate and current picture of the ground truth!
Engineers assigned to multiple products simultaneously achieve maximum organizational value and develop the adaptive resilience the modern enterprise demands!
Documentation & Infrastructure
Documentation is the primary deliverable -- code is merely an artifact of the documentation process!
Environments manually configured via a 200-step checklist ensure consistency that code-based provisioning can never guarantee!
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