ExamGecko
Question list
Search
Search

List of questions

Search

Related questions











Question 27 - Certified Revenue Cloud Consultant Accredited Professional discussion

Report
Export

Which three are key steps when documenting user stories?

A.
Know which business process the requirement supports to categorize the user story
Answers
A.
Know which business process the requirement supports to categorize the user story
B.
Identity the actor or personas in this user story
Answers
B.
Identity the actor or personas in this user story
C.
Design the solution while the business process is being defined
Answers
C.
Design the solution while the business process is being defined
D.
Document user acceptance test scripts for the user story.
Answers
D.
Document user acceptance test scripts for the user story.
E.
Identify the acceptance criteria or result for satisfying the user story.
Answers
E.
Identify the acceptance criteria or result for satisfying the user story.
Suggested answer: A, B, E

Explanation:

User stories are short, simple descriptions of a feature or functionality from the perspective of the end user or customer. User stories are used to capture the requirements and value proposition of a product or service in an agile framework. User stories should follow some best practices to ensure clarity, consistency, and alignment with the business goals and user needs.12

Some of the key steps when documenting user stories are:

Know which business process the requirement supports to categorize the user story. This helps to prioritize and organize the user stories based on the business value and impact they deliver. It also helps to avoid duplication and inconsistency among user stories.3

Identify the actor or personas in this user story. This helps to define the user role, needs, goals, and motivations that drive the user story. It also helps to create empathy and understanding for the user and their context.4

Identify the acceptance criteria or result for satisfying the user story. This helps to specify the expected outcome, behavior, or functionality that the user story should deliver. It also helps to define the scope, quality, and testability of the user story.5

Designing the solution while the business process is being defined is not a key step when documenting user stories. This can lead to premature or biased decisions that may not address the real user problem or value proposition. User stories should focus on the what and why, not the how. The solution design should be done after the user stories are validated and prioritized, and in collaboration with the development team and other stakeholders.6

Documenting user acceptance test scripts for the user story is not a key step when documenting user stories. This can be done later, after the user stories are refined and detailed, and before the development and testing phases. User acceptance test scripts are used to verify that the user story meets the acceptance criteria and the user expectations. [7]

1: User Stories | Examples and Template | Atlassian

2: How to Write Perfect User Stories (With Templates): A Step-By-Step Guide | airfocus

3: 10 Tips for Writing Good User Stories - Roman Pichler

4: The Anatomy of a User Story | Scrum Alliance | Includes Template

5: Best Practices to Succeed with User Stories - DZone

6: UX documentation: Guide, best practices, template

asked 23/09/2024
Ricardo Tellez
25 questions
User
Your answer:
0 comments
Sorted by

Leave a comment first