An Experimenter’s Guide to SCRUM

This post covers some Scrum vocabulary and processes that product teams use and how they align with the process experimenters’ use.

Let’s start with a basic question — why do experimenters need to understand Scrum?

Experimenters need to understand Scrum because a large number of organizations are using Agile & Scrum practices and you are likely at one such organization. Typically, such organizations are focused on adding value to their customers through their product. Running experiments provides insights all throughout the product lifecycle from discovery to exploration to validation. So, many product teams either have experimentation resources embedded or rely on a central team (Centre of Excellence) within the org to support their experiments.

Either way, experimenters work closely with product owners and other stakeholders who are already familiar with Scrum. So, it helps to speak the same language and have similar practices to inspire more confidence in the experimentation process and get buy-in from across the organization.

Scrum framework also provides a great blueprint for experimentation processes as we’ll dive into in a bit. Experimentation is equal parts art and science but a lot of it is driven by disciplined processes. The scrum framework is great for identifying potential gaps in those processes and making them more efficient.

What is Scrum?

My exploration started with reading this post on the SmoothApps blog which curated a treasure trove of other resources. The blog linked to the Scrum Guides which contains the definition of Scrum and explains each element of the framework in a straight-forward jargon-free manner. Many of the sections below have been picked up directly from the Scrum Guide since I didn’t want to lose the essence in translation.

Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems. In a nutshell, Scrum requires a Scrum Master to foster an environment where:

* A Product Owner orders the work for a complex problem into a Product Backlog.

* The Scrum Team turns a selection of the work into an Increment of value during a Sprint.

* The Scrum Team and its stakeholders inspect the results and adjust for the next Sprint.

* Repeat

The Scrum Team is a cohesive unit of professionals — one Scrum Master, one Product Owner, and Developers — focused on one objective at a time, the Product Goal. The Scrum framework is purposefully incomplete, only defining the parts required to implement Scrum theory. So, rather than provide people with detailed instructions, the rules of Scrum guide their relationships and interactions.

Scrum combines four formal events for inspection and adaptation within a containing event, the Sprint. These events work because they implement the empirical Scrum pillars of transparency, inspection, and adaptation. And this is where experimenter’s can benefit from understanding Scrum.

How can experimenters align with Scrum?

Let’s examine each of these pillars.

Transparency

The emergent process and work must be visible to those performing the work as well as those receiving the work. With Scrum, important decisions are based on the perceived state of its three formal artifacts —

  • Product Backlog
  • Sprint Backlog
  • Increment.

While it is hard to map experimentation artifacts 1:1 with those of Scrum, here are some thoughts:

Inspection

The Scrum artifacts and the progress toward agreed goals must be inspected frequently and diligently to detect potentially undesirable variances or problems. To help with inspection, Scrum provides a set of events contained in a sprint.

Sprints are the heartbeat of Scrum, where ideas are turned into value. They are fixed length events of one month or less to create consistency. A new Sprint starts immediately after the conclusion of the previous Sprint.

All the work necessary to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, happen within Sprints.

Each event in Scrum is a formal opportunity to inspect and adapt Scrum artifacts and are specifically designed to enable transparency.

Events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum. Let’s look at each of these events and how they align with the experimentation process.

Adaptation

If any aspects of a process deviate outside acceptable limits or if the resulting product is unacceptable, the process being applied or the materials being produced must be adjusted. The adjustment must be made as soon as possible to minimize further deviation.

In the context of experimentation, this means constantly trying to optimize the experimentation process. We should use every test as an opportunity to improve our processes — workflow, prioritization, sources of hypotheses, reduce bugs/ errors, etc.

On the path to learning all things insights and optimization (linkedin.com/in/bithikamehra) | Foodie | Environmentalist| Loves to travel | Player of a few riffs

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store