<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>a_c</author><text>Agile was meant to be &amp;quot;agile in change&amp;quot;, not following tickets blindly.
It was meant to foster collaboration between people rather than putting every detail in tickets by whatever manager&amp;#x2F;PM. So people know why they are doing stuff, and can make change accordingly. 
Agile was meant for making things that people actually use. Not about how many features were developed in last sprint.&lt;p&gt;Even the original waterfall model empahsized on feedback, feedback of design, feedback of usage &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Waterfall_model#&amp;#x2F;media&amp;#x2F;File:1970_Royce_Managing_the_Development_of_Large_Software_Systems_Fig10.PNG&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Waterfall_model#&amp;#x2F;media&amp;#x2F;File:19...&lt;/a&gt;</text><parent_chain><item><author>matt_s</author><text>Agile is not supposed to make development faster. The core element of being agile (small &amp;quot;a&amp;quot;) is to avoid doing work that results in features that are hardly used, not needed, etc. In lean terminology this is called eliminating waste in a process.&lt;p&gt;Smaller iterations of deliverable work prevents a big up front design and putting in features including UI designs, software designs, coding, tests, QA testing, etc. and then it doesn&amp;#x27;t get used or has minimal ROI.&lt;p&gt;JIRA sucks. If you think your issues with delivery are tied to your work tracking system then you&amp;#x27;re looking at the wrong things.</text></item></parent_chain></comment><story><title>The Slow, Painful Death of Agile and Jira</title><url>https://ehandbook.com/the-slow-painful-death-of-agile-and-jira-c8de04e4269a</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>fernandotakai</author><text>&amp;gt;JIRA sucks.&lt;p&gt;i used to think the same until i had to use azure devops.&lt;p&gt;i legitimately miss JIRA nowadays.</text><parent_chain><item><author>matt_s</author><text>Agile is not supposed to make development faster. The core element of being agile (small &amp;quot;a&amp;quot;) is to avoid doing work that results in features that are hardly used, not needed, etc. In lean terminology this is called eliminating waste in a process.&lt;p&gt;Smaller iterations of deliverable work prevents a big up front design and putting in features including UI designs, software designs, coding, tests, QA testing, etc. and then it doesn&amp;#x27;t get used or has minimal ROI.&lt;p&gt;JIRA sucks. If you think your issues with delivery are tied to your work tracking system then you&amp;#x27;re looking at the wrong things.</text></item></parent_chain></comment><story><title>The Slow, Painful Death of Agile and Jira</title><url>https://ehandbook.com/the-slow-painful-death-of-agile-and-jira-c8de04e4269a</url></story>