> Not every problem is well suited to being broken up into single day chunks of work. Not every developer can maintain a healthy relationship to their work with that level of micromanagement. There is a huge amount of anecdotal evidence about this if you read any thread about developer burnout, or modern day scrum and agile. You mention the Agile Manifesto, but seem to forget that one of the primary points is "individuals and interactions over processes and tools".
I don't plan to continue the conversation at this point, because it's not productive.
And if you are doing "Agile" but it's not working... then you're Doing It Wrong(tm). Right?
There are lots of reasons agile won't work for you, but they're also great indications you should probably leave a given org.
"Agile" software development doesn't work when there's 5 non-technical stakeholders and 1 software developer.
Delivering software to your customer is an interaction. You need more of those, not less of those.
"Stories are "just right" when the whole team can finish four to ten per week, or about six on average." [0]
"For stories that are too big, work with your customers to split them into smaller stories." [0]
If you think it's just "Everything gets shipped every day or two and no other changes get made to how the team functions." then I have not been clear. It's a massive mindset shift, and it comes with a number of other important changes, all of which are best read from the experts themselves, rather than interpreted through me in an HN comment.
Suffice it to say, it's all been accounted for. Agile works.
[0] https://www.amazon.com/Art-Agile-Development-Pragmatic-Softw...