User Story Lifecycle

5 minutes 5 Questions

The lifecycle of a User Story in Scrum begins with its creation and ends with its closure which often involves several iterations. Initially, the Product Owner creates a coarse-grained User Story. As the team begins to work on it, they break it down into finer detail. Then, the Development Team estimates the story and it is placed into the Product Backlog. As part of a Sprint, the team then works to complete the story - writing the code, testing it, and then finally reviewing it within the team. Once the Story meets its definition of done, it is closed. The lifecycle of User Story is crucial for understanding the flow and evolution of work within a Scrum team.

Guide: Understanding the User Story Lifecycle in Scrum (PSM I)

Understanding the User Story Lifecycle is a vital part of Scrum, an agile framework commonly used in project management.

Why it is important:
User Stories guide the team in creating product increments. They help streamline work and facilitate communication by breaking product requirements down into manageable, understandable pieces. Scrum teams live by User Stories as they guide the 'what' of the work that needs to be done.

What it is:
A User Story Lifecycle comprises of four stages:
  • Ready: User story meets 'definition of ready', clearly stating what the user wants.
  • In Progress: Development team is currently working on the User story.
  • Testing: User story is tested against acceptance criteria.
  • Done: It meets 'definition of done', has been accepted by the Product Owner.
Each stage is important and requires careful monitoring and control.

How it works:
The Product Owner prioritizes User Stories in the Product Backlog. The Scrum team then selects from the top, based on how much they can commit to in one Sprint. If a User Story is too large, it is broken down further. It moves between stages throughout the Sprint and is ideally in the 'Done' stage at the end.

Exam Tips: Answering Questions on User Story Lifecycle:
  • Understand and clearly define each stage of the lifecycle.
  • Know who is responsible at each stage (Product Owner, Scrum Master, Development Team).
  • Understand how User Stories move from one stage to another.
  • Know the role of a User Story in Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
Remember, understanding these concepts thoroughly is key to passing Professional Scrum Master I (PSM I) examination.
Test mode:
Start practice test

PSM I - User Story Lifecycle Example Questions

Test your knowledge of User Story Lifecycle

Question 1

A user story has not cleared the definition of done stage in the current sprint, what should be the successive step?

Correct Answer: The user story should be revisited by the team, refined if necessary, and reprioritized in the product backlog.

In Scrum, if a user story does not meet the Definition of Done (DoD) by the end of the sprint, it should be reevaluated during the sprint review. The team, along with the product owner, can decide to refine and reprioritize the story for future sprints based on its importance and urgency. Increasing velocity arbitrarily, assigning work outside the collaborative team structure, or attempting to bypass the established sprint process violates the fundamental principles of Scrum, which emphasize transparency, inspection, and adaptation.

Question 2

You have just concluded a sprint in which a user story was completed, but the customer wants to make a slight adjustment. What would be Scrum's best approach to handle this?

Correct Answer: Re-evaluate the completed user story during the sprint review and, if necessary, create a new user story for the adjustment to be prioritized in the product backlog.

In Scrum, once a user story is completed and the sprint has ended, any new changes or adjustments requested by the customer should be treated as new work. This new work needs to be thoroughly evaluated and prioritized in the product backlog, not immediately acted upon. This ensures that the process remains systematic and that the priorities defined in the product backlog guide the work undertaken by the team. Immediate actions, adjustments without formal prioritization, or starting a new sprint specifically for such changes go against Scrum principles of backlog management and iterative development.

Question 3

The product owner proposes a new user story in the middle of the sprint. As a Scrum Master, how would you handle this situation?

Correct Answer: Discuss it with the Product Owner and devise a plan to consider it in the next sprint planning

The Scrum framework does not encourage changing the Scrum Sprint contents in the middle of it. Any new user story or feature should be discussed in the upcoming Sprint planning meeting. This is to maintain the team's focus and stability throughout the ongoing sprint. Hence, 'Discuss it with the Product Owner and devise a plan to consider it in the next sprint planning' is the best answer.****On the other hand, 'Reject the story immediately' is incorrect as it eliminates the possibility of discussing its potential benefits and impacts. 'Add the story to the ongoing sprint' is incorrect as it undermines the team's commitment and can potentially disrupt the sprint's progress. Lastly, 'Suggest the Product Owner to wait until the sell-off sprint' is also incorrect because it's not a standard practice in Scrum and sell-off sprints are not part of the Scrum framework.

More User Story Lifecycle questions
15 questions (total)
Start 15 question test

Other User Stories in Scrum concepts

3C's: Card, Conversation, ConfirmationAcceptance CriteriaBurn Down ChartsEpics and ThemesINVEST PrincipleNon-Functional Requirements in User StoriesSplitting User StoriesStory PointsUser Story MapsUser Story PrioritizationUser Story Role-Feature-Reason Template
All User Stories in Scrum questions · PSM I practice test