SMC Practice Exam Questions with Answers Scrum Master Certified (SMC) Certification

You should demand the Development Team host a retrospective as it is a rule of Scrum.

You should discuss the situation with the Product Owner to see how she feels about no longer having a Sprint Retrospective.

You should require the key Development Team members to participate in the Retrospective to shorten its duration.

You should do nothing as the Development Team is self-organized and self-managed.

Help create Project Vision Statement

Identify key stakeholders of the project

Ensure back-up resources are available

Define Acceptance Criteria for User Stories

Recruit people from departments within the organization that can best support the project.

Hire a Scrum Coach to help the developers become self-managing.

You should allow the developers to self-organize into a Development Team.

Have the Development Team work directly the customers of the project.

Length of Sprint, Agreed Actionable Improvements, Done Criteria, Team Calendar.

Assigned Action Items, Business Improvements, Dependencies, Team Calendar.

Length of Sprint, Previous Sprint Velocity, Dependencies, Team Calendar.

Proof of Concept, Previous Sprint Velocity, Done Criteria, Team Calendar.

Expected Monetary Value.

Probability Impact Grid.

Pareto Analysis.

Risk Breakdown Structure.

Team velocity is the total number of hours the team has worked during a Sprint.

Team velocity is the total number of story points completed in a given Sprint.

Team velocity is the percentage of story points that have been Done versus those committed.

Team velocity is the actual time spent on delivering User Stories.

Increment

Project Plan

Test Case Specifications

Design Document

Project Status Report

Sprint Backlog

Product Backlog

Self-organization.

Collaboration.

Value-based Prioritization.

Theoretical process control.

Multiple Scrum teams can have sprints of different duration in one project.

When possible, Sprints should start on a Tuesday rather than a Monday.

The Sprint duration should not change once the project begins.

Multiple Scrum teams, in one project, can start their Sprints as soon as the Development Team is assembled.

Product Owner - invites to a grooming session only those stakeholders whose feedback is required and

who can make final decisions about which suggested changes can be considered as Formal Change

Requests.

Scrum Master - ensures that the requirements and Acceptance Criteria are not altered during the Sprint

Review Meeting.

Stakeholders - incorporate new and modified features into the deliverables whenever possible.

Scrum Team - decide whether the change can wait until the next Sprint or represents an urgent situation

that may require ending the current Sprint and starting a new one.

Leadership style, problem-solving, availability, commitment

Stress management, people management, communication, loyalty

Responsiveness, problem-solving, facilitator, negotiation

Intuitiveness, people management, reliability, facilitator

What will I work on today?

What did I complete yesterday?

Am I facing any impediments or obstacles?

How will I solve the impediments that I am facing?

The Scrum Master helps people outside the team communicate and work with the Scrum Team.

The Scrum Master is the time keeper for all Scrum meetings.

The Scrum Master prioritizes the Product Backlog.

The Scrum Master is the project manager of the Scrum Project.

5 to 12

5 to 9

3 to 9

3 to 15

3 to 6

3 to 12

Groom the Prioritized Product Backlog.

Coordinate creation of Release Planning Schedule.

Facilitate Prioritized Product Backlog Review Meetings.

Represent the Scrum Core Team to provide lessons from the project.

The Development Team will work with Martha to estimate the items in the Product Backlog with story points.

The Development Team will work with you, the Scrum Master, to create time and cost estimates for all the Product Backlog items.

Martha can estimate the items in the Product Backlog, but you, the Scrum Master, must be approve the estimates prior to each Sprint Planning meeting.

Martha can estimate the items in the Product Backlog, but the Development Team must approve the estimates prior to the Sprint beginning.

Flexibility: Business-environment-related risk

Regular feedback: Expectations-related risk

Team ownership: Estimation related risk

Transparency: Investment risk

4 hours or less

15 minutes

2 hours

1 hour

A framework to address complex adaptive problems

A collection of the industry's best practices in information technology

A body of knowledge on software engineering to build products

Tasks are easier to complete.

