One of the core problems is doing the feature planning as a big bang event - the backlog refinement event. Developers don't want to sit for hours going through feature after feature. The artificial imposed 2-week cadence is the problem.

If a developer finishes a story, they want another to work on. That's the time to pick one and then sit down with an analyst to go through that story and what it should do. That's when the developer is interested - in that story.

Note that I said "analyst" and not PO, because the PO role makes no sense. A PO - if they do their job right - should be a product manager, and should not be spending their time worrying about individual features: they should be thinking strategically about the product.

Scrum's cadence and events are boring awfulness. Standup? - what's the point? Encounter an impediment? Don't wait for the standup! Retro? - what's the point? Have an idea for improvement? Don't wait for the retro! The cadence is unnecessary and breaks the flow. It also breaks the BDD process.