What type of "quick decisions" does a Scrum Product Owner have to make? Can you give me two examples?
Hi,
I'm writing an article and I need to verify something.
What type of "quick decisions" does a Scrum Product Owner have to make? Can you give me two examples?
Thanks in advance,
Ones that are taken at the last responsible moment perhaps, such as whether or not to cancel a Sprint.
Generally speaking though, the speed of decision making ought to be limited only by people's ability to learn. A common inspect and adapt opportunity for Product Owners is the decision to pivot or to persevere.
Ones where scope might impact the Sprint Goal.
Example: During the Sprint the Developers encounter something unexpected or an unforeseen complexity arises, and with just two days left in the Sprint they turn to the Product Owner to negotiate scope. A quick decision is needed by the Product Owner so the Developers can get back to focusing on and meeting the Sprint Goal. Any delay might put the Sprint Goal in jeopardy.
My 2 cents - During the Sprint planning, lots of quick decision Product Owner needs to make based on situations. Based on the morning market situation during the Sprint Planning, the prioritization of feature, in feature what to implement. May be which stakeholder to talk through includes in quick decision list of Product Owner.