Showing posts with label scrum masters. Show all posts
Showing posts with label scrum masters. Show all posts

Friday 14 March 2014

Explanation Of Scrum Burndown Charts – The Plotting, Requirement, And Purpose Of Burndown Charts

What is a burn down chart?


A burn down chart is an important tool in scrum. It provides a visual representation about the progress achieved in a sprint while it is underway. They are very common and extensively used by scrum masters while scrum is being implemented in a project. The quantity, or the amount of work remaining, in the form of pending tasks, is typically exhibited in a burn down chart. The chart is simple and easy to understand, even by people who are not familiar with scrum methodology. Burn down charts are very useful for estimation purposes, and are essential for determining the sprint velocity – the rate at which work in the form of user stories is being completed by the development team – and planning the sprint release.  

Plotting the burn down chart
A burn down chart can be plotted by including the work remaining in the form of story points along the vertical Y-axis and the working days along the horizontal X-axis. The pending work is typically represented in story points – a unit of measurement to calculate the importance and priority of user stories in the sprint backlog – instead of user stories. The reason is user stories are broken down into tasks during the second half of the sprint planning meeting by the development team. It becomes difficult to read and understand the chart if tasks are represented along the Y-axis. User stories are descriptive in nature, and do not have a number or a value associated with them, so it becomes difficult to estimate them. Therefore, the story points, which are numeric values associated with each user story, are used for plotting purposes. Know more on http://ezinearticles.com/?Explanation-Of-Scrum-Burndown-Charts---The-Plotting,-Requirement,-And-Purpose-Of-Burndown-Charts&id=8371905 

          "Please visit http://www.quickscrum.com to download the Quickscrum tool"  
  

Monday 10 March 2014

The Dos and Don’ts of Servant Leader Role for Scrum Masters

What is understood by the term “servant leader”?
Several experts have tried to define the role of a servant leader, as to what it should ideally include, and what scrum masters should do to be considered as good servant leaders. To summarize what the authors have to say about the role, individuals desiring to function as good servant leaders should be compassionate, exhibit humane characteristics, act as a facilitator, and be a mentor for individual team members. Rather than discussing in details about each characteristic, the role can be briefly understood by going through the Dos and Don’ts associated with the servant leader role.

What the scrum master should ideally do to become a good servant leader
·       Protect the team and its members from distractions and diversions
·       Facilitate the planning activities and sessions
·       Encourage team members to participate in sprint reviews and retrospectives  
·       Implement scrum methodology and coach scrum to team members
·       Help the team to collaborate
·       Publicly represent and protect the team’s position
·       Anticipate issues and problems likely to occur during the sprint activity
·       Discover ways and means to remove the impediments faced by the development team
·       Ensure daily scrum meetings are properly conducted as per scrum principles and rules
·       Support and encourage transparency while implementing the project
·       Properly understand and present the team’s progress to the investors and stakeholders
·       When necessary, arbitrate on behalf of the team members

What should be avoided or prevented
·         Provide instructions directly or indirectly to the development team.
-        The scrum master should act as a facilitator and help the team members to find solutions on their own through guidance, advice, and suggestions.
·       Manage the daily scrum meeting
-        Rather than directing the team and providing development related solutions, the person should supervise scrum and ensure the team members follow it properly.
·       Estimate the work taken up by the team
-        If the team is coming up with an estimate, the scrum master should not interfere by suggesting or advising as to what the estimate should ideally include. If required, the person can arbitrate on behalf of the team.
·       Remain uninvolved or be unconcerned about where the team is heading

-        Always try to maintain a holistic attitude about how the project is proceeding, and how the project can be affected by the work carried out by the development team. One should be clear about the project goals and how the team is currently achieving them.

             "Please visit http://www.quickscrum.com to download the Quickscrum tool"