PMP Q#7 – What is User Story?
Q7. Which of the following best defines the User Story?
A. User Stories defines the requirement in the developers’ language.
B. User Story defines a small requirement that can be developed in iteration.
C. User Story defines the key product requirements.
D. User Story defines the product goal.
Let’s explore all options and how right or wrong they are about the user story:
Option A – “User Stories defines the requirement in developers’ language.” – A big NO because user stories are short descriptions of features from the user or customer’s point of view. A user story communicates what a user wants to do, which is the whole idea of a user story. It is not about developers’ language.
Option B – “User Story defines a small requirement that can be developed in iteration.” – Yes, it is true. A good user story is small in size you can complete in a single iteration. So, this is the right option. But let’s explore the remaining options as the question asks which option Best defines the User Story.
Option C – “User Story defines the key product requirements.” – User Story is one of the tools for exploring requirements; you can say that user stories are the best and most popular forms of product backlog items. A Product Backlog item can be a key or non-key product requirement placed in the product backlog based on their priority. Product Backlog is a prioritised list of all the requirements, so if any requirement is non-key, it will be deprioritised in the product backlog. Therefore, this option does not look like the best option.
Option D – “ User Story defines the product goal.” – User story is not about defining the product goal. Instead, it represents a small increment of requirement, which is small enough so the team can complete it as per the Definition of Done in a given iteration.
So after looking at all options, option B is the best option to mark right. Because; this option is primarily talking about –
It defines a small requirement that a team can develop in an iteration.
