Salesforce Business Analyst Certification Practice Exam

What is a common goal of using user stories in Agile development?

1. To promote a fixed scope of work

2. To facilitate user engagement and alignment

3. To eliminate the need for documentation

4. To determine the project's timeline

The correct answer is: To facilitate user engagement and alignment

Using user stories in Agile development is primarily about facilitating user engagement and alignment. User stories are a way to capture requirements in a format that focuses on the end user's perspective, typically structured as "As a [type of user], I want [a goal] so that [a reason]." This structure helps keep the team aligned with user needs and encourages direct communication with users or stakeholders to ensure the product meets their requirements. By focusing on user needs, the team can prioritize features based on how they will provide value to users, fostering collaboration and maintaining a shared understanding of goals among all team members. This engagement helps to refine the product over time, ensuring that the development effort is directed towards delivering the most relevant and valuable features. In contrast, promoting a fixed scope of work can be counterproductive in Agile, as it contradicts the iterative and flexible nature of Agile methodologies. Eliminating the need for documentation may mistakenly suggest that no documentation is needed at all; however, Agile promotes just enough documentation to support understanding without hindering development. Lastly, determining a project's timeline is more about scheduling and planning, which can be fluid in Agile, focusing instead on delivering valuable increments regularly rather than adhering to a strict timeline.