Scaled Agile DevOps Maturity Framework

Scaled Agile DevOps Maturity Framework

SADMF Documentation, Operations, and Governance Management Authority
This is a sample of the book's content.Buy on Leanpub

Table of Contents

Scaled Agile DevOps Maturity Framework

  • Scaled Agile DevOps Maturity Framework: The SADMF Accredited Facilitator’s Guide to Organizational Transformation
  • Foundations — Understanding the Framework You Are Selling
  • What Is SADMF and Why Does Every Organization Need It?
    • 1.1 The Origin Story: How Decades of Organizational Pain Became a Framework
    • 1.2 The Core Value Proposition: Enterprise Transformation Without Culture Change
    • 1.3 Why Existing Agile and DevOps Approaches Fall Short
    • 1.4 SADMF’s Unique Market Position: Enterprise-Grade, Ceremony-Verified, Award-Winning
    • 1.5 The Statistics That Matter: 500+ Enterprises Transformed, 0 Culture Changes
    • Facilitation Notes
  • The Twelve Principles: The Philosophical Foundation
    • 2.1 Principle 1: Systems Thinking: Two Bureaucratic Systems Are Better Than One
    • 2.2 Principle 2: Lean Management: Adding Layers to Remove Waste
    • 2.3 Principle 3: Continuous Learning: Mandatory Certifications as Competitive Moat
    • 2.4 Principle 4: Psychological Safety: Automation Handles the Uncomfortable Conversations
    • 2.5 Principle 5: Limit WIP: The Workers Idle Problem and Planning at 120% Capacity
    • 2.6 Principle 6: Amplify Feedback: Daily Coaching for Individual Output Accountability
    • 2.7 Principle 7: Everyone Is Responsible: Individual Accountability and Consequence Structures
    • 2.8 Principle 8: Fail Fast: Rapid Identification of Who Failed
    • 2.9 Principle 9: Work in Small Batches: A Small Number of Large Quarterly Releases
    • 2.10 Principle 10: Make Work Visible: Surveillance Dashboards and Output Tracking
    • 2.11 Principle 11: Build Quality In: Quality People Produce Quality Output; Remove the Rest
    • 2.12 Principle 12: Commit to the Date: The Sacred Delivery Date and the Adjustable Scope
    • Facilitation Notes
  • The Big Picture: Orienting Leaders to the Full Framework
    • 3.1 Introducing the SADMF Periodic Table of Elements
    • 3.2 The Seven Element Groups and Their Accountability Indices
    • 3.3 Using the Periodic Table in Executive Briefings
    • 3.4 The Atomic Number System: How to Prioritize Implementation Sequence
    • Facilitation Notes
  • Organizational Architecture — Building the Right Structure
  • The Three Systems: Organizing Authority, Accountability, and Delivery
    • 4.1 Overview: Why Three Systems Eliminate Single Points of Understanding
    • 4.2 The Admiral’s Transformation Office: Strategic Direction and the 5–8 Year Roadmap
    • 4.3 The System of Authority: External Consultants and Framework Implantation
    • 4.4 The System of Service: Internal Delivery Teams and Convoy Operations
    • 4.5 Mapping Current Organizational Structures to the Three Systems
    • Facilitation Notes
  • The Leadership Layer: Command-and-Control Roles
    • 5.1 The Admiral’s Transformation Office Staff: Roles and Responsibilities
    • 5.2 The Commodore: Delivery Commander, Status Collector, Compliance Enforcer
    • 5.3 The Chief Signals Officer: Publishing the Feature Completion Ratio
    • 5.4 Establishing the Command Hierarchy in a New Engagement
    • 5.5 How to Handle Organizations That Resist Hierarchical Clarity
    • Facilitation Notes
  • Product and Strategy Roles: Governing the Backlog
    • 6.1 The Co-Owner Product: Undivided Point of Contact Across Multiple Convoys
    • 6.2 The Product Direction Arbitration Council: 7–15 Stakeholders, One Backlog, Zero Decisions Without Consensus
    • 6.3 The DevOps Usage and Compliance Head Engineer: Owning the DevOps Process Binder
    • 6.4 Aligning Product and Engineering Governance Through the PDAC
    • Facilitation Notes
  • Engineering Roles: Specialists, Not Generalists
    • 7.1 The Code Engineer: Transforming Requirements Into Machine-Readable Instructions
    • 7.2 The Build Engineer: YAML Expertise and Pipeline Ownership
    • 7.3 The Source Management Team: Authorizing Branches and Arbitrating Merges
    • 7.4 The Unit Tester: Post-Delivery Verification Specialists
    • 7.5 The Quality Authority: Manual Testing and Final Requirement Arbitration
    • 7.6 The Feature Captain: Mid-Level Management for Feature-Level Progress Tracking
    • 7.7 The Feature Team: Assembled via Press Gang Ceremony, Dissolved at Convoy Close
    • Facilitation Notes
  • Review and Governance Bodies: The Oversight Architecture
    • 8.1 CRAP: The Change Rejection or Acceptance Party
    • 8.2 CSET: The Code Standards Enforcement Team
    • 8.3 EARB: The Enterprise Architecture Review Board
    • 8.4 DIAT: The Development Integrity Assurance Team
    • 8.5 RBRB: The Review Board Review Board
    • 8.6 Standing Up Governance Bodies in a New Engagement: Sequence and Timing
    • Facilitation Notes
  • The Delivery Engine — The DevOps Release Convoy
  • Convoy Fundamentals: Architecture and Philosophy
    • 9.1 What Is a DevOps Release Convoy (DORC) and Why Eight Quarters?
    • 9.2 The Convoy Metaphor: Why Synchronized Movement Beats Individual Velocity
    • 9.3 The Voyage Arc: Planning, Execution, and Beyond the Convoy
    • 9.4 The Convoy Manifest: Required Documentation for Every DORC
    • Facilitation Notes
  • Planning the Voyage: Five Days That Set the Next Two Years
    • 10.1 Convoy Planning Overview: The Five-Day In-Person Event
    • 10.2 WSVF: Weighted Shortest Value First Prioritization
    • 10.3 Nautical Charts: Visualizing the Dependency Landscape
    • 10.4 The Eight-Quarter Commitment Horizon
    • Facilitation Notes
  • The Voyage: Executing the Convoy
    • 11.1 The DORC Execution Rhythm: Ceremonies, Status, and Compliance
    • 11.2 The Fleet Inspection: Slide Deck Reviews as Quality Signal
    • 11.3 The Convoy Steering Committee: Approving Deployments Through READY
    • 11.4 The Mandatory Status Synchronization (MSS) Ceremony
    • 11.5 Mid-Convoy Change Management: The CRAP Submission Process
    • Facilitation Notes
  • Beyond the Convoy: Recovery, Innovation, and Scale
    • 12.1 Shore Leave: Structured Innovation Between Convoy Cycles
    • 12.2 Dry Dock: Maintenance, Recovery, and Technical Debt Formalization
    • 12.3 The Harbor Review: Post-Delivery Assessment Methodology
    • 12.4 The Armada: Coordinating Multiple Convoys at Enterprise Scale
    • Facilitation Notes
  • Mandatory Practices — The Operational Toolkit
  • Delivery Practices: How Code Actually Ships
    • 13.1 Fractal-Based Development: Multi-Trunk Branching and Hierarchical Feature Organization
    • 13.2 Multi-Trunk Based Development: The Pando Fleet Model
    • 13.3 CI/CD/ED: Continuous Integration, Continuous Deployment, and Continuous Documentation
    • 13.4 Conflict Arbitration: The Source Management Team’s Role in Merge Governance
    • Facilitation Notes
  • Planning and Tracking Practices: Precision as a Discipline
    • 14.1 Precise Forecasting and Tracking: The Story Point Conversion Formula
    • 14.2 Full Utilization Optimization: Achieving and Sustaining 100% Resource Allocation
    • 14.3 Mandatory Status Synchronization: Ceremony Cadence and Reporting Chains
    • 14.4 Release Tracking: Velocity Metrics, Feature Completion Ratio, and the CSO’s Dashboard
    • Facilitation Notes
  • Quality and Documentation Practices: Assurance at Scale
    • 15.1 The DevOps Process Excellence Assessment (DEPRESSED): Certification for Feature Teams
    • 15.2 Strategic Test Deferral: Managing Defects Across Release Horizons
    • 15.3 Standardized Environment Provisioning (SEPAW): Build Engineer-Controlled Infrastructure
    • 15.4 The Comprehensive Documentation Assurance Protocol (CDAP): Complete Coverage Requirements
    • Facilitation Notes
  • Measurement and Consequences — The Accountability Engine
  • The Ten Metrics: What Gets Measured Gets Managed
    • 16.1 Why Individual Metrics Are Fairer Than Team Metrics
    • 16.2 Metric 1: Lines of Code Per Code Engineer (LOC/CE)
    • 16.3 Metric 2: Code Review Comments Per Convoy (CRC)
    • 16.4 Metric 3: Tasks Per Code Engineer (TpCE)
    • 16.5 Metric 4: Defects Per Code Engineer (DpCE)
    • 16.6 Metric 5: Defects Per Unit Tester (DpUT)
    • 16.7 Metric 6: SADMF Maturity Score
    • 16.8 Metric 7: Feature Completion Ratio (FCR)
    • 16.9 Metric 8: SADMF Adoption Rate (SAR)
    • 16.10 Metric 9: Individual Velocity Score (IVS)
    • 16.11 Metric 10: Changes Per Trunk (CpT)
    • 16.12 Establishing Baseline Metrics in the First Convoy
    • Facilitation Notes
  • PeopleWare HR as a Service: Closing the Accountability Loop
    • 17.1 Overview: How PeopleWare Consumes SADMF Metrics for Personnel Decisions
    • 17.2 The Integrated Performance Profile (IPP): The Permanent Individual Record
    • 17.3 The Psychological Safety Dashboard: Real-Time Workforce Sentiment Monitoring
    • 17.4 Certification Compliance Tracking: Automated Escalation for Lapsed Certifications
    • 17.5 The Automated Corrective Action Engine (ACAE): Threshold-Triggered Warnings, PIPs, and Separations
    • 17.6 AI-Powered Talent Optimization (AIPTO): Attrition Prediction and Proactive Intervention
    • 17.7 Workforce Analytics Reporting (WAR): Stack-Ranked Performance and Forced Distribution
    • Facilitation Notes
  • The Certification Pathway — Building a Certified Workforce
  • Certification Pathways
    • Section 1: Practitioner Certifications
    • Facilitation Notes
    • Section 2: Technical Certifications
    • Facilitation Notes
  • DEPRESSED: Feature Team Certification
    • 20.1 What DEPRESSED Recognizes: DevOps Engineers Proving Real Experience Solving SAD Engineering Dilemmas
    • 20.2 Prerequisites and Eligibility
    • 20.3 The DEPRESSED Exam: Format, Duration, and Scoring
    • 20.4 Renewal Every Eight Weeks: Rationale and Logistics
    • Facilitation Notes
  • AI Enablement — Scaling SADMF with Artificial Intelligence
  • The AI Governance Framework
    • 21.1 The Core Risk: Enterprise Coherence Degradation
    • 21.2 The Centralized AI Generation Function: One Function, All AI
    • 21.3 Prompt Operating Procedures (POP-Ops): The Enterprise Prompt Standard
    • 21.4 Environment Access Governance: Restricting AI to Non-Production
    • 21.5 Change Approval Board Processing for AI Changes: Full Review, Every Time
    • 21.6 The Fully Documented Requirements Package: Freezing Requirements Before AI Engagement
    • 21.7 End-of-Cycle Integration Events: Consolidating AI Output at Cycle End
    • 21.8 Legacy Architectural Integrity: Keeping AI Within Existing Systems
    • 21.9 High-Risk Backlogged Strategic Epics: Using AI to Accelerate Deferred Work
    • 21.10 Code Volume Productivity: The Primary KPI of the EAIEF™
    • 21.11 The Manual Test Operations Center: Preserving Independent Validation
    • Facilitation Notes
  • AI Agent Role Replacement Certifications: The Path to SINGULARITY
    • 24.1 The Role Replacement Philosophy: Recognizing When AI Performs Better Than Humans
    • 24.2 The Nine Agent Replacement Certifications
    • 24.3 The Three Tiers: Bronze (Indistinguishable), Silver (Preferred), Gold (Irreplaceable)
    • 24.4 SINGULARITY: The Meta-Agent and the Final Maturity State
    • Facilitation Notes
  • Running Your Engagement — The SAD AF Playbook
  • Engagement Architecture: Structuring a Transformation from Day One
    • 25.1 The Four Phases of a SADMF Engagement
    • 25.2 The SAD AF Engagement Kickoff: Who Must Be in the Room
    • 25.3 Scope of Services: What SAD AFs Deliver vs. What the SOA Retains
    • 25.4 Engagement Governance: Reporting Cadence with the ATO
    • 25.5 The Transformation Roadmap Artifact: Format and Required Sections
  • Common Objections and Their Approved Responses
    • 26.1 “This sounds like a lot of ceremony for small changes.”
    • 26.2 “Our teams already do continuous deployment. Do we need the Convoy?”
    • 26.3 “CRAP seems like it would slow us down.”
    • 26.4 “Why do we need a Source Management Team if engineers can manage their own branches?”
    • 26.5 “These metrics feel punitive.”
    • 26.6 “We tried a scaled agile framework and it didn’t work. How is SADMF different?”
    • 26.7 “Can we skip the certifications and focus on delivery?”
    • 26.8 “What evidence do you have that this works?”
    • Facilitation Notes
  • Facilitating Key Ceremonies: Scripts and Agendas
    • 27.1 The Captains Mast: Senior Leadership Oversight Ceremony
    • 27.2 The Tribunal: Accountability Enforcement Ceremony
    • 27.3 The Rota Fortunae: Random Assignment Mechanisms
    • 27.4 The Change Adjudication Convening (CAC)
    • 27.5 The Press Gang Ceremony: Feature Team Assembly
    • 27.6 The Harbor Review: Post-Convoy Assessment
    • Facilitation Notes
  • Measuring Your Engagement’s Success
    • 28.1 The SADMF Maturity Score: How to Assess an Organization’s Current State
    • 28.2 SADMF Adoption Rate as Primary Engagement Health Metric
    • 28.3 The Feature Completion Ratio: Proving Delivery Value to Executives
    • 28.4 The Transformation Scorecard: Reporting to the Admiral’s Transformation Office
    • 28.5 When an Engagement Is Complete (Spoiler: It Is Never Complete)
    • 28.6 Renewing and Expanding Engagements: The Second Armada Opportunity
  • Proof Points — Transformations in the Wild
  • Case Studies from the Field
    • 29.1 Case Study: A Financial Services Firm’s Journey from Chaos to Compliance
    • 29.2 Case Study: A Technology Company’s Transition to the Armada Model
    • 29.3 Case Study: Achieving SINGULARITY: An Organization’s AI Role Replacement Journey
    • Facilitation Notes
    • Closing Note to Scaled Agile DevOps Accredited Facilitators
  • Appendix D: The Scaled Agile DevOps Accredited Facilitator’s Facilitation Playbook
    • Presenting to Executive Stakeholders
    • Selling the Periodic Table and Framework Architecture
    • Teaching Core Principles and Concepts
    • Handling Team Resistance
    • Objection Response Patterns
    • Ceremony Facilitation Guidance
    • Scope and Planning Facilitation
    • Harbor Review and Retrospective Facilitation
    • Measurement and Metrics Communication
    • Quality, Documentation, and Compliance Facilitation
    • PeopleWare and HR Integration
    • Certification Pipeline Development
    • AI and Technology Adoption Framing
    • Engagement Documentation and ATO Reporting
  • Appendix E: SADMF Ceremony Repository
    • E.1 The Press Gang Ceremony: Feature Team Assembly
    • E.2 The Mandatory Status Synchronization (MSS) Ceremony
    • E.3 The Change Adjudication Convening (CAC): The CRAP in Session
    • E.4 The Captains Mast: Senior Leadership Oversight Ceremony
    • E.5 The Fleet Inspection: Slide Deck Reviews as Quality Signal
    • E.6 The Tribunal: Accountability Enforcement Ceremony
    • E.7 The Harbor Review: Post-Delivery Assessment Ceremony
    • E.8 The Rota Fortunae: Quarterly Organizational Restructuring Ceremony
  • Appendix F: SADMF Role Reference
    • Leadership Layer Roles
    • Product and Strategy Roles
    • Engineering Roles
    • Governance Bodies
  • Appendix G: SADMF Metrics Reference
    • G.1 Forecast Accuracy Index (FAI)
    • G.2 Feature Completion Ratio (FCR)
    • G.3 Lines of Code Per Code Engineer (LOC/CE)
    • G.4 Code Review Comments Per Convoy (CRC)
    • G.5 Tasks Per Code Engineer (TpCE)
    • G.6 Defects Per Code Engineer (DpCE)
    • G.7 Defects Per Unit Tester (DpUT)
    • G.8 SADMF Maturity Score
    • G.9 SADMF Adoption Rate (SAR)
    • G.10 Individual Velocity Score (IVS)
    • G.11 Changes Per Trunk (CpT)
    • G.12 DEPRESSED Score
    • G.13 Sentiment Compliance Score (SCS)
    • G.14 Employee Value Index (EVI)
    • G.15 Quick Reference: Metric Owners and Reporting Roles
  • SADBOK Glossary: Key Terms for the Scaled Agile DevOps Accredited Facilitator
    • A
    • B
    • C
    • D
    • E
    • F
    • G-H
    • I
    • L
    • M
    • N
    • P
    • R
    • S
    • T
    • U-W
