<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>stingraycharles</author><text>Sprints and planning are useful for organizations that attach a lot of value to planning and deadlines. It creates a lot of additional work and pressure, as you say, but I can also imagine that for certain types of organizations that may be worth it (eg when doing client work on a fixed budget with strict deadlines).&lt;p&gt;Other than that, I fully agree that Kanban is a great middle ground, as it’s low overhead and focuses on prioritization and flexibility rather than planning and burndown charts and whatnot.</text><parent_chain><item><author>gbro3n</author><text>Kanban is the best middle ground IMO. I agree sprints are a distraction. The planning and ceremonies alone sap time. Sprints are really just a form of pressure. In my experience the stories estimating is not accurate enough to set up a predictable sprint, and the inevitable deviation from the plan just creates additional work to audit and adjust, along with a sense of failure around what has often been a productive 2 weeks.</text></item></parent_chain></comment><story><title>I don’t believe in sprints</title><url>https://www.robinrendle.com/notes/i-don’t-believe-in-sprints/</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>polotics</author><text>KANBAN is good at ensuring you do not have too many themes on your plate at the same time.&lt;p&gt;Producing effort estimates is one of the many approaches to start talking about a task, and not doing it may mean that somebody else&amp;#x27;s better idea on how to tackle it gets ignored.&lt;p&gt;Having sprints is a good way to coax people in fully finishing things, it is often needed as many developers tend to jump to the next shiny.&lt;p&gt;If any of these three things gets used by a bad manager to get fake importance, to put pressure, push people down instead of pulling them up... then get rid of that manager.</text><parent_chain><item><author>gbro3n</author><text>Kanban is the best middle ground IMO. I agree sprints are a distraction. The planning and ceremonies alone sap time. Sprints are really just a form of pressure. In my experience the stories estimating is not accurate enough to set up a predictable sprint, and the inevitable deviation from the plan just creates additional work to audit and adjust, along with a sense of failure around what has often been a productive 2 weeks.</text></item></parent_chain></comment><story><title>I don’t believe in sprints</title><url>https://www.robinrendle.com/notes/i-don’t-believe-in-sprints/</url></story>