I've said we need to be open-minded, but please, don't misunderstand me. I don' mean we have to question everything. The sun will come up tomorrow. That is a certainty. There's no need think I could be wrong about that. Similarly, there are certain rules within Scrum we can be sure about. If we change those rules, We're creating a process other than Scrum. It might even be better than Scrum, but it's not Sc rum. And for a few minutes, I want to stick with just Scum. If we do, there are certain rules we DO NOT want violate. We don't need to waste time pondering whether they're right or not. These are things like sprints can't be longer than a month. Be done with something by the end of the sprint. and get together at the start of the sprint and figure out what you'll do in the Sprint. And for that last one, it's not saying there's some grandiose sprint planning meeting. It could just refer to a 30-second discussion. I wouldn't even call that a meeting, there is just some initial discussion of what are we going to work on that just helps team members all pull in same direction during the We want to be careful here. We don't want turn Scrum into a list of rules. In fact, I've deliberately never sat down and created what I'd consider a complete list Scum rules I'll probably need to someday just for myself, but I resisted so far. The Scrumb Guide or Agile Atlas are probably as close as we need. The danger with a list of rules is we start to lose creativity and spontaneity. So it's important we keep the list scrum rules to an absolute minimum. I think it is good to have a small set of rule that define what scrums is. Things that if you aren't doing them, the scrumb police can knock on your door and rightfully say, you are not doing scrumm. What that team is doing might be better than Scrum, but if they're violating a Scum rule, it's not Sc rum. Here's an example of going too far with a rule. Are you aware that one of the main books on Scrum says that the daily Scrom must be conducted left to right, starting with the person to the left of The Scram Master? Well, one Of The Scrum Masters at a client I worked with knew this rule and he insisted on it. If it was in the book, then this scrum master was going to follow it. His team knew that this rule was ridiculous, and so they rebelled. They'd go right to left, or they'd randomly, Or people would move around during the meeting. they would do anything but go left to right, like the scrumb master wanted them to do. The team was trying to show their scrumm master how ridiculous that rule is. Going left or right should never have been made a rule. A few rules are fine, but we want to keep them to a minimum.