BA-201 · Question #306
At Universal Containers, a business analyst (BA)r solution architect, lead developer, quality assurance lead, and other team members need access to user stories as part of the Agile lifecycle of…
The correct answer is A. Define a common repository to hold all user stories and track changes over time. In an Agile environment, user stories evolve continuously through refinement, feedback, and sprint cycles. Team members need real-time access to the most current versions to do their work effectively. Allowing each team member to merge stories at the end of UAT (B) creates…
Question
At Universal Containers, a business analyst (BA)r solution architect, lead developer, quality assurance lead, and other team members need access to user stories as part of the Agile lifecycle of enhancements to a Marketing Cloud integration project. What should the BA do to give all team members access and visibility to the most recent user stories as the project is in motion?
Options
- ADefine a common repository to hold all user stories and track changes over time.
- BAllow each team member to merge all user stories at the end of user acceptance testing.
- CSend emails to stakeholders with all of the changes to the user stories.
How the community answered
(67 responses)- A78% (52)
- B15% (10)
- C7% (5)
Explanation
In an Agile environment, user stories evolve continuously through refinement, feedback, and sprint cycles. Team members need real-time access to the most current versions to do their work effectively. Allowing each team member to merge stories at the end of UAT (B) creates version conflicts, delays, and loss of context. Sending emails with changes (C) is error-prone, untracked, and not scalable. Defining a common repository (A)-such as a project management tool like Jira, Azure DevOps, or Salesforce's own tools-gives all team members (BA, architects, developers, QA) a single source of truth. It enables version history, traceability, real-time updates, and role-based access, which are essential for a collaborative Agile team across an entire project lifecycle.
Topics
Community Discussion
No community discussion yet for this question.