Agile Living

How Scrum Masters Can Run a Highly Charged Team

Google can give you hundreds of search pages on great scrum masters, but how have they achieved those goals? Planio gathered insights from experienced professionals of top-performing companies like American Express, Cisco, and Dell. In this article at Planio, Jory MacKay discusses what those scrum masters did to run highly charged teams.

Roles and Responsibilities of Scrum Masters

Scrum masters ensure teams attain the ultimate project goals despite several changes and challenges in the journey. Their leverage their skill sets to maximize available resources, schedule, and funding. Strategic Quadrant founder Andy Sio refers to scrum masters as doctors of Agile teams. However, their role is more of a mentor than a manager. Following are the roles and responsibilities of scrum leaders that want to run highly charged teams:

Product Backlog Creation and Refinement: Scrum masters help to divide a project goal into user stories that they include in the product backlog. They refine each user story and allot time and bandwidth for completion.

Sprint Planning: Developers utilize these user stories to make working models in each sprint that can last from one to four weeks. While the product owners decide stories for sprints, scrum leaders allow the team to express doubts, ideas, etc.

Hosting of Scrum Meetings or Regular Standups: Scrum masters ensure that the development teams encounter no challenges. During the standups, they enquire about the work completion status, current tasks, and challenges that need resolution.

Conducting Retrospectives: Retrospectives occur at the sprint end as a review activity where all team members gather to analyze actions. Some might not open up or be comfortable receiving feedback or sharing opinions in front of all. It is the job of these masters to enable a conducive environment for all teammates.

Measuring of Project Performance Metrics: Scrum leaders evaluate the performance of team activities and decisions with a sharp eye. Agile for Growth scrum master Kamlesh Ravlani recommends 12 metrics like team velocity, commutative flow, cycle time, ROI, NPS, etc. Also, include burn up or down the chart, impact delivered, customer satisfaction, employee experience, defects count, code coverage, automation.

To view the original article in full, visit the following link:

Show More
Back to top button

We use cookies on our website

We use cookies to give you the best user experience. Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.