Your DevOps Journey: Amplifying Feedback

  • 19 Videos | 1h 8m 16s
  • Includes Assessment
  • Earns a Badge
Feedback often gets overlooked in lieu of the pace at which business moves, but organizations ignore the importance of feedback at their own peril. In this course, you’ll learn how DevOps thrives by amplifying feedback, beginning with the principles and practices of amplifying feedback and the importance of identifying problems as they occur. Then you’ll discover the importance of pushing quality closer to the source, optimizing for downstream workflow, telemetry metrics, monitoring, and alerting, telemetry from an architectural standpoint, and levels of telemetry architecture. Finally, you’ll explore the role played by alerting in automation, system monitoring tools and their uses, log aggregation tools, DevOps metrics, how telemetry can be used to anticipate problems, hypothesis-driven deployment, and A/B testing and how it relates to hypothesis-driven development. This course was originally created by Global Knowledge (GK). 

WHAT YOU WILL LEARN

  • describe the principles and practices of amplifying feedback
    discuss the scenario where the Microsoft VSO team had to find a way to make and release necessary changes to address instability
    describe how the Microsoft VSO addressing instability scenario is an example of how to establish mechanisms that can help to identify problems as they occur
    identify problems as they occur
    identify the importance of pushing quality closer to the source
    describe the importance of optimizing for downstream workflow
    define telemetry metrics, monitoring, and alerting
    discuss telemetry from an architectural standpoint
    describe the levels of telemetry architecture in order to think in terms of the types of information that you are capturing
    discuss the role played by alerting in automation
  • describe various system monitoring tools and their uses
    discuss the role played by log aggregation tools
    describe common DevOps metrics
    discuss how telemetry can be used to anticipate problems
    describe how telemetry information can help to understand whether problems occur during deployment
    discuss how hypothesis-driven deployment can be leveraged to guide development
    describe the Microsoft VSO hypothesis-driven deployment scenario
    discuss takeaways from the Microsoft VSO hypothesis-driven development scenario
    describe A/B testing and how it relates to hypothesis-driven development

IN THIS COURSE

  • Playable
    1. 
    The Second Way: Feedback
    3m 9s
    UP NEXT
  • Playable
    2. 
    MS VSO Addressing Instability Case Study
    51s
  • Locked
    3. 
    MS VSO Addressing Instability Debrief
    1m 5s
  • Locked
    4. 
    Identifying Problems as they Occur
    2m 30s
  • Locked
    5. 
    Pushing Quality Closer to the Source
    3m 53s
  • Locked
    6. 
    Optimizing for Downstream Workflow
    2m 57s
  • Locked
    7. 
    Telemetry: Metrics, Monitoring, Alerting
    8m 9s
  • Locked
    8. 
    Telemetry Architecture Layers
    3m 31s
  • Locked
    9. 
    Telemetry Architecture Levels
    5m 51s
  • Locked
    10. 
    Create Alerts
    5m 15s
  • Locked
    11. 
    System Monitoring Tools - Introduction
    1m 35s
  • Locked
    12. 
    The Role of Log Aggregation Tools
    5m 31s
  • Locked
    13. 
    Common DevOps Metrics
    6m 18s
  • Locked
    14. 
    Using Telemetry To Anticipate Problems
    5m 40s
  • Locked
    15. 
    Feedback For Safe Deployment of Code
    6m 54s
  • Locked
    16. 
    Hypothesis-Driven Development
    2m 46s
  • Locked
    17. 
    MS VSO Hypothesis-Driven Development Case Study
    38s
  • Locked
    18. 
    MS VSO Hypothesis-Driven Development Debrief
    24s
  • Locked
    19. 
    A/B Testing
    1m 20s

EARN A DIGITAL BADGE WHEN YOU COMPLETE THIS COURSE

Skillsoft is providing you the opportunity to earn a digital badge upon successful completion of this course, which can be shared on any social network or business platform

Digital badges are yours to keep, forever.