Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Masters of the Scrum Universe


Tweet: The key question to ask when creating your Scrum Roles: who knows what I/we should be working on? Learn more. #YourAgileCoach

If you have not read my first article here is a link to it for context.


Remember the three-legged stool analogy from my previous article well we are going to cover the second stool leg, my experience as a Scrum Master.

I have been a Scrum Master and I have had the opportunity to support a number of Scrum Masters within the software development industry. In my experience, the individuals that make the best Scrum Masters are those that want to support everyone in any way they can. Known as the servant-leader of teams within organisations they serve the Development Team and the Product Owner while leading best practices within the Scrum framework.

I have worked within a few organisations that have adopted the Scrum Master role without adopting the rest of the framework. The majority of the time, those organisations incorrectly implement the Scrum Master duties within another role, such as a member of the Development Team or the Product Owner, while not prioritising their duties as the servant-leader. This ultimately ends in the team and product suffering or the roles within the Scrum framework not attaining an efficient cohesion.

scrum master.jpg

You want to be a Scrum Master? Be a servant-leader; coach your team, teach your Product Owner, help your team to find the right tools for developing the product, understand and accept your limitations (your are not a product or development expert), facilitate the resolution of conflicts (talk-the-talk 😊), educate your product stakeholders on the benefits of Scrum, build a secure environment for your team to work productively.

In my next post, I’ll be talking about my experiences with the strongest stool leg of all, the Development Team.


Scott Theus
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Feb 04, 2019

Hi @[deleted],

It's interesting to read that in your experience "the majority of the time, those organisations incorrectly implement the Scrum Master duties within another role, such as a member of the Development Team or the Product Owner;" with those to roles mentioned specifically. Was that by chance, or are those the roles you commonly see combined with the Scrum Master role? 

I've seen the Scrum Master combined with the Project Manager, and as a member of the dev team, but rarely do I see the PO and the Scrum Master in one position. TBH, I think a PO combined with the Scrum Master would be a nightmare and would inject a large amount of bias into the Scrum team.


Deleted user Feb 05, 2019

Hi @Scott Theus,

Those are the roles I have commonly seen combined, though I have seen the Project Manager role combined with the Scrum Master role. On average those combinations have been more successful so I was not able to give a thorough opinion on that particular combination. 

Oh yes, a PO acting as a Scrum Master quickly breaks down as decisions and tailoring of the framework is biased towards the product as you mentioned. 

As a member of a dev team, what are you experiences when interacting with the other roles. 

Thanks for taking the time to read my article Scott :)  

AUG Leaders

Atlassian Community Events