{"id":1016,"date":"2018-12-12T07:25:47","date_gmt":"2018-12-12T07:25:47","guid":{"rendered":"http:\/\/talentedtester.com\/?p=1016"},"modified":"2018-12-12T07:25:47","modified_gmt":"2018-12-12T07:25:47","slug":"who-is-the-scrum-master-in-agile","status":"publish","type":"post","link":"http:\/\/talentedtester.com\/who-is-the-scrum-master-in-agile\/","title":{"rendered":"Who is the scrum master in agile?"},"content":{"rendered":"
Agile without the Scrum master is like an orchestra without a conductor. In my years of Agile, this person is always the central person in the team.<\/p>\n
Who is the scrum master in agile? The scrum master is the organisor of an Agile development. Think of this person as the process manager of Agile or if you like, the linchpin that brings all the related project team together to follow the Agile process.<\/p>\n
Now that you understand from a high level what a scrum master does, you need to understand exactly what they do and how they fit into the process. If this interests you, please read on for more information.<\/p>\n
During an Agile scrum all project team members huddle together for a quick “stand-up” meeting. The reason it’s a stand-up meeting is so it physiologically reduces the expected duration.<\/p>\n
Meaning it is likely to be shorter and concise if you do not sit down, well that is the idea.<\/p>\n
The Scrum Master is effectively the organiser of the scrum and really wants to establish three key peieces of information from each scrum meeting attendee:<\/p>\n
Even though this may sound like the scrum Master is similar level to a project or programme manager, in reality this is not the case. The scrum master is just responsible for facilitating the scrum, not the outcome of the project or programme o work.<\/p>\n
During the scrum, we just established what the scrum masters role is. But what is their objective you may be thinking? Well they have a challenging task of keeping the team focused and most importantly avoiding blockers that could prevent progress within the current, or future sprints.<\/p>\n
As well as this, they have to make sure the team is in agreement with the direction of the day. For example, if you are asked “what is your plan today?”. Your response may be: “Work on the second drop down list data feed”.<\/p>\n
There is a chance that your response my cause an objection or suggestion to this a bit different. This is where scrum master is valuable to keep everyone on track and reach an agreement.<\/p>\n
As discussed earlier, the scrum master is not a project or programme manager. And in fact they may not have any real project level authority at all. However they do own the “process”.<\/p>\n
What does this mean? Basically they can decide how the scrum is organised, who speaks next. Or even if they want to make alterations to the sprint duration.<\/p>\n
Bare in mind, all of this is in theory. However, in my experience of testing throughout the years, the real authority to make these decisions stick depends on the politics of the company you work for and how respected that individual really is. But on paper, they should have the ability to do this.<\/p>\n
Apart from the actual scrum itself, the Scrum Master also ads value to the Product owner. In particular making sure that the team fully understand the product backlog and importance of having very clear and understandable backlog items designated to each sprint.<\/p>\n
The value add here is helping the development team come up with the highest quality products that they can. This is mainly by helping to remove any blockers that may be preventing their progress within the current sprint. Also making making sure they understand the sprint plan and how that related to the product backlog.<\/p>\n
In general the scrum master works to help the organisation understand and adopt the scrum process. Initially it can be hard to get a project team to conform because they are not used to the new process. This is where the scrum master really adds value.<\/p>\n