Scrum Master Mock Exam Flash Cards Video 2

[@fabioiyke5083]

Checking how far we are from the sprint goal, and status update sound like they are same

[@valueinsights]

Thanks for the feedback Fabio. So it looks a bit same but it is different. 🤓 A status update concentrate on what each developer did since last daily and what they plan to do next from the Sprint backlog. Checking how far we are from the Sprint goal (inspecting progress towards the Sprint goal as the Scrum Guide calls it) is looking for the developers to concentrate as a group on how to reach the Sprint goal and collaborate to create a plan for the day on how to get closer to it (actionable plan for the next day of work as mentioned in the Scrum Guide). Small but important difference. As a Scrum Master, you want to see your developers collaborate to reach the Sprint goal and work as a team instead of developers concentrating on their own individual tasks. This is how you can reach great team effectiveness for which the Scrum Master is accountable. I hope that this helps! 😄

[@sylviaujunwa]

Love the clarification. Both looks similar but means different thing.

[@jeevamlokii4937]

1st and 2nd question and question from videao1 related to scrum master * developers is bit confusing .. is it possible for you to make separate video for them and explain please

[@valueinsights]

Hello @jeevmlokii4937 thank you for your question! Here is an explanation regarding the first question in video 2: This question pertains to the purpose of the daily Scrum. According to the Scrum Guide, the daily Scrum serves to "inspect progress towards the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work". In other words, it is a time for the developers to come together and discuss their progress, identify any obstacles, and adjust their plans for the day in order to achieve or get closer to the Sprint goal. While it is important to note that the daily Scrum does involve providing updates on individual tasks, its main focus is not simply to give a status update. Instead, it is a collaborative effort to assess where we currently stand, determine where we want to be, and make any necessary adjustments to our work in order to reach our goal. Therefore, the primary purpose of the daily Scrum is to facilitate progress towards the Sprint goal, rather than just sharing individual updates. I hope this explanation clarifies the purpose of the daily Scrum for you. If you have any further questions, please feel free to ask!

[@valueinsights]

Here is a detailed explanation regarding the second question in video 2: This question pertains to the role of the Scrum Master in the daily Scrum. According to the Scrum Guide, the daily Scrum is a 15-minute event for the Developers of the Scrum Team. While the Scrum Master may facilitate the daily Scrum, it is not explicitly stated that the Scrum Master must lead it. The Scrum Guide emphasizes that the Scrum Master is accountable for the Scrum Team's effectiveness and ensuring that all Scrum events are conducted positively, productively, and within the timebox. However, it does not prescribe a specific role for the Scrum Master during the daily Scrum. In practice, especially in the early stages, the Scrum Master generally facilitates the daily Scrum to ensure its effectiveness, encourage collaboration, and assist the developers in addressing any impediments. However, it is entirely possible for the Developers to lead the daily Scrum themselves without direct involvement from the Scrum Master. This depends on the dynamics, maturity, and specific needs of the developers.

[@jamie-ho5fm]

you missed something on the sprint retrospective question you are reading the incomplete sentence the full sentence is "The most impactful improvement are addressed as soon as possible. They may even be added to the sprint backlog for the next sprint. So it clearly mentioned that actionable improvement are addressed soon, and they may be added to the Sprint backlog if need please clearify

[@valueinsights]

hello @jamie-ho5fm so I believe that the question you referred to is "An improvement created during a Sprint retrospective should come immediately to the next Sprint". And the answer to that is no. Why? The Scrum team will actually strive to implement key improvements devised in the retrospective as soon as possible but it is not an obligation that one (or more) of those improvements are brought immediately into the next Sprint. Of course, the spirit (and a recommended practice) is to address the most important improvement in a speedy and timely manner but it may happen that - for various reasons - this is not possible in the Sprint following a retrospective. I hope that this clarification helps.

[@jamie-ho5fm]

@@valueinsights i still didn't get this answer because it is clearly mentioned in scrum guide 2020 they add most impactful improvement to the next sprint and may even add to the next sprint backlog so this means team do add improvement to the next sprint orelse what is the point to do sprint retrospective but may add in the Sprint Backlog if needed the may is for sprint backlog not for the next sprint. please clarify

[@valueinsights]

@jamie-ho5fm Some clarity on what the Scrum events and artifacts are may help you there. Please read till the end :-) Let's start with a Sprint. A Sprint is a container event of 1 month max. which contains the 4 key events of Scrum: Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective. One Sprint follows immediately the next - Scrum is a continuous cycle of Sprints in terms of events. Now let's go for 2 of the Scrum artifacts. One of them is the product backlog. The product backlog is the wishlist of all the things which could be done for your product/services/whatever you are developing. Those things you have in your product backlog are called product backlog items. They may be developed during a Sprint or never at all, the product backlog being dynamic and new items may superseed older items based on value, prioritization, capacity, etc... Now another key Scrum artifact is called the Sprint backlog . The Sprint backlog consists of items selected from the product backlog for the Sprint (a subset of the product backlog if you will), the Sprint goal and the plan on how to get those items to done (build increment) and achieve the Sprint goal. Now what does that mean regarding our retrospective question? It means that during the retrospective, possible action improvements are devised by the Scrum team - there may be a lot, a little, some very valuable, some not so much, some requiring a lot of efforts, some easy to implement. Now, no matter how many improvements are created during the retrospective, there are two possibilities on how to handle them: 1- either place them in the next Sprint as items in the Sprint Backlog (ideal case, at least one top improvement selected by the team) OR 2- in case the team feels they cannot handle any improvement for the next Sprint for whatever reason (capacity, priority, capability, size of the item, etc...): include those actions improvements as items in the product backlog. They may therefore be selected in another Sprint later down the road but not immediately. A third choice would also be to give up entirely on those items but as you mentioned, it defeat the purpose of the retrospective. I hope that this helps this time :-)

[@jamie-ho5fm]

@@valueinsights Thanks this was useful to understand

[@jamie-ho5fm]

@@valueinsights i got a question which i am kind confuse is Scrum Master a management position is it true or false

[@AaminaSadiya-v5e]

Add more questions sir please

[@valueinsights]

Hello Aamina, you may find more Scrum Master questions on our website at valueinsights.ch