Scrum disempowers developers
Like any and every business theory, Scrum has one or two core ideas that are awesome, but could be explained adequately in a paragraph or two. This does not sell books and consulting, so it evolved into a field of its own.<p>The fact that there is so much B.S. in Scrum doesn&#x27;t mean that it has nothing of value to offer, though.<p>Here&#x27;s what I get out of it:<p>1. Sprints are a better way to organize than Waterfalls. I&#x27;ve experienced this over and over again personally, so I&#x27;m sold on this.<p>2. It&#x27;s important to stop what you&#x27;re doing on a regular basis to evaluate progress and problems. This always seems like a waste in the moment, but failure to do so leads to regret down the line.<p>3. Ship functional products as frequently as possible. This is better than waiting until everything is done, because you can get feedback early and often from the end user.<p>Okay, so that&#x27;s 3 ideas. It&#x27;s better than most.