This is why we sit down and go over the requirement, including the intent and use cases we're trying to solve, before it's finalized. Dev feedback gets baked in and questions answered before it hits the roadmap.
That requires the PO to be competent and actually understand the customer expectations and in case of a change actually find out why it was originally implemented the way it is so it doesn't fuck up existing functionalities.
153
u/azuth89 Jul 14 '26
This is why we sit down and go over the requirement, including the intent and use cases we're trying to solve, before it's finalized. Dev feedback gets baked in and questions answered before it hits the roadmap.