Scrum Master Responsibilities

Responsibilities of the Scrum Master 


The Scrum Master has some important responsibilities:

A Guard: 

Guard the Scrum Team from external requests and disruptions.
Even if the request is from higher management. Any request will go through accepted, and prioritize by the Product Owner Only.
Scrum Development Team should not be disturbed by management, Scrum Master will take care for such events. 

A Change Agent:

 Act as a change agent and adapt processes to maximize productivity of the team.
Scrum Master will continuously helps scrum team to adapt good and productive process.

A Coach:

Coach the Scrum Team. Scrum Master will take care to happen all scrum events within the time box.
Introduce process improvement games and activity etc...

Impediments Remover:

 Remove impediments for the Scrum Team. Any external impediments will be taken care by Scrum Master to improve the productivity of Scrum Team

Communication Ensurer:

Ensure efficient communication between the Scrum Team and the Scrum Product Owner

Scrum Event Facilitator:

Facilitate the various Scrum Events.
Scrum Master will watch-out for all scrum Events to happen within time-box






Comments

Post a Comment

Popular posts from this blog

A brief overview of Scrum

Scum in Brief Scrum Meetings Sprint Planning (8 hours for 1 month sprint) Daily Scrum (15 minutes)   -> parallel -> Backlog Refinement Sprint Review (4 hour max for 1 month sprint) - After Sprint execution, the team holds a Sprint Review Meeting to demonstrate a working product increment to the Product Owner and everyone else who is interested. Sprint retrospective (3 hours from 1 month sprint) -> Each Sprint ends with a retrospective. At this meeting, the team reflects on its own process. They inspect their behavior and take action to adapt it for future Sprints. Scrum Artifacts Product Backlog Sprint Backlog Sprint Task Sprint Burn-down Chart Sprint Burn-down Chart : Indicates total remaining team task hours within one Sprint Indicates total remaining team task hours within one Sprint Re-estimated daily, thus may go up before going down Intended to facilitate team self-organization. Product / Release Burn-down Chart -> Tracks the r...
Read more

Scrum Stund-up VS Kanban Stand-up

Stand up Meetings in different Agile Engineering Time Box:15 Minutes. Stund-up meetings should finish in 15 Minutes time box. It helps to resolve many individual and team problems. Helps to plan/re-plan. My resolve issues if any one has face the same issues in team. Its very helpful in team building and collaborative. Why Stand-up meeting ? Collaboration   Helps to get More Valuable Information Reduces problems More understanding on road blocks The Scrum Style  Stand-up  Focus On       Scrum Style stand-up has  3 main Questions. What I have done yesterday What I will do today What are the impediments. The Kanban Style Stand-up Focus on       Scrum Style stand-up has  3 main Questions. The RED cards ( obstacles which are stopping the Progress ) The Progress Cards ( In-progress or Done ) Source: Internet
Read more