Scrum disempowers developers
I find this article lacking, because it makes all of the same mistakes typical of these bandwagon anti-Scrum articles.<p>Despite working in a a Scrum team, I recognise <i>literally nothing</i> of the problems that are described. Our product owner works closely with both commercial and development groups to build the backlog. Pressure to build good technical solutions is reasonably balanced with commercial requirements. The development team is empowered to step in and request product changes when they think it&#x27;s necessary. This happens because we are a team of skilled professionals who want to deliver working things at reasonable pace, and this applies to both commercial and development groups.<p>There is a weird underlying assumption in these kinds of articles that implicitly seems to assume that Scrum will somehow turn a bad team into a good one. I have no idea where that comes from. A team using Scrum still needs skilled people who know how to do their jobs effectively – and that includes the scrum master and product owner roles. Introducing it into a good team can then help to reduce the impact of common software development issues. It doesn&#x27;t work for every company, team, or product – but that doesn&#x27;t mean its without value.<p>I&#x27;d be more interested in articles that talked a little about better processes that we can use. I&#x27;m absolutely open-minded about the idea that there are other legitimate and effective ways to deliver software other than Scrum, because it&#x27;s obviously the case. &quot;These are the problems with Scrum and this is why they aren&#x27;t a problem in &lt;other process&gt;&quot; is more valuable than &quot;If you have a bad team then Scrum is bad&quot;.