I can only speak for myself, but I think the answer is "No.. sortof.. it depends.. maybe?" Writing an epic and a dozen US is definitely a lot quicker for one p

I can only speak for myself, but I think the answer is "No.. sortof.. it depends.. maybe?" Writing an epic and a dozen US is definitely a lot quicker for one person to do, than it is for a team to implement it. So from that side, PM does a lot less work. Plus there's dev work like platform architecture, upgrading, platform, change management, automated test-cases etc, that I don't even have to think about. There's a massive multiplier there. Maybe 1 day a week writing requirements can keep a team busy and another day for answering questions, sprint ceremonies etc (story review, signing off demos) - but I'd say less than half my time is dealing with the actual productive work. Dev team just functions on 2-week sprints and the commitments they've given - so hard for it to go too-sideways, and they're safely insulated. Majority of my time goes on the "meta-work" - trying to manage what goes into those sprints. Customer requirements/placation - they don't (and shouldn't) have to give a toss about our internal sprints - so somebody has to ensure they'll be happy/not-going-to-sue in 18 months. Also the budget side is a complete Pain-in-the-arse. Your Agile trainer imagines there's some single pot of money to splash about however you choose to spend most efficiently. Reality is you're fighting for little top-down piles on internal accounts and then trying to fit the work you've done to them.