Skip to content

Latest commit

 

History

History
70 lines (43 loc) · 4.05 KB

File metadata and controls

70 lines (43 loc) · 4.05 KB
title WebOps Certification
subtitle Chapter 1: WebOps
description Learn about the principles and benefits of WebOps.
permalink docs/certification/study-guide/webops
cms
drupal
wordpress
previousurl /certification/study-guide
nexturl /certification/study-guide/platform

What is WebOps?

  • Define WebOps and the principles it emphasizes.
  • Describe WebOps' impact on the lifecycle of a web application.
  • Describe why WebOps is particularly valuable for Open Source developers.
  • List three general problems that can be solved through the implementation of WebOps.

What Problems Does WebOps Solve?

  • Describe how WebOps helps solve collaboration bottlenecks between Marketing, Developers, and IT.

Shortening the Marketer/Developer Feedback Loop

  • Define the responsibilities of a marketing leader as a Product Owner of the website
  • Describe some of the common KPIs that a marketer is responsible for in order to deliver business impact through the website.
  • Explain how WebOps helps shorten the feedback loop between marketing and developers.

Creating a Partnership between IT and Marketing

  • Describe the types of challenges that IT leaders are typically most concerned about.
  • Explain why marketing teams might view IT as a bottleneck.

Reducing Friction for Developers

  • Explain some of the extra tasks a developer is typically expected to perform, beyond simply writing code.
  • Describe how putting WebOps guardrails in place ahead of time helps Developers be more productive and work more efficiently.

Optimized for Velocity

The best balance of people, processes, and platform technology is always shifting, even as the primary forces shaping that balance are fairly constant. The pressure to deliver more value leads to moving faster. The pressure to maintain stability can lead to moving slower.

Perhaps the most important breakthrough pioneered by the wider DevOps community was increasing safety and speed together. Instead of viewing the pressure to go fast and the pressure to stay stable as always opposed to each other, healthy DevOps teams find they can increase stability by making deployments a frequent occurrence. If the pressure to stay stable leads to rare deployments, then the fear of deployments builds. When deployments go from quarterly to monthly to weekly to daily to hourly and faster, the risks tend to go down. The unknown dangers of deployments get resolved as deployments happen more and more frequently.

The same virtuous cycle is possible through WebOps. Instead treating collaboration across IT and Marketing as a rare event happening only around big, drawn out relaunches, a WebOps team collaborates constantly. As the targets for success constantly move, a healthy team of cross-functional people uses an iterative process on top of a stable platform.

  • Maximizing the impact of the website requires harmonious synchronization across multiple departments, including Marketing, Developers, and IT.
  • WebOps allows Marketing, Developers, and IT to collaborate more effectively and efficiently around the delivery of a marketing website.
  • WebOps shortens the feedback loop between Marketers and Developers by facilitating communication, providing collaboration tools, and giving the Developers the tools necessary to share their progress with multiple stakeholders in real time.
  • WebOps allows Marketing and IT to become strategic partners by ensuring that each team has the tools and automation in place to satisfy the critical metrics that each team cares about.
  • Pantheon allows Developers to focus on what they do best by providing a best-in-class web development environment, multiple environments, and time-saving automation capabilities.