https://www.youtube

.com/watch?v=N7ns-w260qw

Join this channel to get access to perks: https://www.youtube.com/channel/UCNKuT9PW0nYjgxwFIRHyncg/join @BeingAgile Consulting #agile #scrummaster #interview #projectmanagement #productdevelopment Hey lovelies, thank you so much for watching! If you are looking to explore the Agile Coach/Scrum Master/RTE career path, if you are struggling with conquering that interview, if you are struggling with doing your job and you need a mentor/coach to guide you through this journey, we can help you! For Mentoring/Coaching services, please visit our website to learn more: Website: https://beingagileconsulting.com/screening-form/ Email: [email protected] Instagram: BeingAgile_Consulting FaceBook: BeingAgile Consulting LinkedIn: BeingAgile Consulting Great practical books for practicing and aspiring Scrum Masters: Essential Scrum: https://amzn.to/2V0fIBn Coaching Agile Teams: https://amzn.to/2V6Uzph DISCLAIMER ALERT: Some of the links in this description may be affiliate links which means that if you purchase this product through these links, we will get a small commission at no additional cost to you. Your purchase is a way of expressing your support to this platform which really encourages us to want to bring more rich contents to you every week. Thank you so much DISCLAIMER: This is not a sponsored video If you have a question/input regarding this video, please leverage the comment section. @Karen Fomafung – Your Agile Evangelist LinkedIn; linkedin.com/in/karen-fomafung 0:00 Introduction 0:09 5 things to Never Say during your Scrum Master Interview 3:16 Agile Methodology X . 5:11 I told X 6:55 I manage projects and teams X 8:46 Stop trying to claim all the credits X 12:06 Do not be output driven (The triple constrains) X

22 Replies to “5 Critical Mistakes Scrum Masters Make During Interviews – Agile Coach/RTE . Stop Saying these words”

  1. Thank you!!!! You got me to subscribe after you explained why we SHOULD NOT say Agile Methodology.

  2. 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.

  3. 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.

  4. 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!

  5. 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.

Leave a Reply

Your email address will not be published. Required fields are marked *