Question 41
Choose 1
A new employee at Universal Containers just sent the business analyst (BA) a Slack
message with an named User3tories_v37_final_final_final.docx.
Which best practice should the 6A train the employee on first?
Correct answer:
C. Use a version control repository
Explanation:
The file name UserStories_v37_final_final_final.docx is a classic sign of manual version tracking, which leads to confusion, duplication, and loss of traceability.
The best practice the Business Analyst (BA) should train the employee on is to use a version control repository (such as Git, SharePoint, Confluence, or a dedicated requirements management tool). This ensures:
Single source of truth — everyone works from the same document.
Automatic version tracking — no need for manual filenames.
Collaboration and auditability — changes are logged, reviewed, and reversible.
Why not the other options?
A. Use standard naming conventions
While standard file naming conventions (like including version numbers or dates) can help keep files organized, they are still a manual and error-prone approach to version control.
Here’s why it’s not ideal in this situation:
✅ When it helps: Naming conventions are useful when storing static files (like signed contracts or exported reports).
❌ When it fails: For living documents such as user stories, which evolve frequently and are updated by multiple contributors.
B. Use acceptance criteria to define success
This concept is completely unrelated to the version control issue described in the question.
Acceptance criteria define how to verify that a user story or requirement has been successfully implemented — e.g., “Given, When, Then” conditions.
They are part of requirements definition and validation, not documentation management or version control.
Teaching the new employee about acceptance criteria would improve requirement quality, but it wouldn’t solve the problem of file version chaos (e.g., final_final_v37.docx).
✅ When it helps: During requirement gathering, refinement, or testing.
❌ When it fails: For managing or organizing project documentation files.
C. Use a version control repository — Why it’s the best answer
A version control system (like Git, Confluence, SharePoint, or Jira attachments) automatically tracks changes, stores historical versions, and allows collaborative editing.
It eliminates the need for manually naming files with version numbers.
Everyone accesses the same “single source of truth” for user stories and documentation.
You can easily see change history, restore previous versions, and avoid duplication or overwrites.
✅ When it helps: Always — for managing evolving project documentation, code, or user stories.
❌ When it fails: Only if the team doesn’t maintain proper permissions or branching practices (rare in documentation workflows).
Reference:
Salesforce Business Analyst Best Practices: “Maintain documentation in a central, version-controlled repository to ensure consistency and traceability.”
Agile / BA Standards (BABOK): “Version control ensures that requirements and documentation remain consistent, traceable, and auditable across changes.”
Summary:
👉 The BA should train the employee to use a version control system — this eliminates the need for messy file naming like “final_final_final” and promotes professional collaboration and traceability.
The file name UserStories_v37_final_final_final.docx is a classic sign of manual version tracking, which leads to confusion, duplication, and loss of traceability.
The best practice the Business Analyst (BA) should train the employee on is to use a version control repository (such as Git, SharePoint, Confluence, or a dedicated requirements management tool). This ensures:
Single source of truth — everyone works from the same document.
Automatic version tracking — no need for manual filenames.
Collaboration and auditability — changes are logged, reviewed, and reversible.
Why not the other options?
A. Use standard naming conventions
While standard file naming conventions (like including version numbers or dates) can help keep files organized, they are still a manual and error-prone approach to version control.
Here’s why it’s not ideal in this situation:
- It depends on user discipline — everyone must remember to name files correctly and upload them in the right order.
- It doesn’t prevent duplication — multiple team members can still create “final” versions at the same time.
- It lacks automatic version history — you can’t easily see who changed what or revert to an older version.
- It doesn’t support collaboration — real-time co-editing, change tracking, and merging updates are missing.
✅ When it helps: Naming conventions are useful when storing static files (like signed contracts or exported reports).
❌ When it fails: For living documents such as user stories, which evolve frequently and are updated by multiple contributors.
B. Use acceptance criteria to define success
This concept is completely unrelated to the version control issue described in the question.
Acceptance criteria define how to verify that a user story or requirement has been successfully implemented — e.g., “Given, When, Then” conditions.
They are part of requirements definition and validation, not documentation management or version control.
Teaching the new employee about acceptance criteria would improve requirement quality, but it wouldn’t solve the problem of file version chaos (e.g., final_final_v37.docx).
✅ When it helps: During requirement gathering, refinement, or testing.
❌ When it fails: For managing or organizing project documentation files.
C. Use a version control repository — Why it’s the best answer
A version control system (like Git, Confluence, SharePoint, or Jira attachments) automatically tracks changes, stores historical versions, and allows collaborative editing.
It eliminates the need for manually naming files with version numbers.
Everyone accesses the same “single source of truth” for user stories and documentation.
You can easily see change history, restore previous versions, and avoid duplication or overwrites.
✅ When it helps: Always — for managing evolving project documentation, code, or user stories.
❌ When it fails: Only if the team doesn’t maintain proper permissions or branching practices (rare in documentation workflows).
Reference:
Salesforce Business Analyst Best Practices: “Maintain documentation in a central, version-controlled repository to ensure consistency and traceability.”
Agile / BA Standards (BABOK): “Version control ensures that requirements and documentation remain consistent, traceable, and auditable across changes.”
Summary:
👉 The BA should train the employee to use a version control system — this eliminates the need for messy file naming like “final_final_final” and promotes professional collaboration and traceability.
