Posted on October 12, 2015
by Doug Klugh

The role of a Scrum Master requires skills in a variety of disciplines.  But for starters, good soft skills are a must.  A good Scrum Master must be able to communicate effectively and be able to relate well to all team members.  He/She must be able to influence others and constantly sell the value Scrum to team members and other stakeholders.  Everyone has an opinion on how Agile principles should be applied and a Scrum Master must drive his/her team along the path carved out by the organization’s processes and methods.  It’s natural for a team to deviate from this path, but a good Scrum Master will constantly make small corrections to keep the team headed in a common direction.

Experience Matters

For software development teams new to Agile, it also helps to have a Scrum Master who has a strong background in software engineering disciplines and who has significant experience in applying Agile practices across various roles.  While Scrum teams are to be self-managing, new teams often need guidance breaking old Waterfall habits and forming new Agile habits.  As an example, many team members tend to plan around activities and delivering artifacts (such as design documents) that don’t offer any (direct) value to the customer.  It is often difficult getting team members to plan around functionality and focus on delivering value to the customer.  Scrum Masters who have experience writing use cases would be well suited to coach teams on writing stories which focus on functionality.  Many Scrum teams struggle with simply defining appropriate user roles, especially within a systems development organization.

If the Scrum Master does not have experience delivering software utilizing Waterfall, as well as Agile, it will be nearly impossible for him/her to relate to the issues that the Scrum team will face.  And if the Scrum Master does not have experience delivering a particular type of software (i.e. application software vs. system software), that will also inhibit his/her ability to coach the team; even in regards to applying Scrum processes to particular software development efforts.  The bottom line is…  domain knowledge and experience should always be prerequisites for anyone fulfilling a Scrum Master role.
Tags:
Agile Scrum Master software engineering Waterfall

Doug Klugh

Doug is an experienced software development leader, engineer, and craftsman having delivered consumer and enterprise firmware/software solutions servicing more than one billion users through 20+ years of leadership.

Related Items


subject Article

Scrum Methods:  Planning for Value

Steve Jobs was obsessed with providing the best user experience to his customers.  Because, above all else, that is what they valued most.  He was the grand master at delivering value to his customers.  Not necessarily in terms of dollars, but in terms of what they wanted.  And while technology helped get him there, his focus was always on exceeding the expectations of the user.

Read More
subject Article

Agile Is More Than Process

There is more to Agile than estimating stories, collaborating with customers, and showing working software.  Agile is also about technical excellence.  And this is where many Agile teams drop the ball.  All too often, teams focus too much on process and not enough on technical practices.  If the effort, complexity, and risk is too great for your team to extend and maintain their software, they will struggle to deliver functionality to their customers at the end of each iteration.  They will struggle to deliver working software as promised.

Read More
subject Article

A Dozen Ways to Fail at Scrum

Scrum provides a process framework to help realize the benefits of Agile principles.  The value of Scrum has been demonstrated many times, on numerous projects, throughout various industries.  It is a fairly simple and straightforward set of practices and guidelines that will (usually) result in greater adaptability to change, improved productivity, high quality products, and happier customers.

Read More
;