Mastering Agility

The only constant in life is change. Organizations are dealing with constantly changing competition, new insights, innovation, and even culture. Mastering Agility aims to be THE content platform driven by the community to inspire and connect other agile practitioners.

Follow publication

Member-only story

Team Sauron’s Shapeshift: Adapting to Forge Success

Sander Dur
Mastering Agility
Published in
6 min readDec 12, 2023

Join the Mastering Agility Discord community!

Photo by Alessandra Verre on Unsplash

This article was co-written by Sabrina Love.

Meet Team Sauron. Sauron is a Scrum Team working at Magnum Opus, a company that creates biometric security machines. This team specifically is creating facial recognition software with highly sophisticated cameras. The team consists of the following people:

Product Owner — Ruben Blackstone
Scrum Master — Rafaela Higgins
Developers — John Doe, Joanna Doe, Anna Nonimous, No Wan Noes, Patty Kong

They have successfully delivered increments for 15 Sprints, but they have been struggling in the last three Sprints.

In the refinement session, the team runs into the same issues they had in the previous Sprints: they don’t have the right skills to address some of the upcoming work having to do with more advanced facial recognition software. Ruben, the Product Owner, is the first to recognize this impending impediment. The team has tried to refine these items before but they always seem to get stuck and ultimately agree to do some research offline. This is the third time they’ve tried, and now it’s becoming increasingly more risky to continue on the current path. Ruben presented the current state of the roadmap and Product Backlog that demonstrates an increasing amount of functionality depending on the missing skill.

Ruben raises his concern to the team; he’s worried that there are missing skills on the team that will prevent him from being able to do his job and maximize the value of the product they are building. A few Sprints have gone by where Ruben has acquiesced to the team’s request to do more research before diving into the advanced features. But they haven’t shown meaningful progress yet, and Ruben’s stakeholders are starting to get antsy. Which means Ruben is starting to get antsy. He needs a solution to this problem before the team runs out of funding. To Ruben’s credit, he presents the problem to the team and gives them the opportunity to figure it out.

The following week, the team reconvenes, and they have some proposals for Ruben:

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Mastering Agility
Mastering Agility

Published in Mastering Agility

The only constant in life is change. Organizations are dealing with constantly changing competition, new insights, innovation, and even culture. Mastering Agility aims to be THE content platform driven by the community to inspire and connect other agile practitioners.

Sander Dur
Sander Dur

Written by Sander Dur

PST at Scrum.org. Scrum Mastering from the Trenches. Podcast host at “Mastering Agility”, found on all big platforms. LinkedIn: www.linkedin.com/in/sanderdur

No responses yet

Write a response