Skip to main content
    DevOps
    Way of Working
    1. Home
    2. Capabilities
    3. Operate Iac

    Infrastructure as Code

    Foundation
    Phase: operate
    DF
    MTTR

    Quick Reference

    Phase
    operate
    Epic
    Infrastructure & Operations Baseline
    Milestone
    Foundation
    Target
    >= 70% infrastructure in IaC
    Implementation Time
    Part of Infrastructure & Operations Baseline epic: 4 weeks (32 hours per capability avg)

    What & Why

    Definition

    >= 70% of infrastructure managed via IaC (Terraform, Pulumi, CloudFormation) in version control.

    Business Value

    Prevents infrastructure drift entirely and reduces environment provisioning time from 2 weeks to 2 hours through versioned infrastructure code Achieving >= 70% infrastructure in IaC is a key milestone toward this goal.

    Context

    This capability is part of the Foundation milestone's focus on establish baseline practices (testable, releasable, monitorable). Essential for teams targeting DF, MTTR improvements.

    Success Criteria

    Target

    >= 70% infrastructure in IaC

    Measurement

    Infrastructure inventory vs IaC-managed resources

    Evidence

    • IaC code repository
    • Resource tagging
    • IaC coverage reports

    In Practice

    Real-World Implementation

    Teams define infrastructure in Terraform modules, store in Git, apply via CI/CD, track resources with tags.

    Concrete Example

    AWS resources: 150 total. IaC-managed: 120 (VPCs, EC2, RDS, S3). Manual: 30 (legacy systems being migrated). 80% IaC coverage.

    Implementation Guide

    Implementation Steps

    Follow the measurement approach: Infrastructure inventory vs IaC-managed resources

    For detailed step-by-step guidance, refer to the Infrastructure & Operations Baseline Implementation Kit.

    Resources

    Implementation Kit

    Infrastructure & Operations Baseline Kit

    Templates

    Browse all templates

    Related Resources

    View learning paths

    Related Capabilities

    Enables

    What this unlocks

    Autoscaling Configuration
    GitOps Deployment Model

    Complementary

    Often adopted together, from the Infrastructure & Operations Baseline epic

    Operational Runbooks
    On-Call Rotation
    Backup and Recovery

    Troubleshooting & FAQs

    Common Issues

    Issue: Target metric not improving

    Solution: Verify measurement is accurate, check if prerequisites are fully implemented, review evidence artifacts for completeness

    Issue: Team resistance to adoption

    Solution: Start with pilot team, demonstrate value with metrics, provide training and support during transition

    Issue: Inconsistent implementation across teams

    Solution: Create shared templates and guidelines, establish regular sync meetings, use automation to enforce standards

    Frequently Asked Questions

    Can we implement this before completing prerequisites?

    While possible, it's not recommended. Prerequisites ensure foundational practices are in place, making this capability more effective and easier to adopt.

    How long does implementation typically take?

    Most capabilities can be implemented within 90 days when tackled as part of the Foundation milestone. Individual timelines vary based on team size and existing practices.

    DevOps
    Way of Working

    DevOps practices for the entire delivery lifecycle

    © 2019-2026 devopswow.com. Created by Burhan Öcüt

    PartnersAboutPrivacyTermsCookies