I have a question about the responsibilities of the Scrum Product Owner and the Scrum Engineer/Architect.
It is said that in Scrum the Product Requirements (PRD) specify the "what", but not the "how". In other words, PRD should not dictate (or be concerned with) the implementation details.
We are building an app that relies heavily on the interaction with vendors' APIs. It has been said that we don't want to couple our app tightly with vendors' APIs and therefore the Product Requirements should not reflect the vendors' APIs capabilities and limitations. More specifically, the PO is expected to write the Product Requirements in the absence of vendors' APIs documentation.
Is this the correct interpretation of the Scrum methodology? What are the advantages and disadvantages of this approach?