SMC Scrum Master Certified (SMC) Questions and Answers

Gap analysis.

SWOT analysis.

Proof of Concept.

Speed Boat.

Effort spent in each Sprint increases gradually, as the team gains momentum to deliver.

Effort spent in each Sprint decreases gradually, as the team becomes more familiar with the expected

deliverables.

Effort expended in the present Sprint is similar to the effort spent on the previous Sprints, and is a

comfortable pace for the team.

Effort spent in the Sprint is directly proportional to the cost incurred in the Sprint.

Scrum Expert, Business Domain knowledge, Highly motivated.

Collaborative, Self-organizing, Negotiation skills.

Business Domain knowledge, Collaborative, Cross-functional outlook.

Collaborative, Highly motivated, Independent.

Quality Control involves execution of planned quality activities; Quality Assurance involves carrying out

integration-type activities.

Quality Control lessons are learned during the Sprint Retrospect meeting; Quality Assurance is

demonstrated during the Sprint Review Meeting.

Quality Control activities are carried out during the process of Creating Deliverables that are potentially

shippable; Quality Assurance activities are usually standalone activities, not carried out as part of the work.

Specific skills are not required to perform Quality Control activities; Quality Assurance is a significant factor

of the definition of Done.

Yes it's a good time to start the first Sprint

No, we should wait for the whole backlog to be completed before starting the Sprints

Seeking help from team members

Experienced team members mentoring new members

Recording Lessons learned to improve processes and address problems

Using information radiators to track the project progress

Fist of Five.

Wideband Delphi.

Affinity Estimation.

Planning Poker.

Value-based prioritization

Appropriation

Iterative development

Transparency

Scrum Master.

Product Owner.

Sponsor.

Scrum Guidance Board.

Awareness, articulation, and appropriation

Transparency, precision, and coordination

Perfection, cooperation, and comprehension

Honesty, responsiveness, and adaptability

Industry and project types are not determinants of change requirements.

Change management is executed in the ongoing processes of prioritizing and adding user stories to the

Prioritized Product Backlog.

The type of change is independent of stability or the dynamic nature of a project.

Once changes have been accounted for in the Prioritized Product Backlog, the team need not be

concerned about the time and resources available to accomplish the tasks during Sprint.

Having multiple checkpoints and a thorough review by senior management at those checkpoints

Using short iterations called Sprints

Having a detailed and extensive risk management plan

Identify Scrum Master and Stakeholder(s)

Estimate User Stories

Conduct Daily Standup

Commit User Stories

Discuss ways to resolve technical impediments faced by development teams, especially if two or more

teams face the same issue.

Discuss what each individual development team member has worked on since the last time all Scrum

Masters met.

Discuss actions of a team that could potentially affect another team.

Share a status update on all individual team member' tasks.

The definition of done creates transparency over the work inspected at the Sprint Review.

The definition of done guides the Development Team in creating a forecast at the Sprint Planning.

The definition of done defines what it takes for an increment to be ready for release.

The definition of done defines the duration and cost of a sprint.

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.

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.

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

Updated with new tasks and completed tasks.

Placed besides the new one to compare team velocities in Sprints.

Analyzed by the Scrum master to understand the project progress in that particular sprint.

Reset or wiped off.