<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>isityouyesitsme</author><text>Scrum as a concept doesn&amp;#x27;t matter. Agile as a thing doesn&amp;#x27;t matter. Team structure doesn&amp;#x27;t matter.&lt;p&gt;All that matters is who has authority and the business both enforcing that authority and also making sure that authority is being used to accomplish business efficiently and not causing greater risk in the process. The rest just falls in to place. Or doesn&amp;#x27;t, and the business dies.</text><parent_chain><item><author>bartread</author><text>I agree with your second point but...&lt;p&gt;&amp;gt; I don’t think it does unless you take a dim view of it and perpetuate the simplistic scrum-agile bad meme.&lt;p&gt;Look, the thing is, if you&amp;#x27;ve worked in a load of different organisations, and lots of different teams, with other smart people and have never really seen Scrum done well, and have in some cases actively seen it inhibit the delivery of quality software, I think it&amp;#x27;s legitimate to start questioning the process. People - smart people - struggle to make it work effectively. Plus, 50% of software developers (UX, product management, QA, SRE, stakeholders, etc.) are worse than average: a process that top quartile people struggle to make work well, sometimes even under the most favourable of circumstances, is less valuable when broadly applied across the delivery professions as a whole, and over different industry sectors.&lt;p&gt;On the flip side, with any process being introduced, I think it&amp;#x27;s fair to spend some time, maybe 6 months (but it will vary, depending on the process), implementing that process fairly strictly. It does need time to bed in, and there will be areas of friction simply due to creating new habits or resistance to change rather than due to problems with the process during that time. You need time for those issues to shake out so that you can see how much value the process itself really delivers and where it can be improved. At the 6 month point you can review the process, implement improvements, and move forward. You can keep doing the same review&amp;#x2F;evolve process on whatever cycle you choose, and that way your processes are more in step with changes in the wider organisation (hopefully growth).&lt;p&gt;Your processes need to fit your organisation, your business model, your culture. So, by all means, you can start with a process like Scrum, but to be really successful with it you need to treat it as just that: a starting point. You need to evolve it to fit your business. We all like to mock cargo-culting and yet, somehow, Scrum and agile often seem to blag a free pass. I don&amp;#x27;t understand why, because they shouldn&amp;#x27;t get that free pass. Your processes need to work for your business, and they are always a means for delivering value and never an end in themselves.</text></item><item><author>ljm</author><text>I don’t think it does unless you take a dim view of it and perpetuate the simplistic scrum-agile bad meme.&lt;p&gt;An easy way to throw an effective team into disarray in tech is to waylay it with back channel requests and unplanned work. If you’re too busy fighting fires and working personal errands for disruptive managers and executives then you’re not delivering what your team is supposed to deliver.&lt;p&gt;The ‘proper channel’ isn’t a bureaucracy as described in the SSFM, it’s simply an ordered list of priorities with a gatekeeper.&lt;p&gt;Edit: as far as dogmatically adhering to this process goes, then any effective agile&amp;#x2F;scrum process will have a baked in allowance to handle the unexpected or adapt to change, rather than stubbornly stay the course.</text></item><item><author>rightbyte</author><text>I always knew agile was a CIA plant gone ammock. (&amp;#x2F;s?)&lt;p&gt;The article feels like one of these chain mail jokes rather than a serious article, but anyway.&lt;p&gt;&amp;quot;Insist on doing everything through “channels.” Never permit short-cuts to be taken in order to expedite decisions.&amp;quot;&lt;p&gt;That bullet point list more or less describes Scrum.</text></item></parent_chain></comment><story><title>Simple Sabotage Field Manual – How to Destroy Your Organizations</title><url>https://butwhatfor.beehiiv.com/p/simple-sabotage-field-manual-destroy-organizations</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>ljm</author><text>Yeah that’s a totally fair point, and one I took as given because it’s hard to discuss something like this if you need a disclaimer on facilitating organisational change every time the topic comes up. After explaining for years that no, doing agile doesn’t mean daily status reports and endless meetings, you start to consider that maybe these arguments are offered in poor faith and you want to focus on the good faith nuance.&lt;p&gt;Ironically, you can sabotage any attempt to apply some useful agile (or scrum) principles in earnest simply by trotting out a few strawman arguments against it.</text><parent_chain><item><author>bartread</author><text>I agree with your second point but...&lt;p&gt;&amp;gt; I don’t think it does unless you take a dim view of it and perpetuate the simplistic scrum-agile bad meme.&lt;p&gt;Look, the thing is, if you&amp;#x27;ve worked in a load of different organisations, and lots of different teams, with other smart people and have never really seen Scrum done well, and have in some cases actively seen it inhibit the delivery of quality software, I think it&amp;#x27;s legitimate to start questioning the process. People - smart people - struggle to make it work effectively. Plus, 50% of software developers (UX, product management, QA, SRE, stakeholders, etc.) are worse than average: a process that top quartile people struggle to make work well, sometimes even under the most favourable of circumstances, is less valuable when broadly applied across the delivery professions as a whole, and over different industry sectors.&lt;p&gt;On the flip side, with any process being introduced, I think it&amp;#x27;s fair to spend some time, maybe 6 months (but it will vary, depending on the process), implementing that process fairly strictly. It does need time to bed in, and there will be areas of friction simply due to creating new habits or resistance to change rather than due to problems with the process during that time. You need time for those issues to shake out so that you can see how much value the process itself really delivers and where it can be improved. At the 6 month point you can review the process, implement improvements, and move forward. You can keep doing the same review&amp;#x2F;evolve process on whatever cycle you choose, and that way your processes are more in step with changes in the wider organisation (hopefully growth).&lt;p&gt;Your processes need to fit your organisation, your business model, your culture. So, by all means, you can start with a process like Scrum, but to be really successful with it you need to treat it as just that: a starting point. You need to evolve it to fit your business. We all like to mock cargo-culting and yet, somehow, Scrum and agile often seem to blag a free pass. I don&amp;#x27;t understand why, because they shouldn&amp;#x27;t get that free pass. Your processes need to work for your business, and they are always a means for delivering value and never an end in themselves.</text></item><item><author>ljm</author><text>I don’t think it does unless you take a dim view of it and perpetuate the simplistic scrum-agile bad meme.&lt;p&gt;An easy way to throw an effective team into disarray in tech is to waylay it with back channel requests and unplanned work. If you’re too busy fighting fires and working personal errands for disruptive managers and executives then you’re not delivering what your team is supposed to deliver.&lt;p&gt;The ‘proper channel’ isn’t a bureaucracy as described in the SSFM, it’s simply an ordered list of priorities with a gatekeeper.&lt;p&gt;Edit: as far as dogmatically adhering to this process goes, then any effective agile&amp;#x2F;scrum process will have a baked in allowance to handle the unexpected or adapt to change, rather than stubbornly stay the course.</text></item><item><author>rightbyte</author><text>I always knew agile was a CIA plant gone ammock. (&amp;#x2F;s?)&lt;p&gt;The article feels like one of these chain mail jokes rather than a serious article, but anyway.&lt;p&gt;&amp;quot;Insist on doing everything through “channels.” Never permit short-cuts to be taken in order to expedite decisions.&amp;quot;&lt;p&gt;That bullet point list more or less describes Scrum.</text></item></parent_chain></comment><story><title>Simple Sabotage Field Manual – How to Destroy Your Organizations</title><url>https://butwhatfor.beehiiv.com/p/simple-sabotage-field-manual-destroy-organizations</url></story>