You are correct; however, the word "can" is not in the question. "Sprint backlog contain..." is a definitive statement and there are times where there are no such items in the Sprint backlog. This is a trick they use to get us lol
In this question, if the author marked **b) False**, it might be due to a literal interpretation of the sentence and the fact that it lacks the word **"can"** (i.e., "can contain"). Without this word, the sentence implies that **the sprint backlog always** contains improvement items from the retrospective, which is not necessarily true. Improvement items identified during the retrospective may or may not be added to the sprint backlog. The team has the right to decide whether those items will be included in the backlog or addressed in another way. In this sense, a more accurate statement would be **“Sprint backlogs can contain items for improvement”**, which implies a possibility, not a certainty. Therefore, if the author pointed out the absence of the word "can" as the reason for marking **b) False**, it would be correct from the standpoint of linguistic precision.
Q20: option d). If PO put the requirements from "important executives"=stakeholders into the backlog, does'nt it mean that Scrum team can manage such ad-hoc high priority requrements?
Q68 according to your video on the sprint burn down chart, days are on the X-axis, however when I google sprint burn down chart all the outcomes show days on the Y-axis on the bottom. Can you confirm what is the right answer?
Question 48's suggested answer makes no sense, and my assertion is supported by the suggested answer to the very following question 49. According to the "immutable" Scrum Guide, "the purpose" of the Review is for developers AND stakeholders to inspect the increment. How can that happen if stakeholders are not required to be there? The Guide continues to set forth that the Sprint Review is a "working session and the Scrum team should avoid limiting it to a presentation", which is basically saying it's two-way, collaborative, between the team and the stakeholders. Without their feedback, what's the point of the Review at all? Again, referring to the Scrum Guide, "if Product Backlog item does not meet the Definition of Done, it cannot be released OR EVEN PRESENTED AT THE Sprint Review." Since the Developers knew, going into the Review, that they had an Increment to present because they'd have confirmed it met the Definition of Done, there's nothing to gained or learned from going into a Review by themselves. And, low and behold, in question 49, stakeholders are among the applicable answers, along with the owner and developers, in participating in the inspection. Which is correct. So there's no way they cannot be required to show up at the Review. Many people have recommended not trying to memorize answers to questions, but to use one's own reasonable application of the mindset and lightweight framework. So, I'd absolutely answer a question like this consistent with what I'm understanding of the Scrum Guide, and if it ends up being marked wrong, I'm going to be ticked off.
Thank you for the really good video. However, I can not understand the answer to question 49. Scrumguide has nothing about Stakeholders ability to perform inspection of scrum events.
The Sprint Review is a working meeting where the Scrum Team presents their completed work to their stakeholders and asks for feedback and guidance. Together, the Scrum Team and stakeholders discuss the progress made toward the Product Goal, any emerging changes in the business or technical climate and collaborate on what to do next.
The Sprint Review is a working meeting where the Scrum Team presents their completed work to their stakeholders and asks for feedback and guidance. Together, the Scrum Team and stakeholders discuss the progress made toward the Product Goal, any emerging changes in the business or technical climate and collaborate on what to do next.
This is why I hate this test. Look at question 69, the correct answer states active stakeholders are required, but in quesiton 48 they are not. This is an example of many inconsistencies in scrum.
There are some wrong answer. Like if time boxed events exceed the time limit, it means that scum master didnt eductae developrs enough about importance of time box, and not the efforts of develoeprs
Question 45: Scrum recommend 10 or less but it's up to the teams to decide how they want to be formed, and especially for some very complex products they can be more than 10
So many are really BAD questions and answers.....Out of the boundaries of the Scrum Guide, others using terms that are never used in Scrum Trainings and Formal Documentation.... Event they refer to the ROLES when Accountabilities is the correct term.... Not helping people is the true
Question 34: Scrum team is usually between 3-9 people
Great resource. Thank you!
Scrum Guide says 10 or less.
Meaning more or less PO, SM + 8devs.
Nope, its 10 or less
10 or less, homie
@@niels.ae4301 😊😊😊
@@SapienSafari if the answer is 10 or less, it means 1 or 2 persons can be a scrum team then
Thank you Sir/Mam. It was very helpful. I'm now ready for my regd scrum master. Regards
This video helps a lot, thanks!
56) Improvements from the Sprint Retrospective can become PBIs and therefore get selected into the Sprint Backlog? Can't they?
Well spotted. That was my thought too!
You are correct; however, the word "can" is not in the question. "Sprint backlog contain..." is a definitive statement and there are times where there are no such items in the Sprint backlog. This is a trick they use to get us lol
In this question, if the author marked **b) False**, it might be due to a literal interpretation of the sentence and the fact that it lacks the word **"can"** (i.e., "can contain"). Without this word, the sentence implies that **the sprint backlog always** contains improvement items from the retrospective, which is not necessarily true.
Improvement items identified during the retrospective may or may not be added to the sprint backlog. The team has the right to decide whether those items will be included in the backlog or addressed in another way. In this sense, a more accurate statement would be **“Sprint backlogs can contain items for improvement”**, which implies a possibility, not a certainty.
Therefore, if the author pointed out the absence of the word "can" as the reason for marking **b) False**, it would be correct from the standpoint of linguistic precision.
Q20: option d). If PO put the requirements from "important executives"=stakeholders into the backlog, does'nt it mean that Scrum team can manage such ad-hoc high priority requrements?
Thanks for the questions it will surely helpful
Thank you, this was a great help.
question no 12- arent the scrum roles the scrum team? in that case the answer is only D . correct me if im wrong
Good, I watched it for CSM.
Q68 according to your video on the sprint burn down chart, days are on the X-axis, however when I google sprint burn down chart all the outcomes show days on the Y-axis on the bottom. Can you confirm what is the right answer?
B is good answer.
@piotrpol1415 how? Try to Google the charts and you will see that the answer is C
Same here
32: developer is not a role, developerS is.
Thank you for the PDF. It is great help!
Please share pdf
hey i am unable to access the pdf can you reupload it?
Thanks, it's really helpful
I'm glad!
Thanks you very much..this is very very helpful :)
Question 48's suggested answer makes no sense, and my assertion is supported by the suggested answer to the very following question 49. According to the "immutable" Scrum Guide, "the purpose" of the Review is for developers AND stakeholders to inspect the increment. How can that happen if stakeholders are not required to be there? The Guide continues to set forth that the Sprint Review is a "working session and the Scrum team should avoid limiting it to a presentation", which is basically saying it's two-way, collaborative, between the team and the stakeholders. Without their feedback, what's the point of the Review at all?
Again, referring to the Scrum Guide, "if Product Backlog item does not meet the Definition of Done, it cannot be released OR EVEN PRESENTED AT THE Sprint Review." Since the Developers knew, going into the Review, that they had an Increment to present because they'd have confirmed it met the Definition of Done, there's nothing to gained or learned from going into a Review by themselves. And, low and behold, in question 49, stakeholders are among the applicable answers, along with the owner and developers, in participating in the inspection. Which is correct. So there's no way they cannot be required to show up at the Review.
Many people have recommended not trying to memorize answers to questions, but to use one's own reasonable application of the mindset and lightweight framework. So, I'd absolutely answer a question like this consistent with what I'm understanding of the Scrum Guide, and if it ends up being marked wrong, I'm going to be ticked off.
Some of these questions are not in the scrum guide. Am I missing something?
i’m confused too! how did the test go?
@@nismith58 did you end up taking the test for PSM1?
@ yes ! I passed actually
hi, the link is not working for me to download the questions
Thank you, for this!!❤
Q12 there are no roles, but accountabilities! Link in bio doesn't work to download the questions.
39. Is scrum master a Management Position? one of the CSM trainers specifically said they are not.
It is considered managerial, source: mastering professional scrum, Ockerman and Reindl.
This is helpful, thank you.
can the CSM exam contain some (all) of the questions in the video ?
Thank you for the really good video. However, I can not understand the answer to question 49. Scrumguide has nothing about Stakeholders ability to perform inspection of scrum events.
I think they are only invited in the sprint review meeting
The Sprint Review is a working meeting where the Scrum Team presents their completed work to their stakeholders and asks for feedback and guidance. Together, the Scrum Team and stakeholders discuss the progress made toward the Product Goal, any emerging changes in the business or technical climate and collaborate on what to do next.
who passed using this resource.
Detailed. Thank you
In question 48, should the Sprint Review include Stakeholders? They're the ones to inspect correct?
ONLY WHEN THEY ARE INVITED
The Sprint Review is a working meeting where the Scrum Team presents their completed work to their stakeholders and asks for feedback and guidance. Together, the Scrum Team and stakeholders discuss the progress made toward the Product Goal, any emerging changes in the business or technical climate and collaborate on what to do next.
This is why I hate this test. Look at question 69, the correct answer states active stakeholders are required, but in quesiton 48 they are not. This is an example of many inconsistencies in scrum.
The link to download questions doesn't work.
did you take your PSM1 test yet? i'm just curious what you found to be the most helpful learning aid
thanks
Ques 39,42,48,56,58,66,76
Please is anyone able to download the pdf.
Tried several times but could not
Good one thank you
Is this similar to the format of the test?
yes it should be!
19? Structuring the team such ..... has the team structure?
Thank you ❤
There are some wrong answer. Like if time boxed events exceed the time limit, it means that scum master didnt eductae developrs enough about importance of time box, and not the efforts of develoeprs
it is sprint planning meeting and not daily scrum meeting so it is possible to have developers getting to understand the products backlog.
Thanks
i cant downlaod the question need help
Some of those questions/answers are somewhat ambivalent.
agree, there are some inconsistencies in scrum testing which is frustrating.
Question 45: Scrum recommend 10 or less but it's up to the teams to decide how they want to be formed, and especially for some very complex products they can be more than 10
helpp.... esta todo en ingles
Weird ressource
So many are really BAD questions and answers.....Out of the boundaries of the Scrum Guide, others using terms that are never used in Scrum Trainings and Formal Documentation.... Event they refer to the ROLES when Accountabilities is the correct term.... Not helping people is the true