How the Scrum Master will hep in picking up the good user stories for the team members ?

-

 

1.     As a Scrum Master, one of the responsibilities is to help the team pulling up the backlog for a sprint which is already prioritized and pulling items which are placed on the top (sorted as per the priority).

2.     Once, the team is able to identify items that can add value from the pile of requirements, the Scrum Master can help them (Product Owner + Development Team) to convert them into good user stories (if it is not already).

A good user story is one which includes 

  •        a description and
  •          has acceptance criteria defined.

It should be a piece which can be delivered in a sprint and entails minimum dependencies.

The team should be able to develop and test within the boundaries of the sprint along with providing the estimates.

In short, good user stories follow the INVEST principle.
  • Independent - Reduced dependencies
  • Negotiable - Describes the functionality, can be negotiated between the Team and PO
  • Valuable - Provides value to the customer
  • Estimable - Too big or too vague = not estimable
  • Small - Can be done in a Sprint by the team
  • Testable - Good acceptance criteria

The scrum master can help the team in creating good user stories during the backlog refinement or sprint planning so that the team can pick them up for the commitment.

Comments

Post a Comment

Popular posts from this blog

Real time example to create Epic Features, Stories, Acceptance criteria , Tasks , DOD , DOR, Story points

-
Creating epic features, stories, acceptance criteria, tasks, Definition of Done (DOD), Definition of Ready (DOR), and assigning story points is a common practice in Agile project management, particularly in Scrum. Here's a real-time example for a hypothetical project: Project: Developing a Mobile App for Task Management Epic: User Authentication                                                                                                          Story 1: User Registration Acceptance Criteria: User should be able to enter their email and password. Password should be at least 8 characters long. User's email should be in a valid format. Upon successful registration, a confir...
Read more

Agile v/s scrum v/s Kanban v/s Devops

-
  Agile, Scrum, Kanban, and DevOps are all methodologies and practices used in the software development and project management fields, but they serve different purposes and have distinct characteristics. Here's a brief overview of each: Agile: Agile is a set of principles and values that promote flexibility and collaboration in software development. It emphasizes customer collaboration, responding to change, and delivering working software in short iterations. Agile methodologies aim to deliver value to customers early and frequently through continuous improvement and feedback. Scrum: Scrum is an Agile framework for managing and controlling complex software development projects. It organizes work into fixed-length iterations called sprints, usually 2-4 weeks long. Scrum teams have defined roles, including a Product Owner, Scrum Master, and Development Team. Scrum practices include daily stand-up meetings, sprint planning, sprint review, and sprint retrospective. Kanban: Kanban is a...
Read more

What Does a SM-SCRUM MASTER do “All the Day”

-
What Does a SM-SCRUM MASTER do “All the Day” ·         Facilitate the Daily Scrum (Timeboxed) o    Facilitate the Daily scrum meetings for the team and maintaining the time box ·         Arrange the Follow-up meetings o    Arrange the follow-up meetings for the detailed discussion after the daily scrum meeting, if anything is raised in the daily scrum meeting ·         Meeting with the PO – PRODUCT OWNER o    To arrange the meeting with the PO to support the Backlog creation and the Road Map preparation ·         Facilitating the SCRUM EVENTS   o    such as – BACKLOG REFINEMENT, SPRINT PLANNING, SPRINT REVIEW AND SPRINT RETROSPECTIVE meetings. ·         Meetings with the Team’s Manager                   ...
Read more