A business analyst (BA) is in the process of documenting requirements. The BA wrote the following user story:
"As a sales team manager, I want the ability to access reports on Sales Cloud to evaluate if the team’s daily activities are meeting the set goals."
Which acceptance criteria is most appropriate for this user story?
The most appropriate acceptance criteria is 'Able to view the sales team's reports'. This directly addresses the requirement of accessing reports to evaluate the team's daily activities against set goals. Option A focuses on a specific action (clicking the run button), which is more about implementation than the actual requirement. Option C, while relevant, is broader and better suited as a high-level requirement rather than specific acceptance criteria.
I strongly believe this should be C
(c) is the requirements, but it's too broad to use it as acceptance criteria. (b) on the other hand, is very specific and can be used as an acceptance criteria.
This should be C.
it is C - verified it in another study site
Also think it should be "C". I also think access too all "reports" is to unspecific looking at the user story.
i should be C
B. Able to view the sales team's reports,
The correct answer is B because it focuses on the "what", while C focuses on the "why". On the other hand, A explains a specific implementation that's not appropriate.
"Able to view the sales team's reports" B then it's possible to monitor and verify if goals are reached...But if just monitored the performance/goals (summary: high level report or dashboard with totals) it does not mean access on Sales reports
it should be A Able to click the Run button on sales reports would be the most appropriate acceptance criteria for this user story. This criterion is specific and measurable, describing the action that the user needs to perform to achieve the desired outcome. It also aligns with the user's stated need for the ability to access reports on Sales Cloud to evaluate if the team's daily activities are meeting the set goals
"able to Click the Run Button" its part of the solution which should not be present on the User Story.
I think C. because it says It wants ability to ACCESS. not view.