None of the "breakers" are picky: you'll find most of them in the Table of Contents of the Scrum Guide.

= = = = = = = = = = = =

New for 2024: my best-ever training:
"How Your Agile Teams Can Achieve Predictability and Productivity WITHOUT Burnout"
→ https://www.developmentthatpays.com/w...

= = = = = = = = = = = =

Check out the full Scrum Guide here: https://scrumguides.org/




-------------------
158. 13 ways to BREAK Scrum. (Easier than you think.)
#scrum # scrumguide #DevelopmentThatPays

Scrum, as I'm sure you know, is a framework. And because it's a framework we can adapt it to our needs. It's actually highly adaptable. As the Scrum guide says, it "functions well as a container for other techniques, methodologies and practices." We can add, but we can't take away. Welcome to Development That Pays, the number one agile channel on YouTube. My name is Gary Straughan and I have a question for you. Did you by any chance do French at school I did, and I was particularly bad at it. And the thing I was most bad at was dictation. I found the marking process, you know that thing where you swap books and mark each other's work Yeah, I found that rather humiliating. You know the way it works, 10 points to start with. Lose a mark for every big mistake, a half point knocked off for a misplaced accent or a mixed up gender. I can tell you that a mixed up accent was the least of my problems. By the end of the first sentence I was inevitably every time down to null points. But I'm sure you'll do much better as we play a similar game with Scrum. You're gonna start with 10 points and knock one off for every time your version of Scrum differs from the Scrum guide. And don't worry, there'll be no pickiness on my part. We're gonna keep things very high level and there'll be no judgment either. I can tell you that most of the Scrum teams I've been a part of would've struggled to hold on to all 10 points, but you just might. Let's take a look. Over to the Scrum guide and I think we're gonna find most of what we need right here in the table of contents, specifically these four sections. Scrum values, Scrum team, Scrum events, and Scrum artifacts. Let's get things off to a gentle start with a look at those values. Successful use of Scrum depends on people becoming more proficient in living five values. Commitment, focus, openness, respect and courage. This section is a relatively recent addition to the Scrum guide. The authors must have thought long and hard before including it, and for that reason I think we need to take it seriously. These values are not to be considered optional. Having said that, it's a tricky one to score for the purposes of our game here today. So unless you know your team is entirely lacking in one or more of the above, then I'm not gonna dock any marks. I'm gonna move a swiftly on to talk about Scrum events. Yes, you're right. Scrum team is the next one on the list but I'm gonna save that one for later. Your points will thank me. The Scrum events formally known as ceremonies are, the sprint, sprint planning, daily Scrum, sprint review and sprint retrospective. The sprint for me, perhaps for everyone is the defining feature of Scrum. So if you're doing Scrum I'm pretty sure that you're working in sprints. The guide describes a sprint as a fixed length event of one month or less. So lose a point here only if your sprint is longer than one month. And lose a point also if you flex the duration. Onto sprint planning. And again, if you're working in sprints I'm sure that you plan each of those sprints. So whereas I could get a little bit picky here I'm gonna move right along to the event that shares its name with the framework. I'm talking of course about the daily Scrum, also known as the daily standup. The Daily Scrum is a 15-minute event for the developers of the Scrum team. Drop a point if you don't do daily Scrum. Also drop a point if you don't do it every day. Now don't give me a hard time about this. After all, it's right there in the name. How are your points doing I thought I'd just ask before we get to the next two events. No reason. The purpose of the sprint review is to inspect the outcome of the sprint and determine future adaptations. Drop the point here if you don't do sprint reviews and yeah, drop a point here if you don't do a sprint review every sprint. The purpose of the sprint retrospective is to plan ways to increase quality and effectiveness. Drop a point if you don't do them. Also drop a point if you don't do them every single sprint. Did you just drop a point Nevermind, I'm sure things will improve as we move on to the next section, Scrum artifacts of which th
   • 13 ways to BREAK Scrum. (Easier than ...