What’s the simplest thing that can possibly work and still be called Scrum? What Scrum “says” you have to do comes up plenty with teams I work with. Many have a difficult time remembering all the rules and get hung up in what they are. Or people blame Scrum for various reasons, like it insists on all these meetings or doesn’t allow for any up-front nor long-term thinking. That self-organization means hands-off. What are the rules, or the constraints of Scrum for teams to evaluate themselves against? What can people remember easily? It’s something I tried to discuss a bit … Continue reading →