A CHECK LIST FOR THE SCRUM MASTER

-

 

                                            A CHECK LIST FOR THE SCRUM MASTER

A check list for the SCRUM MASTER to do the role effectively:

Check List Related to PLANNING

Task

Details

 

USER STROIES has subtask

Ensure that the User Stories has the Sub-tasks

 

User Stories and Tasks are Estimated

Make sure that User Stories and Tasks are Estimated by the team

 

All the Tasks are Assigned

Ensuring that All the Tasks are Assigned to the Team members

 

Team Finishes the task before taking New Task

Ensure that the Team finishes the current task before the new Task to increase the ambition speed

 

Task Board is up-to Date

Validating and making sure that the Task Board is up-to Date

 

Action Items are Tracked from all the meetings

SM Ensure that Action Items are captured and Tracked from all the meetings

 

 

 

Check List Related to

Daily Activities of the Scrum Team

Impediments are visible to Everyone

Scrum Master should ensure that the Impediments are visible to Everyone.

 

 

Status is Managed for All the User Stories

Status of the User stories are Managed and the Impediments are reported to all the Team members

 

Stake Holders are informed about the Impediments

Ensure that the Scrum master should inform the Stakeholders about the Impediments.

 

 

 

Reports and Visual Dashboards

Burndown Char is updated

SM ensure that the Burndown chart is updated on the daily basis

 

Actions are planned based on the burn down charts reports

Actions are planned based on the Burndown chart and the status is reported

 

Team Members Participating the Scrum Events

Ensure that All the Team members are participating the Scrum Events

 

Team Members demonstrating the scrum values

Ensure that the Team members are demonstrating the scrum values in their daily activities

Note: Scrum Master can use this check list to Ensure that the Reports and Dashboards are available for all the Stake Holders.

Comments

Post a Comment

Popular posts from this blog

Product Owner - Role And Responsibilities and Po V/s SM

-
Image
What is a Product Owner?  Reference : https://www.c-sharpcorner.com/article/product-owner-role-and-responsibilities/ To be precise, a product owner is a scrum development role for a person who represents the business or user community, and is responsible for working with the user group to determine what features will be included in the product release.   Image Source – ProductCoalition.com   What are a Product Owner’s Responsibilities? The Product Owner (PO) represents the business to the development team and the Scrum team to the business folks. The PO  is one person, not a committee or group of people. The PO has product vision. The PO  owns the budget and is responsible for the success of the product. He/she is part of the Scrum team – closely works with the development team and Scrum Master throughout the sprint. The PO owns the product backlog and directs product development through product backlog prioritization. Strives to maximize the...
Read more

how many story points we can allocate for a sprint and how

-
 To determine how many story points you can allocate for a sprint, you need to consider the available hours, the number of developers, and the relationship between hours and story points. Here’s how you can calculate it: Step 1: Determine Total Available Hours for the Sprint Given: Total hours for the sprint : 180 hours Number of developers : 3 Step 2: Estimate Story Points Per Developer Assume that one story point represents a certain number of hours of work. For example: 1 story point = 8 hours Each developer has 60 hours available: Hours per developer = 180  hours 3  developers = 60  hours/developer \text{Hours per developer} = \frac{180 \text{ hours}}{3 \text{ developers}} = 60 \text{ hours/developer} Hours per developer = 3  developers 180  hours ​ = 60  hours/developer Given this, the number of story points each developer can handle: Story points per developer = 60  hours 8  hours/story point = 7....
Read more

To determine how many sprints for a User Stories

-
 To determine how many sprints it will take to complete 59 user stories and how many story points to assign to each user story, we need to break this down step-by-step: Step 1: Estimate the Story Points Assess the Complexity : First, you need to estimate the complexity of each user story. Story points are often assigned based on factors like effort, risk, and complexity. Use techniques like planning poker or t-shirt sizing to estimate. Typical Scale : Story points are often estimated using Fibonacci-like sequences (e.g., 1, 2, 3, 5, 8, 13, 21) or other scales that represent effort. Step 2: Determine Team Velocity Velocity : Velocity is the number of story points a team can complete in one sprint. For example, if the team completes 30 story points in a 2-week sprint, their velocity is 30. Historical Data : If the team has historical data, use that to determine their average velocity. If not, start with a rough estimate based on team capacity. Step 3: Calculate Number of Sprints Once...
Read more