Member-only story
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…
