I am the Product Owner ... I never have time to write the Conditions of Satisfaction ("Verify that ... "). It seems to work best to have the developer team write the "verifies" (as we call them) and then I review and approve them.
Are there other ways to do this bearing in mind that most Product Owners will not have a lot of time to dedicate?
Add comment viewed 85 times Latest activity over 1 year ago
robertdempsey
The optimal situation is for the product owner to define done in via the acceptance criteria, or the conditions of satisfaction, as that is what the team works towards. Requirements and their creation are 100% under the purview of the PO. The team can definitely have input and suggest additions, however the PO needs to be doing these. If the PO is unavailable then either a new PO should be found, or office hours should be put into place (dedicated time to work on things and answer questions).
John Merriwether
[ Editor ]
I would typically shy away from this situation. One problem is the team, presumptively the developers, are the ones implementing it. By not writing it yourself you really aren't gaining much. It's also difficult to review because the verifies did not come from your own thought process - which could lead to missed requirements unless you wrote them yourself.
Kathryn Van Stone
One problem I found with just verifying conditions is if there is an edge case that is missing in the conditions it will usually be missed in verification. When working directly on the conditions, such cases are more likely to come to light.