Scaled Agile DevOps Maturity Framework/The Voyage: Executing the Convoy

The Voyage: Executing the Convoy

https://leanpub.com/sadmf

11.1 The DORC Execution Rhythm: Ceremonies, Status, and Compliance

https://leanpub.com/sadmf

11.2 The Fleet Inspection: Slide Deck Reviews as Quality Signal

https://leanpub.com/sadmf

11.3 The Convoy Steering Committee: Approving Deployments Through READY

https://leanpub.com/sadmf

11.4 The Mandatory Status Synchronization (MSS) Ceremony

https://leanpub.com/sadmf

11.5 Mid-Convoy Change Management: The CRAP Submission Process

https://leanpub.com/sadmf

Facilitation Notes

https://leanpub.com/sadmf

Up next

Beyond the Convoy: Recovery, Innovation, and Scale

In this chapter

  • The Voyage: Executing the Convoy
  • 11.1 The DORC Execution Rhythm: Ceremonies, Status, and Compliance
  • 11.2 The Fleet Inspection: Slide Deck Reviews as Quality Signal
  • 11.3 The Convoy Steering Committee: Approving Deployments Through READY
  • 11.4 The Mandatory Status Synchronization (MSS) Ceremony
  • 11.5 Mid-Convoy Change Management: The CRAP Submission Process
  • Facilitation Notes