Cover image for DevOps and Business

DevOps and Business

Author Leon Fayer
Release Date: 2019/07/01
ISBN: 9781492036609
Topic:
0%
12
Chapters
0-1
Hours read
0k
Total Words
    Start Reading Now    
       Add to Wishlist       
View table of contents

Book Description

DevOps is much more than a set of practices to eliminate silos between development and operations groups. If your company’s DevOps transformation is to succeed, you need to blur the lines between business and technology domains. This report helps engineering leaders understand what drives the business and provides best practices for aligning technology with business goals to increase efficiency and improve the bottom line.

Author Leon Fayer, vice president of software development at Teaching Strategies, provides methods and techniques to help your organization improve cross-departmental processes, cooperation, and visibility. Getting IT and business groups to adopt DevOps principles will go a long way toward accomplishing that goal. This report shows you how.

  • Use practical strategies to teach stakeholders how DevOps can provide value for the business
  • Quantify the ROI value of DevOps implementation and culture changes
  • Determine the best ways to position technology groups to support business outcomes
  • Improve communication efficiency to identify mistakes and optimize service delivery
  • Understand the importance of continuous insight into business performance
  • Build empathy and trust by encouraging people to support common goals and solve problems together

Table of Contents

  1. 1. Introduction
    1. DevOps and Business
  2. 2. Setting the Stage
    1. Defining DevOps
    2. Educating Stakeholders
      1. DevOps Is Not a Product (or Suite of Products)
      2. DevOps Is Not Interchangeable with Other Industry Buzzwords
      3. DevOps Is Not a Separate Team
      4. DevOps Is Not a Staff Consolidation Technique
      5. DevOps Is Not New
      6. DevOps Is Not Just About Development and Operations
    3. Defining Your DevOps Goals
    4. Understanding the Impact of Change
      1. Complacency
      2. Personal Impact
      3. Lack of Trust
    5. Helping Teams to Embrace Change
      1. Address Personal Concerns
      2. Be Transparent
      3. Involve Affected Groups
  3. 3. Quantifying Success
    1. Organizational versus Departmental Goals
    2. Quantifying Success
    3. Applying the Appropriate Metrics
      1. Delivery Speed
      2. Value Stream Mapping
      3. Quality
  4. 4. Defining Responsibilities
    1. Technology’s Place Within the Organization
    2. Decision-Making Structure
      1. IT Responsibilities
      2. Business Groups Responsibilities
  5. 5. Improving Communication
    1. Education
      1. Educating IT Groups
      2. Educating Business Groups
    2. Continuous Communication
      1. Before the Start of the Delivery Cycle
      2. During the Delivery Cycle
      3. After the Delivery Cycle
  6. 6. Improving Visibility
    1. The Importance of Holistic Monitoring
    2. A Top-Down Monitoring Strategy
      1. Understand the Business Objectives
      2. Map Business and Technical Metrics
    3. Continuous Instrumentation
    4. Monitoring Processes
    5. Alerting
  7. 7. Improving Culture and Reaping Rewards
    1. Fostering Empathy
    2. Building Trust
  8. 8. Conclusion
18.118.0.240