Mastering Scrum Complexity: Navigate the Agile Landscape
Unlock the secrets to navigating Scrum complexity with ease! Dive into our insightful exploration of agile project landscapes. Learn to adapt and thrive in a world of change.
Enjoy this video? 🔔 Like and subscribe to our channel:
https://www.youtube.com/@nakedAgility
In this video, Martin delves deep into the essence of Scrum, the backbone of agile project management. 🌟 Discover the crucial difference between complicated and complex tasks and why understanding this is key to your team’s success. 🧩 Experience the dynamism of complexity through hands-on exercises that bring theory to life. 🎮 Join us as we decode the intricacies of Scrum with practical insights and actionable strategies.
Key Takeaways:
00:00:00 Introduction to Complexity in Scrum
00:01:00 Adjusting Processes for Increased Complexity
00:02:00 Empirical Learning with Minecraft and Website Building
00:03:00 Scrum Artifacts and Transparency for Risk Mitigation
NKD Agility can help!
These are the kinds of issues that lean-agile practitioners love and most folks hate, and if you find it hard to navigate the complexities of Scrum, my team at NKDAgility can help you or help you find a consultant, coach, or trainer who can.
If you have issues that are undermining the effectiveness of your value delivery, it’s especially important to find help as soon as you can and not wait!
You can request a free consultation:
https://nkdagility.com/agile-consulting-coaching/
Sign up for one of our upcoming professional Scrum classes:
https://nkdagility.com/training-courses
Because you don’t just need agility, you need Naked Agility.
#scrum #agile #projectmanagement #productdevelopment #agilecoach #agileconsultant #agiletraining #scrumtraining #scrumorg #scrummaster #productowner #kanban #continuousdelivery #devops #azuredevops
Watch on Youtube
So the most useful element of the APS class for beginner Scrum teams is really that grounding in understanding complexity and empiricism. Right, um, so that’s something that we really focus on and double down on those two things. So the first one is complexity, right?
There is a difference as you increase in complexity, and usually it’s an exponential scale, right? The type of processes and practices that you use need to change as you increase in complexity. So if we have very low complexity, um, let’s say it’s just complicated or even it’s simple, then we can probably plan further out into the future and be okay. Right? We can plan, let’s say we’re running a textile mill and we have a thousand machines producing fabric. Um, in general, you’ll be able to predict how long to a very high degree of accuracy it will take to fulfil whatever order comes in, right? Because you understand the cadence of the machines, you understand how long it takes to retool the machines for different types of fabrics or different patterns. You already understand all of that stuff up front, and it’s fairly consistent.
There’s the odd thing: a machine breaks down, something else goes wrong, somebody gets injured, right? These are all things that can surprise you or get in the way, but generally the variance is very small. As soon as you get into really high variance work, the APS really focuses on that piece, that high variance work, and quantifies what does it look like and how does it feel, right? How does it feel for the people involved?
Um, so we do that through an exercise that enables people to experience complexity. Depending on which class you go to will depend on what experience that is. Uh, we’ve done building websites, uh, we’ve done Minecraft, right? That’s my favourite one, is using Minecraft in that class, um, to create that complexity so that people actually feel it. Once they realise the difference between complicated and complex, they feel it. Then we can start talking about, well, how do we mitigate risk in that world of complexity?
And that’s where we focus very heavily on transparency, inspection, and adaption, right? That’s why we talk about the definition of done really heavily. We talk about the product backlog and why it needs to be transparent. Um, we talk about the Sprint backlog and why it needs to be transparent. All of those things are the important piece because everything else is built on top of it.
There’s no point in doing a Sprint review unless you have a transparent product to look at. There’s no point in doing a Sprint planning unless you have a transparent product backlog to look at. You need those, um, artifacts, those three artifacts in Scrum with their commitments in order to be able to do everything else, and that’s what makes it valuable.
Thanks for watching the video. If you enjoyed it, please like, follow, and subscribe. I always reply to comments, and if you want to have a chat about this or anything else Agile, Scrum, or DevOps, then please book a coffee with me through Naked Agility.
