Scrum.org’s Post

Scrum is NOT simple. The 2020 Scrum Guide states that Scrum is Simple. I can't entirely agree and that statement needs to change. Read the post for more. #scrum #scrummaster #productowner https://lnkd.in/gNG_prZK

Scrum as Scrum is immutable "and functions well as a container for other techniques, methodologies, and practices", so depending of what in include it can appear to be very different from team to team; and that is the part of the immutable thing that accepts changes. But, as they say, you can use only parts of Scrum as you see fit... only don't call it Scrum.

Are you doing Scrum? Did you ever check if you fulfill the preconditions to do so? Too often Scrum is applied in a way that sets it up for failure. I wrote about the most common preconditions teams miss in the Agile Compass: https://lnkd.in/edqhtd42 #scrum #agile #team

Large-Scale Scrum by Craig Larman and Bas Vodde is a nice book for organizations seeking to scale their agile practices beyond a single team and never experienced it before. The book Large-Scale Scrum offers a practical guide to implementing LeSS (Large-Scale Scrum), a framework that helps organizations achieve greater agility, faster delivery, and higher quality. With a focus on simplicity, transparency, and continuous improvement, More with #LeSS provides a case for scaling #agile and #scrum principles across multiple teams and complex systems. READ NOW: https://lnkd.in/dWhgk2FW

The false claim that "Scrum is immutable"! The Scrum Guide makes it clear that it's a flexible approach that welcomes change, including in Scrum itself, during implementation. Every part of the "Guide" (including its name) discusses flexibility and adaptation. However, many will rally around the battle cry that "Scrum is immutable" and scream about its lack of fundamental agility, forgetting that it's a "guide" and that its creators were one-sixth of those who created the Agile Manifesto. The paragraph that they take offence to is way down in the "endnotes" of the Scrum Guide and reads: "The Scrum framework, as outlined herein, is immutable. While implementing only parts of Scrum is possible, the result is not Scrum. Scrum exists only in its entirety and functions well as a container for other techniques, methodologies, and practices." I can kind of understand where the confusion comes from if one only reads the "The Scrum framework, as outlined herein, is immutable." and ignores the rest. Still, with the content of the rest of the guide, as well as the following sentence, it is quite explicitly clear that this refers to an immutability of definition and not of implementation! This is an extremely important distinction that results in the idea that: You don't have to implement Scrum as it says in the Guide at all. You can do whatever you want. All the Guide "asks" is that if we change the game's core rules, we should be honest, open, and transparent and that we are playing a different game. Is that too difficult a concept to grasp? The only people having these arguments are practitioners; for everyone else... it's irrelevant. Focus instead on the intent and purpose... ...are we delivering value regularly? ...are we getting feedback regularly? ...are we adapting our plans regularly? ...are we reflecting regularly? #TakeBackScrum #Scrum

Boost your Scrum and Agile team's performance with these essential tactics! Create a dynamic atmosphere by regularly reviewing practices, involving all team members, and focusing on solutions that put customers first. Applying these approaches will enhance team dynamics, stakeholder connections, and product excellence. Begin with small steps, prioritize practical changes, and nurture a culture of ongoing advancement for your team's success. #Scrum #Agile #Improvement #TeamSuccess

From the Scrum Guide: “Scrum is a lightweight framework…” Let’s have a closer look at what this means? From Cambridge Dictionary: Lightweight “Weighing only a little or less than average” … euh… Scrum is lightweight... Of course, we’re not worried about Scrum tipping the scales physically. But, in terms of for example process and role complexity, Scrum weighs much less compared to most “agile” methodologies. Lighter than other frameworks in that it brings us only the required parts. Only those parts that are really needed to support the teams applying its underlying theory. Less rules, less artifacts, less events, less process, less roles. Less. Just less; of everything. Note though that less isn’t about cutting corners, it’s about cutting out the noise. Fewer rules don’t mean chaos, they give more space for teams to innovate and self-manage. If you feel it is about “more”, then something in your use of the Scrum framework is not working as intended; inspect this. Then adapt. So, how are you using Scrum as it is intended, as a lightweight framework? If your Scrum feels heavy, bloated, or rigid, ask yourself: Have you bolted on extra processes, tools, or roles that aren’t in the Scrum Guide? Are you still using Scrum as a lightweight framework, or has it become something else? These are core concepts I cover in my Professional Scrum courses. Interested in more? Watch out for upcoming posts or take contact for more clarifications. Don't want to miss any of these posts? You can have them weekly in your mailbox via https://lnkd.in/eDkNgYTs Wishing you an inspiring read and a wonderful journey. Have fun. Scrum on. #BoostYourScrum #ProfessionalScrum #Scrum #ScrumMaster #RulesOfTheGame Scrum.org

Let's talk about a common trap I've seen as a Scrum Master: aiming for perfection, force teams to use specific "best practices" and micromanaging every Agile event can hold back team autonomy. 👮🏻♂️🚨 This is not the sake of our role! While it's crucial to teach new teams initially, it's equally important to step back and let them navigate their own challenges. Remember, you're there to coach and enable them to find their own way (not your way). 😉 Embracing the journey of trial and error is where true learning happens. 💡 Let's empower teams to experiment, make mistakes, and grow! 💪 #Scrum #ScrumPolice #Agile Please take a look of this great article by Brett Maytom!

This post dives into the top ten actionable strategies derived from the Scrum Anti-Patterns Guide book by PST Stefan Wolpers , providing a roadmap for teams eager to embrace Kaizen practices. English: https://ow.ly/Z2cr50QYiwM German: https://ow.ly/LFzf50QYiwI #Scrum #Agile

Motivation for knowledge workers must be intrinsic (not extrinsic). And, if they (the team members) are not motivated after 1 year, THAT is a big problem. To over-simplify, motivation has two factors. #Scrum #Agile