[pjmlp]

Not if you have the misfortune to be a single developer project or having a lead role on a team.

Someone needs to convert those Jira/Trello/Wall/... items into nice Excel sheets because upper management won't look at anything else.

While you are at it including some nice Powerpoints for the weekly/monthly updates.

And on the remaining time do those development tasks, while coaching junior devs at the same time.

[mdorazio]

If you have a lead role on a team the large majority of your time should be leading the team by doing all those non-development tasks. If you're trying to also cram in mission critical development you're trying to do too much or your company's leadership sucks. If it's a single developer project, 1) Agile might not be the best approach, and 2) updates to management should take very little time since you just need to sum up what you personally have accomplished and are planning to accomplish vs. whatever deadlines exist.

[pjmlp]

That's the nice theory and then there are the actual real life projects, hence why we reached the point discussed on the linked article.

[mdorazio]

Yes, that is the nice theory and also the nice real world. And yes, I've been on and managed dozens of projects at 10+ companies over the last decade so I feel confident saying that. Sounds to me like your company's leadership just sucks. That's not a problem with the methodology.