BUSINESS-ANALYST practice question 13 of 35

A group of business analysts (BA) at Universal Containers have been working with different teams of stakeholders on eliciting requirements for a new…

Full set: 310 questions
A group of business analysts (BA) at Universal Containers have been working with different teams of stakeholders on eliciting requirements for a new Salesforce app. The BAs have gathered and documented all of the information in a central location. Upon review of the requirements, the BAs discovered that changes made to the documentation were overwritten by each other, and they will lose time recapturing them. What should the BAs do differently to prevent this error from happening?
Answer options
A: Each BA should use their own separate documentation.
B: Each BA should enter their business needs in a shared spreadsheet,
C: Each BA should use a shared system that has version control. Correct answer
Correct Answer:
C. Each BA should use a shared system that has version control.
Explanation

The problem described is a classic consequence of multiple users editing a single document without a system to manage concurrent changes. A shared system with version control is the standard solution. Such a system tracks all changes, identifies who made them, and provides mechanisms to merge contributions and resolve conflicts. This prevents accidental overwrites and ensures a single, reliable source of truth for requirements documentation while enabling effective team collaboration.

Why Incorrect

A. Using separate documentation creates information silos, making it impossible to maintain a unified view of requirements and leading to inconsistencies and redundant work.
B. A shared spreadsheet offers some real-time collaboration but typically lacks the robust version history, conflict resolution, and audit capabilities of a dedicated version control system.

References

1. Salesforce Architects, Well-Architected Framework, "Operating on Salesforce" pillar, "Implement Change and Release Management" section. This source advocates for using a version control system (VCS) as the source of truth for metadata, a principle that applies equally to the documentation that defines those changes.

2. Salesforce Trailhead, Business Analyst Best Practices, "Document Business Requirements" module, "Choose a Documentation Method" unit. This unit discusses the need for requirements to be "accessible to all stakeholders," implying a shared system. While not explicitly naming version control, it's the underlying technology that enables safe, collaborative access.

Scroll to Top