In a small city IT Scrum team building a recreation registration app, the same person sometimes acts as BA and product owner. What should the team still ensure?
Select an answer to reveal the explanation.
Short Explanation
Small towns double-hat all the time—one person can be BA and PO—but everyone still needs to know who decides backlog priority versus who facilitates analysis. Clear hats beat confused meetings.
Full Explanation
In a small city IT Scrum team building a recreation registration app, the same person may sometimes act as BA and product owner, but the team should still ensure clear role clarity for backlog decisions and analysis facilitation even if one person wears both hats. Role clarity prevents confusion about when the person is prioritizing as product owner versus facilitating analysis as BA. Civic small teams need explicit working agreements more, not less, when roles combine.
Dropping product ownership duties whenever BA work occurs fails conceptually because the product still needs continuous ownership; duties should be clarified, not abandoned. Requiring a separate PMI-PBA credential holder to approve every story fails because credential mandates are not the CAPM point here—clarity of decision rights is. Claiming Scrum forbids any BA involvement with the product owner fails because analysis support for the product owner is common and valuable.
Exam caveat: Combined roles are allowed in small teams if decision rights and facilitation boundaries stay explicit. Operational check: write a working agreement for the recreation team stating when the dual-role person decides backlog priority versus when they facilitate elicitation, review it with the Scrum team, and escalate conflicts if those hats collide on contested stories.