5 Critical Mistakes Scrum Masters Make During Interviews - Agile Coach/RTE . Stop Saying these words 

Wonderful Video and very insightful. I learnt 5 major mistakes which generally we do during scrum master interview. 1. We are saying - We worked on Agile Methodlogy. Correction- Never ever say Agile is a methodology. Agile is a mindset where we bound to scrum pronciples and values by 3 Accountabilities, 5 Scrum Events and 3 Artifacts. 2. Never Say " We/I told" Correction: Scrum Master is for coaching/training/Facilitating/Guiding the scrum princples,values and its events so instead of saying we/I told , say I suggested/guided/coached 3. Never Say I manage 2 teams when Interviews asked you howmany teams have you handled. Correction: As Scrum Master is not a Project Manager, he never manage any project. He is coaching/leading the 2 scrum team. 4. Do not mention I word when you are talking about team's success Correction: Always use "We" when you are talking about Team's Success 5. Do not focus only on Output Focus on metrics especially placing more values on customer satisfaction than output when it comes to measuring success.

Karen, your videos have great inputs and I appreciate all that you do for the Agile community! If I may give u one suggestion/feedback. In your summary, can you quickly recap the points you mentioned during the video. (For ex: in this video, quickly say those 5 things, not to say in an interview) It’d help me, make note of it and revisit them before an interview. Thank you!

I agree with the points, except that I won't shoot anyone for saying Agile Methodology even though I understand where you're coming from. Methodology by itself refers to a body of methods, rules, and postulates employed by a discipline and that is exactly where the concept of Agile started from - the thought that principles of traditional project management would work for what was a new software engineering discipline from the 50s into the 70s when concerns over repeatedly failed projects sparked debates on better ways of delivering software projects. Various discussions and debates led to words like incrementally, iteratively and then to agile as a methodology. Over the years however, it has evolved from practices to deliver projects to include, who we are, our mindsets, cultural practices, way of thinking, way of working, etc. Hence, we talk in terms of agile thinking, agile mindset, agile way of working. However, if the discourse is on whether a named project should be run using traditional project management or agile methodology, there is no harm is saying we'll adopt agile methodology. It just simply means you'll be looking to develop iteratively in small increments irrespective of the framework that you adopt, whether Scrum, Less, SAFe, etc. As far as all the other ingredients of psychological safety, trust, open communication, etc. they should exist even if you were adopting a traditional project management approach anyway. What is key is the understanding and context. Of course, if you're discussing agile across an enterprise then it's right to talk in terms of agile way of working, agile mindset, agile thinking... Just thought I'd make this point so that no one out there who maybe has a candidate in front of them saying they delivered a project using agile methodology interprets that to mean they've said rubbish. Absolutely not! But you do need to go further to explain how you delivered value outcomes, the nuances you faced and how you dealt with them, etc. OR your interviewer says to you, can you tell me the difference between traditional (or waterfall) and agile methodology, and you start by saying to them that it is wrong to say agile methodology. No! There is such a concept in project management, and agile methods require you to deliver requirements iteratively and incrementally. They integrate planning with execution, allowing an organisation to create a working mindset that helps a team respond effectively to changing requirements.

Amazing video, very insightful! I learnt so much in this short video, especially placing more value on customer satisfaction than output when it comes to measuring success. Thank you so much 😁

This is much needed for my upcoming interview! Thank you!

Amazing one thankful

Thank you for the video it was very helpful and informative.

You are amazing indeed just listen to your video. Will definitely keep in touch.

Thank you. Agile is not a methodology. But I thunk there are Agile methodologies: Scrum Framework, Kanban Framework, Lean , etc. My thought though

Hello I am so thankful for your video, I have an interview today for the position of Scrum Master so I will definitely keep these key points in mind, I am also looking for a mentor and would like more information please.

Very insightful, thanks so much for this piece. Much needed for me.

Hello BeingAgilist, thank you for watching. I used to make the 3rd mistake in the past (a lot). What are some of the mistakes you have made or still making? Lets discuss

This has been very informative, thanks Karen

Thanks for the info

Great information as always. Thanks Karen

Golden informations once again, thank you!!!🙌🙌

How easy for an auditor to switch career to IT as a scrum manager? Thank you for your advice

This is so helpful . Thanks so much

As a scrum master how do you support P.O? Answer?

Thank you

Starts at 2:46

In India most scrum masters openings show the description of project management.

This so Impressive. Love the tutorial. More grease to your elbows.

This was good advise. Thank you

Oooo this was great!

Hi , all your videos are amazing 🙏🙏

Hello great video I’m interested

5 stars . U are such a helper

Good work 👌

Interesting. Thanks for sharing.

Great video

Quite insightful. Thank u

Great video! How do I get into a phone meeting with you ?

Thanks!

True talk.

What would you say is biggest difference between an agile coach and scrum Master.

How do I get in touch with you?

Another 1 👍🏾

Please am a new scrum master I need that one on one . U