Methodologies exist only to shepherd delivery - don't make shepherding itself the primary focus of your day-to-day lest you lose sight of the real aim: to deliver projects on time with minimal bugs while minimizing the effects of inevitable bugs on revenue/customer satisfaction.
You forgot the devs are stakeholders too. Usually they want to be paid for the least amount of work. (Unless manipulated into thinking work is a goal. I know a bunch of these.)
Or at least be actually fulfilled by it.
