A new employee at Universal Containers just sent the business analyst (BA) a Slack message with an attachment named User_Stories_v37_final final _final.docx.
Which best practice should the BA train the employee on first?
A new employee at Universal Containers just sent the business analyst (BA) a Slack message with an attachment named User_Stories_v37_final final _final.docx.
Which best practice should the BA train the employee on first?
The best practice the business analyst should train the new employee on first is to use standard naming conventions. Proper naming conventions help in organizing and identifying documents easily. It avoids confusion and errors when multiple versions of a document exist. This practice would immediately address the issue presented by the attachment named 'User_Stories_v37_final final _final.docx' by introducing a clear and consistent method for naming files.
Its B you need to use a standard naming convention for documents C makes no sense version control wouldn't help the naming of the document A is just not relevant
The file name is v37_final final _final So, there's been 37 versions and three potential 'final' ones too! Version control helps impacted stakeholders to track any changes made to a particular file. With version control, every change made to a file or piece of code is stored in a repository along with the information about who made the change, when it was made and why. This would be much more applicable than using standard naming conventions because that's still going to result in numerous files for the user stories without knowing changes made etc.