Salesforce Business Analyst Certification Practice Exam

Why is using an undefined user as the 'who' in a user story detrimental?

1. User stories aren't meant to be written for users outside of the company.

2. Intention of the user can't be clearly defined.

3. Acceptance criteria for an undefined user requires extra work.

4. It can confuse the project team.

The correct answer is: Intention of the user can't be clearly defined.

Using an undefined user as the 'who' in a user story is detrimental primarily because the intention of the user cannot be clearly defined. User stories are meant to convey specific needs, goals, and expectations from the perspective of a particular user or persona. When the user is not clearly defined, it becomes challenging to articulate what that user wants to achieve and the context in which they will use the product or feature being developed. Clarity in understanding the user's needs is essential for creating effective requirements and for guiding the development team in building a product that meets those needs. Without a defined user, there is a significant risk that the development efforts will not align with the actual requirements needed to satisfy stakeholders or end-users. This lack of clarity could lead to misunderstandings and ultimately result in a product that fails to meet the necessary criteria or expectations of its intended audience. In contrast, the other options do not capture the core issue as effectively. While user stories ideally focus on internal users to maintain relevance, the main concern revolves around the ambiguity that arises from not defining the user properly. Additionally, while acceptance criteria can become more complex with an undefined user, this aspect stems from the foundational problem of not having a clear understanding of who the user is in the first place