<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jstimpfle</author><text>&amp;gt; Scrum isn&amp;#x27;t good or bad&lt;p&gt;I must have heard this at least a dozen times in the last months. OOP isn&amp;#x27;t good or bad, Exceptions aren&amp;#x27;t good or bad, Scrum isn&amp;#x27;t good or bad. It makes me mad. Guys and girls! Software is not a contest in being liberal and tolerant. There are methods and techniques that are objectively better than others in reaching most of the goals that are important. You wouldn&amp;#x27;t contest a F1 driver on a bicycle - not on a race track. And engineers who really know their stuff usually agree on how to build software in a given domain. I do not know of any success stories using Exceptions on Kernels or RDBMSs or even most server software. But I know people have tried, and even they agree it was a bad idea.&lt;p&gt;If you want to say Scrum isn&amp;#x27;t good or bad, depending on how you tweak it so it sucks less, then I say it&amp;#x27;s definitely bad. It&amp;#x27;s not a solid method that helps you reliably reach your goals.&lt;p&gt;If you want to say Scrum isn&amp;#x27;t good or bad unless metrics are defined (that doesn&amp;#x27;t seem to be the case here), then you are right, but it&amp;#x27;s a meaningless statement.</text><parent_chain><item><author>gregdoesit</author><text>Scrum isn&amp;#x27;t good or bad, but the way the OP (or their company) uses it seems to be a reflection of an inflexible culture.&lt;p&gt;For example, the OP argues how scrum strips engineers the autonomy they need to get the job done and how it&amp;#x27;s super inflexible. When we did scrum with my team, the scrum master role was rotated among engineers, growing each of us significantly as professionals. We also made changes to the &amp;quot;core&amp;quot; of scrum after our retrospectives when we decided it was stuff that did not work for us. When management tried to use story points for tracking or forecasting we told them to forget about the whole thing. We added bugfixing sprints after we observed the bugs piling up.&lt;p&gt;I can go on - we made scrum work in an environment where we were empowered to do what makes sense. The crux of the post seems to be that OP has some very rigid management and devs cannot change the mindset.&lt;p&gt;Instead of complaining about scrum, I suggest the OP either try changing the culture from the team level. Or if it won&amp;#x27;t work, just get out and work at a place where there is sane management who does not drink the rigid scrum kool-aid. Luckily, there are more and more places like that these days.</text></item></parent_chain></comment><story><title>A brief list of what Scrum gets wrong</title><url>https://medium.com/@ard_adam/why-scrum-is-the-wrong-way-to-build-software-99d8994409e5</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>codemac</author><text>&amp;gt; Scrum isn&amp;#x27;t good or bad.&lt;p&gt;There isn&amp;#x27;t enough evidence-based science on what produces the best software -- but Scrum &lt;i&gt;can&lt;/i&gt; be measured against other software practices, and should be.</text><parent_chain><item><author>gregdoesit</author><text>Scrum isn&amp;#x27;t good or bad, but the way the OP (or their company) uses it seems to be a reflection of an inflexible culture.&lt;p&gt;For example, the OP argues how scrum strips engineers the autonomy they need to get the job done and how it&amp;#x27;s super inflexible. When we did scrum with my team, the scrum master role was rotated among engineers, growing each of us significantly as professionals. We also made changes to the &amp;quot;core&amp;quot; of scrum after our retrospectives when we decided it was stuff that did not work for us. When management tried to use story points for tracking or forecasting we told them to forget about the whole thing. We added bugfixing sprints after we observed the bugs piling up.&lt;p&gt;I can go on - we made scrum work in an environment where we were empowered to do what makes sense. The crux of the post seems to be that OP has some very rigid management and devs cannot change the mindset.&lt;p&gt;Instead of complaining about scrum, I suggest the OP either try changing the culture from the team level. Or if it won&amp;#x27;t work, just get out and work at a place where there is sane management who does not drink the rigid scrum kool-aid. Luckily, there are more and more places like that these days.</text></item></parent_chain></comment><story><title>A brief list of what Scrum gets wrong</title><url>https://medium.com/@ard_adam/why-scrum-is-the-wrong-way-to-build-software-99d8994409e5</url></story>