Typical day of a Scrum Master

Is there a specific question/concern you have Sahiti?   The answer to your initial question is probably more like a book than an answer that can be posted here.

Regarding what a Scrum Master "delivers", I never really considered my role as one that delivers something on a daily basis.   It is always my hope that through my interactions with my team and the organization, that they will be in a better place and continue to seek improvement each day.

Congratulations for certificate..... As a Scrum Master what i do on daily basis:

- I have to be comfortable with uncertainty. The very nature of the process is that things will change and shift constantly--work moving in and out of sprints, focus shifting from feature to feature, and from new development to bug fixing and back again.

- I deal with constantly shifting nature of requirements, changes and priorities and to be flexible with higher management and dev team.

- I make facilitation but it does not mean I don't impose my will on my team. I do so whenever I see outage within process. I take care of roadmap of product release. 

 

- I do try to introduce new things which can enhance the productivity of dev team and from product point of view focus on collecting product requirements from many direct/indirect stakeholder. 

- Most important point, ensuring that the ultimate deliverables are on time, scope, quality, and under budget. It seems like a work of Project Manager in traditional project management but i think it is crucial for a SM. 

Besides above, I do care of training dev team and agile coaching in org. 

Expect to spend most of your day with people who want to change Scrum rather than change their existing practices. The greater part of the issues you deal with will be either directly or indirectly related to that problem.

Are you guys working exclusively as SM at your company?

I spend a lot of my time creating training materials to tackle specific problems I've identified or a team has identified.  

I also spend a lot of my time continuing to learn about Scrum, Agile, Lean, etc. and how different concepts are applied, are lacking, or should be implemented in the organisation I'm working in.

Ian and Alex described my typical day pretty well.

Expect to spend most of your day with people who want to change Scrum rather than change their existing practices. The greater part of the issues you deal with will be either directly or indirectly related to that problem.

I think this is one of the best pieces of truth regarding Scrum that I've ever seen. 

Thank you all for great answers. But what really caught me was:

• Expect to spend most of your day with people who want to change Scrum rather than change their existing practices. The greater part of the issues you deal with will be either directly or indirectly related to that problem.

"Expect to spend most of your day with people who want to change Scrum rather than change their existing practices. The greater part of the issues you deal with will be either directly or indirectly related to that problem."

MY EVERYDAY BATTLE!!

Expect to spend most of your day with people who want to change Scrum rather than change their existing practices. The greater part of the issues you deal with will be either directly or indirectly related to that problem.

TRUTH!

While Ian's statement above is pure gold (diamonds, really, more transparent!), this checklist below has some typical things.

CAVEAT:  Do not ever think you can rotely implement the SM role well by following a checklist!

http://scrummasterchecklist.org/

While i find all answers very useful, i am curious to what traits/skills a scrum master has to have. Both soft and hard skills. What are the most important traits of SM?

Johannes,

Here are a few traits/skills that in my opinion are critical to being a successful Scrum Master, in no particular order, and certainly not exhaustive:

• desire to learn/improve
• servant-leadership skills
• consensus-building skills
• coaching skills
• solid understanding of Scrum
• patience
• acceptance of failure