Embrace the Chaos: Transforming Scrum Learning Through Experience and Minecraft

Published on
3 minute read

As I reflect on my experiences delivering the Applying Professional Scrum class, I can confidently say it’s my favourite course to teach. The reason? It consistently sparks some of the most profound epiphanies for my students.

In this class, we don’t just talk about Scrum; we live it. We engage in four sprints, and I’ve recently started incorporating Minecraft into these sessions. This approach has transformed the way we experience Scrum, making it not just a theoretical exercise but a practical one.

The First Sprint: Embracing Chaos

We kick off the course with a sprint right away. This initial sprint is crucial because it allows participants to use the techniques they’re accustomed to when organising their work. What often follows is a realisation of just how chaotic the process can be. Many students enter the classroom with little to no experience in gaming, let alone Minecraft, which adds an extra layer of complexity.

This first sprint simulates the real-world experience of embarking on a brand new product or project. Imagine stepping into a situation where you have no idea what’s next, who your customers are, or even who you need to collaborate with. It’s a whirlwind of uncertainty, and that’s exactly what we aim to replicate.

The chaos of that first sprint is not just a minor inconvenience; it mirrors the confusion that can linger in the early stages of any project. In reality, this state of disarray can persist for an extended period, especially when various voices come in, dictating how things should be done. Often, a project manager might step in, attempting to impose order, but the initial chaos is a common experience.

Learning Through Structure

After this chaotic introduction, we transition into teaching the fundamentals of Scrum. The course is structured over two half days, with the first half dedicated to the initial sprint and the second half to another sprint, following a comprehensive introduction to Scrum principles.

During this time, we cover essential Scrum practices, and students begin to grasp how to organise their work effectively. They engage in planning sessions, have meaningful conversations, and agree on their objectives for the next sprint. While not every team achieves perfect alignment, the act of striving for agreement is a significant step forward.

The Realisation: Understanding Scrum’s Value

The second sprint is where the magic truly happens. Armed with their newfound knowledge, students approach this sprint with a clearer understanding of how to manage the chaos. They conduct check-ins and reflect on their progress, leading to another epiphany moment.

It’s during this reflection that students begin to understand the true purpose of Scrum. They recognise the benefits it can bring to their real-world projects. This understanding is transformative; it shifts their perspective from merely following a framework to appreciating the value of agility in their work.

Conclusion: The Journey of Discovery

In conclusion, the Applying Professional Scrum class is more than just a course; it’s a journey of discovery. By experiencing the chaos of the first sprint and then applying structured Scrum practices, students emerge with a deeper understanding of both the framework and its real-world applications.

If you’re considering diving into Scrum, I encourage you to embrace the chaos and learn through experience. The insights gained from this process are invaluable and can significantly enhance your approach to agile methodologies. Remember, it’s not just about doing Scrum; it’s about understanding its purpose and the value it can bring to your projects.

My favourite agile course to deliver is the applying professional scrum class and it’s my favourite class to deliver because I think it generates some of the greatest epiphanies for students.

So in that class we actually practice scrum and that’s different from all the other classes as well.

We do four sprints. I’ve been adopting Minecraft in these sprints.

We break everybody up into teams. We do a sprint straight off the bat.

The reason we do the first thing we do is a sprint is that people use the techniques they’re used to in organising when they do the first sprint.

So there’s this huge realisation at the end of the first sprint about how chaotic it was and how difficult the process was. There are people in the classroom that have never used or played a game before, let alone Minecraft.

That simulates that real-world experience of when you get onto a brand new product or a brand new project and you’ve got no idea what’s next.

You get no idea what you need to do. You’ve got no idea who you need to speak to. You’ve got no idea who the customer is. I’m trying to figure that out.

That first sprint demonstrates the chaotic is not the right word. It just generates, I don’t know, the cluster of that first moment when you start working on a product or project.

In the real world, that can last for an incredibly long time.

Right, because there’s who comes in and tells everybody how they’re supposed to do stuff. At some point, maybe a project manager gets hired or a project manager is there and they manage to get around everybody, but it’s generally chaos.

So then we go into teaching them scrum.

We have a kind of, I guess it’s two half days. We’re going to teach them scrum, but the first part of the first half day is the sprint and the second part of the second half day is another sprint.

So we teach some scrum in between and then they go into that second sprint with that knowledge of here’s how we’re going to organise all the stuff we do in order to try and control the chaos and figure out what it is we’re going to do going forward.

They do planning, they have a conversation, they agree what they’re going to do.

That doesn’t always happen, but they have that agreement. They have those check-ins. They have that reflection at the end and they themselves, that’s the second epiphany moment for the students, is they realise what it is that they’re there for.

They realise what scrum is trying to achieve. They realise the benefit they could get from it in the real world.

Software Development

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Capita Secure Information Solutions Ltd Logo
Sage Logo
Illumina Logo
Emerson Process Management Logo
Xceptor - Process and Data Automation Logo
Akaditi Logo
Schlumberger Logo
New Signature Logo
Boeing Logo
SuperControl Logo
Boxit Document Solutions Logo
Slaughter and May Logo
Hubtel Ghana Logo
Brandes Investment Partners L.P. Logo
Deliotte Logo
Graham & Brown Logo
Workday Logo
Ericson Logo
Washington Department of Transport Logo
Washington Department of Enterprise Services Logo
Ghana Police Service Logo
New Hampshire Supreme Court Logo
Royal Air Force Logo
Department of Work and Pensions (UK) Logo
Milliman Logo
YearUp.org Logo
Deliotte Logo
Slicedbread Logo
SuperControl Logo
Schlumberger Logo