A. They should work apart as much as possible in order to keep the concerns of business and technology separated.
B. They collaborate often so the Product Owner can make informed decisions in balancing effort and value of Product Backlog items.
C. The Product Owner should be with the Developers full-time to grow a deep understanding of the technology being used.
D. They collaborate often so the Developers build Increments keeping end-user and stakeholder concerns in mind.
E. They should share no more than the Sprint Planning and the Sprint Review meeting.
Explanation:
The Product Owner and Developers must collaborate closely to maximize value, as per the Scrum Guide.
B: Collaboration enables the Product Owner to balance effort (Developer input) and value (their priority), aligning with: "The Product Owner may influence the Developers by helping them understand and select trade-offs."
D: Frequent collaboration ensures the Developers understand stakeholder needs, supporting the creation of a valuable Increment: "The Developers are required to conform to the Definition of Done and to deliver an Increment that meets the Sprint Goal."
A: Separation contradicts Scrum’s emphasis on teamwork; the Scrum Team is cohesive, not siloed.
C: Full-time co-location isn’t required; the Product Owner focuses on value, not technical mastery.
E: Limiting interaction to two events undermines refinement and ongoing alignment.
Exact Extract from Scrum Guide: "The Scrum Team is responsible for all product-related activities... The Product Owner is accountable for effective Product Backlog management, which includes... ensuring that the Product Backlog is transparent, visible, and understood." (Section: "The Product
Owner") This implies regular Developer interaction for clarity.
Thus, B and D best describe their relationship.
Reference: Scrum Guide (2020), Sections: "The Product Owner," "Sprint Planning."