Scrum Teams are smaller in size.

Too large to be completed in a Sprint.

Take considerably longer time to review.

The Development Team needs a Sprint Goal to create a communications plan of who does what and when.

The Development Team needs a Sprint Goal to communicate exactly who'll do what in the Sprint.

The Development Team needs a Sprint Goal to create synergy among the Development Team members.

The Development Team needs a Sprint Goal so they'll see the value and importance of completing all of the user stories selected for the Sprint meet the definition of done.

C and D.

A and ?

?, B, and D.

All of the above.

You will direct the Scrum team to re-work the User Story in the same Sprint.

The Scrum Team will not re-work an already developed deliverable; however, the Product Owner will reject

the deliverable in Demonstrate and Validate Sprint.

The deliverable is rejected on the basis of the changed requirements, and added to the Prioritized Product

Backlog with the new Acceptance Criteria to be worked on in a subsequent Sprint.

You should inform the Product Owner that the Scrum Team does not have the bandwidth to re-work the

already created deliverable.

Daily Standup Meeting

Sprint Planning Meeting

Financial Planning Meeting

Prioritized Product Backlog Review Meeting

In Scrum, upfront planning is high, while in Traditional Project Management it is low.

In Scrum, performance measurement is based on plan conformity, while in Traditional Project

Management it is based on business value.

In Scrum, customer involvement is high throughput the project, while in Traditional Project it varies

according to the project's lifecycle.

In Scrum, Quality Assurance is process centric, while in Traditional Project Management it is customer

centric.

You should direct the Scrum team to stop working on the current Sprint Backlog, and to start working on

the latest business requirements.

The Product Owner should add this requirement to the overall Prioritized Product Backlog, and the team

would work on it in a future Sprint.

You should tell the Product Owner to inform the stakeholders that this business requirement cannot be

worked on as the Scrum Team has no bandwidth in the current Sprint.

The Product Owner should cancel the current Sprint, and should start planning a new Sprint for the team to

be able to develop the deliverable as per the latest business requirement.

The Development Team will consult on user stories for the Product Backlog.

The Development Team chooses the Product Owner for each Sprint.

The Development Team determines who'll do what task in the Sprint Backlog.

The Development Team will estimate the work of Product Backlog.

B and D

A and ?

?, B, and ?

Only ?

They reduce the productivity of a Scrum team.

Impediments can be both internal and external.

Impediments should be documented only by the team members in the Impediment Log.

Impediments faced are brought up by the Scrum Team during the Daily Standup Meeting.

The item is done when the item has no work remaining to be released.

The item is done when the product customer accepts the item.

The item is done when the Product Owner agrees that the item can be released.

The item is done when the Scrum Master agrees it is complete.

Forming

Storming

Norming

Performing

User Stories are objective, and the Acceptance Criteria provides the subjectivity required for the User Story

to be considered as Done.

In the Sprint Review Meetings, the Acceptance Criteria provides the context for the Scrum Master to

decide if a User Story has been completed satisfactorily.

It is the Scrum Master who has to ensure that the Acceptance Criteria for a User Story are not changed by

the Product Owner in the middle of a Sprint.

It is the Scrum Team's responsibility to keep track of what changes are being made to the Acceptance

Criteria even during the Sprint.

An impediment is any hindrance or hurdle that reduces the productivity of the Scrum Team.

Impediments can be internal or external to the team.

The Impediment Log must be shared with the stakeholders.

Impediments should be formally recorded by the Scrum Master in an Impediment Log.

No

Yes

True

False

A, C, and D

A and D

All of the above.

None of the above.

A

A and ?

? and ?

A and D

Scrum Master.

Product Owner.

Sponsor.

Scrum Guidance Board.

Eliminating all changes that may affect the quality of deliverables and processes

Facilitating identification of Change Requests by the Scrum Team and their assessment and prioritization

by the Product Owner.

Providing requests for changes in a project.

Approving changes that are amended, removed, or added according to project requirements, and

communicating the same to the Scrum Team.