CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Vmedu
  5. Scrum Master Certified

Free Scrum Master Certified Exam Braindumps (page: 15)

Page 14 of 37
PDF with 147 Questions

Scrum Master is the 'servant leader' of Scrum Team. In this context, which of the following is a key responsibility of the Scrum Master?

  1. Help create Project Vision Statement
  2. Identify key stakeholders of the project
  3. Ensure back-up resources are available
  4. Define Acceptance Criteria for User Stories

Answer(s): D



During a Daily Standup Meeting, several members of the team voice their concerns about some Acceptance Criteri


  1. Which of the following would be the best course of action?
  2. The Product Owner must proactively help the team solve issues during the meeting.
  3. The Product Owner should discuss the issues with the management and come up with solutions after the meeting.
  4. Discuss and resolve issues as and when they are spoken about during the meeting.
  5. Discuss among Core Roles after the meeting and resolve the issues.

Answer(s): C



Listed below are some risks and issues that might be encountered during the course of a project.
Identify which of the following are risks (not issues).

A) After extensive training, marketing representatives might still not be ready to take orders after the project is launched.
B) The painting crew might be delayed due to heavy rain, which could negatively impact the project schedule.
C) Funding was not approved.
D) Requirements, as currently defined, are unclear.

  1. Only
  2. A and C
  3. and D
  4. A and B

Answer(s): B



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?

  1. It is advisable to consider the Release Dates for the overall product or service to determine the Length of Sprint.
  2. The impact and frequency of expected changes do not have any impact on the decision related to the Length of Sprint.
  3. If the project is stable, with only minor changes expected, the Length of Sprint should be relatively shorter, 1 to 3 weeks.
  4. To get maximum benefits from a Scrum project, it is always recommended to keep the Sprint Time-boxed to 6 weeks.

Answer(s): A

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/






Post your Comments and Discuss Vmedu Scrum Master Certified exam with other Community members:

Scrum Master Certified Discussions & Posts