top of page
rebel scrum new logo 1.png

The framework is not the point

4 hours ago
4 min read
The Scrum framework is a means to an end.


I am not sure how many times I have explained to my kids that no, they probably won't use Calculus. And maybe they won't need to know the details of Earth Science. Or how Pride and Prejudice ends. But that's not the point. The point of going to High School is to learn how to learn. How to assimilate and analyze data. To find out what you're capable of and to give you confidence that yes, you can do that thing - whatever "that thing" is for you.


Scrum has something in common with Calculus, it turns out.



Scrum helps teams learn how to learn.


The framework of Scrum isn't the end goal. Just implementing Scrum by itself is helpful, but it's only the beginning. When you implement Scrum, you are implementing a way for the Scrum team to learn how to deliver value better.


Here's what I mean.



Role clarity empowers the team

The Scrum framework includes three accountabilities: the Product Owner (they decide what the team will work on next), Developers (they deliver the product) and a Scrum Master (they facilitate meetings and improve the adoption of Scrum.) The role clarity that comes from this simple framework is enormous. Whenever I see strife on a team, it often comes from a lack of role clarity. Scrum helps teams get beyond that. When it's clear what your job is, only then you can embrace it and get better at it.

Scrum events create a feedback loop.

Scrum has just enough structure to help teams plan frequently, work together to deliver something, inspect it, and adapt their plan, and talk about how they can do it better next time. That's what the five events of Scrum are all about:

  1. Sprint Planning is a time for the team to talk about what will be delivered in the next Sprint and how to work together to deliver it.

  2. The Daily Scrum is a touch point to monitor progress and possibly update the delivery approach.

  3. The Sprint Review is an opportunity for the Scrum team to meet with its stakeholders and get feedback on what was delivered

  4. The Sprint Retrospective is time set aside for the team to discuss how they can improve the way they work together.

  5. The Sprint itself is a timebox of less than one month or less. During this time, the team delivers a done increment of usable product.


Together the five Scrum events help the team create a cadence for getting feedback from the customer and talking about how they can work together better. They create a feedback loop that helps the Scrum team learn.

The artifacts make it clear what the plan for the product is, and who is doing what

Scrum includes artifacts like the Product Backlog and the Sprint Backlog that provide transparency on what the plan is for the product as well as the team's plan for delivering the Sprint. When you have visibility as to how work is proceeding in the Sprint Backlog, you can come up with ideas on how to improve your work process. And when you know what is in the Product Backlog and where the Product is going, you can better discuss what might be more valuable.

Deliver early and often

When you deliver something, you learn a lot about feasibility and also whether it is what the customer really wanted. You're reducing business and technical risk and getting value sooner. When teams use Scrum, they deliver something usable every Sprint. Frequent delivery shortens the learning loop, so you get feedback faster and learn from it.

Empiricism means learning by doing

Scrum isn't about just going through the motions. It's about using transparency as a tool that enables the team to inspect what was delivered and learn from it. The engine behind Scrum is Empiricism, a way to learn from experience and adapt based on what is learned. This doesn't get talked about enough. The superpower behind Scrum is that it is a learning engine when it's used effectively. Every artifact provides transparency, and every event is an opportunity to inspect and adapt. When you do that, you learn how to improve value delivery.

A clear Product Goal promotes learning

The Scrum framework includes the establishment of a Product Goal. I worked with a consumer products company a few years back, and our Product Goal was to increase sales. The team met to discuss how to achieve it, and we decided to take two paths: increase traffic with SEO and decrease shopping cart abandonment. After every release, we measured the impact of our changes. Having a clear goal and being empowered to meet it meant we ran experiments to see what worked and what didn't. When you work towards a Product Goal, you learn over time what changes are a good step towards that goal, and which are not.


And all of that adds up to a lot of learning and continuous improvement - but only when you realize that the framework was never the goal, but merely a means to an end. And that end is delivering value.



Conclusion

So no, most people will never use Calculus. But that was never the point. The point is learning how to learn. The Scrum framework is no different. When teams use Scrum, they learn how to work together effectively, how to deliver something of value, and they learn how to learn through experimentation and a focus on value delivery.

bottom of page