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.
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
Unlocking Agile Mastery: How the Minecraft Case Study Transforms Training and Team Dynamics
Discover how using a Minecraft-based case study enhances Agile training by boosting engagement, illustrating complexity, and improving team …
Pragmatism crushes Dogma in the wild
Explores how practical use of Scrum fosters adaptability and resilience in teams, highlighting the value of flexibility over rigid rules in …
Transform Your Career: How to Become a Confident Scrum Master Through Real-World Learning and Community Support
Learn how practical training, real-world application, and community support help you build confidence and skills to succeed as a Scrum …
Transform Your Agile Training: The Power of Immersive Learning for Lasting Impact
Explores how immersive learning in Agile and Scrum boosts retention and real-world application by using spaced sessions, practical …
Why is Lego a shit idea for a scrum trainer - Part 3
Explores why Lego may oversimplify Scrum training, contrasting it with Minecraft’s ability to reflect real-world complexity and …
Transforming Scrum Training: How Real-World Insights Empower Agile Teams at Great Calm
Explores how practical, real-world Scrum training at Great Calm improved team collaboration, alignment, and continuous improvement across …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar
Is your team’s “done” really done? Discover how a clear, objective definition of done boosts quality, agility, and trust in product …
Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster
Stop confusing acceptance criteria with definition of done, learn the crucial difference to boost quality, speed, and trust in your agile …
How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum
Unlock a smarter Definition of Done, start small, evolve standards, and build team momentum without overwhelm. Discover how progress drives …
Why Most Transformations Fail Without Honest Conversations
Most transformations fail without open, honest conversations that address real issues, making transparency and tough dialogue essential for …
Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth
Transform your definition of done into a strategic advantage, deliver real value, reduce risk, and drive business impact with every sprint.
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Kendall Guide - A System of Work for AI Adoption
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …