Questions for the SMC were updated on : Oct 04 ,2024
During a Scrum of Scrums, each Scrum Team representative provides an update on which of the following:
A) What has my team been working on since the last meeting?
B) What will my team do until the next meeting?
C) How many story points has my team completed since the last meeting?
D) What is our team planning on doing that might affect other teams?
A
Explanation:
Reference: http://www.cs.vsu.ru/~svv/spm/SBOK_Guide_3rd_edition_English_Sample.pdf (59)
During a Daily Standup Meeting, several members of the team voice their concerns about some Acceptance Criteria. Which
of the following would be the best course of action?
C
Scrum Master is the 'servant leader' of Scrum Team. In this context, which of the following is a key responsibility of the
Scrum Master?
C
Which of the following activities is NOT a part of the implementation phase in Scrum?
C
Explanation:
Reference: http://blog.scrumstudy.com/exploring-the-implement-phase-of-a-scrum-project/
One of the responsibilities of the Scrum Master is to ensure that the Product Owner does not change the Acceptance Criteria
of a committed User Story in the middle of a Sprint. In this regard, which of the following statements about Acceptance
Criteria is correct?
B
Explanation:
Reference: https://blog.teamtreehouse.com/when-is-a-user-story-done-acceptance-criteria-definition-done
George is a Scrum Master on a project to develop a Course Management System and Leave Management System for
Greyward University. He is maintaining an Impediment Log. Which one of the following statements is NOT TRUE regarding
Impediment Logs?
C
Explanation:
Reference: http://blog.scrumstudy.com/scrumstudy-scrum-video-on-daily-standup-meeting-and-its-importance-to-a-scrum-
team/
Which of the following is a tool that can be used for communicating information related to risks?
B
Explanation:
An important tool which can be used for communicating information related to risks is the Risk Burndown Chart.
Reference: http://blog.scrumstudy.com/risk-prioritization-and-communication-in-scrum/
Which of the following comparisons is true about Scrum and Traditional Project Management?
C
Explanation:
Reference: http://blog.scrumstudy.com/why-use-scrum-2/
You are a Scrum Master on a project that is preparing to begin its first Sprint. You explain to the Scrum team the concept of
Daily Standup Meetings. You include all of the following points in your introduction to the Daily Standup Meeting, EXCEPT:
B
Explanation:
Reference: https://www.mountaingoatsoftware.com/agile/scrum/meetings/daily-scrum
The table given below presents some Scrum roles that play an important part in business justification and their
responsibilities. Choose the option that correctly matches each role in the left hand column to its action in the right hand
column.
D
Suppose you are a Scrum Master on a project to design a metro rail system for a city. It has been brought to your attention
that the Product Owner wants to change the Acceptance Criteria for one of the User Stories committed to for the current
Sprint because the customer has changed a critical business requirement. Which one of the following statements presents
the best solution for such a situation?
B
Which of the following events does NOT help the Scrum Team in identifying or resolving risks?
D
Explanation:
Reference: http://blog.scrumstudy.com/risk-management-in-scrum/
Collaboration within a team is an important principle of Scrum. All of the following activities constitute collaboration EXCEPT:
A
Explanation:
Reference: https://www.oreilly.com/library/view/head-first-agile/9781491944684/ch04.html
Change must be integrated properly in the Prioritized Product Backlog. In this regard, which of the following statements is
true?
D
Explanation:
Reference: http://blog.scrumstudy.com/change-management-in-scrum-framework/
As a Scrum Master, you have to coordinate with the Product Owner to ensure that an appropriate Length of Sprint is
determined keeping in mind the changes expected. Which of the following statements is true in this regard?
C
Explanation:
If project requirements are generally stable and major changes are not expected in the near future, the Length of a Sprint
may be set to be longer, 4 to 6 weeks. This provides stability to the
Scrum Team members to work on the Prioritized Product Backlog requirements for lengthy periods of time without having to
go through the Create User Stories, Approve, Estimate and Commit User Stories, Create Tasks, Estimate Task, and other
related processes that are conducted for every Sprint. However, if project requirements are not very well defined or if
significant changes are expected in the immediate future, the Length of Sprint may be relatively shorter, 1 to 3 weeks. This
provides stability to the Scrum Team members to work on shorter Sprints and deliver results, which can be evaluated by the
Product Owner and stakeholders at the end of the Sprint. This also provides enough flexibility for them to clarify
requirements and make changes to the Prioritized Product Backlog at the end of each Sprint.
Reference: http://blog.scrumstudy.com/change-management-in-scrum-framework/