Skip to main content
5 events
when toggle format what by license comment
Dec 28, 2019 at 16:20 comment added jessehouwing The availability, security and performance could be covered under the Quality Standards ad referenced from the Definition of Done, in which case, the Product Owner wouldn't need to be concerned too much about them. NOT having defined the technical aspects by the Product Owner, does keep the responsibility for these aspects with the Development Team.
Dec 28, 2019 at 16:15 comment added jessehouwing @ThomasOwens, you're right. And I'd want the PO/Stakeholders to describe what they need from the system. Then the Development team to transform that into technical requirements. The customer needs availability and security. But how to meet these are ideally selected by the Development Team. Too many Product Backlogs contain all kinds of technical details which the team can fill in for themselves. It does require a mature development team.
Dec 28, 2019 at 16:13 history edited jessehouwing CC BY-SA 4.0
added 182 characters in body
Dec 28, 2019 at 16:04 comment added Thomas Owens I don't think it's safe to say that the Product Owner is responsible for "functional acceptance criteria". There are also non-functional characteristics that come from external stakeholders that may arrive through the Product Owner - disaster recovery, security, performance, availability and uptime are a few examples. How these are met, though, are up to the Development Team.
Dec 28, 2019 at 15:52 history answered jessehouwing CC BY-SA 4.0