The product owner at Cloud Kicks wants to know which user stories fail user acceptance testing (UAT) and the potential impact on other successful use stories. Currently, user stories are stored in a shared spreadsheet.
What should a business analyst recommend to ensure UAT result are document security.
12 comments · newest first
AV
Avery
11 months ago
Isn't it risky to rely on a spreadsheet for UAT results?
TH
Thaddeus
11 months ago
Totally agree, history feature is a must for accountability!
CA
Carissa
12 months ago
Wait, how does a shared spreadsheet even ensure security?
SH
Shala
12 months ago
I think enabling history is a smart move for tracking changes.
WI
William
12 months ago
Just a heads up, giving everyone edit access can lead to chaos!
BL
Blondell
1 year ago
I think enabling history could help track changes, but I wonder if it really addresses the security concerns we talked about in class.
MA
Markus
1 year ago
I feel like asking each tester to edit the shared spreadsheet might create confusion. We need a more structured approach, but I can't recall the best solution.
VA
Vallie
1 year ago
This question reminds me of a practice scenario where we had to manage access to documents. I think giving all stakeholders editing rights could lead to issues.
LE
Lettie
1 year ago
I remember we discussed the importance of document security, but I'm not sure if enabling history in the spreadsheet is enough to protect sensitive information.
KA
Kaitlyn
1 year ago
This seems like a straightforward question about organizational change. I'll review the options carefully and choose the one that best captures the key reasons why organizations change their processes.
RE
Rebbecca
1 year ago
I think I've got this. The key is to calculate the cost of capital and then subtract that from the net operating profit after taxes. Shouldn't be too hard.
CA
Candida
1 year ago
This question seems straightforward - I think the key is to focus on the effectiveness of the IT controls, which is what the question is asking about.