Well my current experience is that the answers are a sounding yes. Developers love to develop software using Scrum. Still a whisper can be heard that "yes" is not without consequences. Say your team is developing with Scrum. We have the following roles:
Because a new release is available every two weeks the stakeholders should also provide feedback every two weeks. Therefore they sometimes hate Scrum.
But later you realize that Scrum says the team is responsible. You must acknowledge that the product success is also your success. Each design decision is now also driven by ROI considerations. If you master these responsibilities you suddenly discover the world of engineering, creating great products with an optimal balance of external quality and costs without ever jeopardizing the quality of the core. But you can never again deny that you as developer are in charge.
Cool isn't it. But wait as a product owner I am responsible of the budget and product success and each time a member of the team asks me something I must have an answer ready.
Scrum is cool and we enjoy it. But Scrum makes everything transparent and fast. Every two weeks a new version is delivered. This version must be evaluated, accepted or a list of improvements must be provided in the next days. This rhythm is fast, really fast. Once you are up to this speed you will enjoy the flow.