The three dimensions of enterprise DevOps

Contents

• Introduction Introduction

  • Transforming your organization

    1m 35s
• 1. Why DevOps at the Enterprise level? 1. Why DevOps at the Enterprise level?

  • (Locked)
    Why is the enterprise level different?

    2m 59s
  • (Locked)
    The role of corporate culture

    4m 19s
  • (Locked)
    The three dimensions of enterprise DevOps

    2m 57s
  • (Locked)
    Transformation is a continual process

    4m
• 2. Where to Start 2. Where to Start

  • (Locked)
    Analyze your application portfolio

    2m 48s
  • Find a minimum viable cluster (MVC)

    3m 1s
  • (Locked)
    Use the MVC to uplift capabilities

    3m 27s
• 3. Value Stream Mapping 3. Value Stream Mapping

  • (Locked)
    What is a value stream map (VSM)?

    2m 7s
  • Creating value stream maps

    3m 22s
  • (Locked)
    Using value stream maps

    2m 30s
• 4. Tooling at the Enterprise Level 4. Tooling at the Enterprise Level

  • (Locked)
    Types of DevOps tools

    3m 56s
  • (Locked)
    Making the right choices

    2m 56s
  • (Locked)
    Central vs. federated approaches

    2m 40s
• 5. Vendor Management 5. Vendor Management

  • (Locked)
    Include vendors in the journey

    2m 43s
  • (Locked)
    Contracts and incentives

    2m 45s
  • (Locked)
    Implement engineering standards

    3m 35s
• 6. Steering the Transformation 6. Steering the Transformation

  • (Locked)
    Use the Deming cycle

    2m 33s
  • (Locked)
    Transaction costs and batch sizes

    2m 33s
  • (Locked)
    A transformation scorecard

    3m 3s
• 7. Organizational Structure 7. Organizational Structure

  • (Locked)
    DevOps organizational patterns

    2m 53s
  • (Locked)
    Using a central team

    3m 17s
  • (Locked)
    How to make a DevOps team work for you

    3m 22s
• Conclusion Conclusion

  • (Locked)
    Next steps

    18s