Product Owner and Developers disagree.
I am Scrum master for a team, my team is having a problem: in Sprint planning there is a user story developer who sees it as not worth too much for the product with a proposal to the PO, please rearrange its priority. and request in user story reduces user experience but PO insists on team to implement that user story.
I also advised Developers to respect PO's decision and do it then we'll check back at Sprint Review, Developers still insist that user story doesn't bring better value but make our product recognized. about the bad feedback, I also advised the PO to reconsider the request but it still didn't work.
If anyone has encountered this situation, please give me some useful advice. My English is not good, I hope everyone will understand the problem I mentioned above. Thank you.
From the Scrum Guide:
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
It's good that the Developers are engaging with the work they are being asked to do and trying to help maximize the product's value. But, at the end of the day, the Product Owner is accountable for maximizing value. Unless there is a technical reason why the work described by the Product Backlog can't be done or shouldn't be done in the order laid out, the Product Owner's decision about the ordering of the Product Backlog is final and everyone - including the Developers - need to respect their decisions.
Product Backlog refinement is the art and science of de-risking Sprint Planning, so issues like this do not arise.
It sounds as though this item is not ready. Why not perform a spike investigation, as part of refinement, to better understand the likely value of the item? Is there a quick experiment of some kind which might be conducted?
Amazing information! We are real estate development company. But in despite of this I read your websites content on daily basis. I really enjoyed this thread and discussions by the people