Free Scrum Master I (PSM I) Practice Assessment 2
Free Scrum Master I (PSM I) Practice Assessment 2
Results
40 of 60 Questions answered correctly
1 2 3 4 5 6 7 8 9 10
11 12 13 14 15 16 17 18 19 20
21 22 23 24 25 26 27 28 29 30
Correct Incorrect
False
Correct
This may be desirable, but it is not always
possible.
Correct
Sprint Planning – 8 hours or less,
Daily Scrum – 15 minutes or less,
Sprint Review – 4 hours or less,
Sprint Retrospective – 3 hours or less.
Incorrect
The Scrum Team consists of one Scrum
Master, one Product Owner, and Developers.
Incorrect
Small Scrum Teams typically work best. The
exact upper limit is not set by Scrum. 10 is a
recommendation.
Incorrect
The term “grooming” was removed from
Scrum many years ago and replaced with
refinement. This was due to negative
connotations with the word in many parts of
the world.
What tool(s) can be used for managing the Product
Backlog?
Correct
The Product Backlog can be managed using
various tools and none are prescribed by
Scrum.
True
Correct
A Scrum Master is always required. In
complex environments, things change and
the focus of the Scrum Master will change as
the Scrum Team matures in its use of Scrum.
False
True
Correct
The Product Owner is accountable for the
Product Backlog.
True
False
Correct
Releasing is not linked to Sprint cadence. Any
time we have an Increment we can choose to
release it or not. We do not have to release
the Increment at the end of a Sprint.
False
True
Correct
The Daily Scrum is a 15-minute event for the
Developers of the Scrum Team.
– The Scrum Guide
Stakeholders
The Developers
True
False
Correct
A Scrum Team must only work on a single
Product Goal at any time in order to
maintain focus.
A Scrum event
Incorrect
Product Backlog refinement is an ongoing
process in which the Product Owner and the
Developers collaborate
True
False
Incorrect
In past versions of the Scrum Guide, the
Sprint Planning event was described as
having 2 parts. This is no longer true.
Correct
As long as there is a product there will be a
Product Backlog containing work that may
be carried out in future.
The Developers.
Incorrect
In Scrum, the ideal would be to have all skills
needed to deliver the Increment on the
Scrum Team. If part of the Increment
includes documentation, then that skill
should be on the Scrum Team as well.
Correct
The Scrum Guide details 3 important topics:
Topic One: Why is this Sprint valuable?
Topic Two: What can be Done this Sprint?
Topic Three: How will the chosen work get
done?
The Developers
The Project
Correct
The Product Owner is also accountable for
effective Product Backlog management
– The Scrum Guide
The Developers
The Stakeholders
The Architect
Correct
Developers are the people in the Scrum
Team that are committed to creating any
aspect of a usable Increment each Sprint.
They determine the “How”
Select 3 answers.
Correct
The Daily Scrum is a 15-minute event for the
Developers of the Scrum Team.
[The] Daily Scrum focuses on progress
toward the Sprint Goal and produces an
actionable plan for the next day of work. This
creates focus and improves self-
management.
– The Scrum Guide
Correct
A chart which shows the amount of work
which is thought to remain in a backlog. Time
is shown on the horizontal axis and work
remaining on the vertical axis. As time
progresses and items are drawn from the
backlog and completed, a plot line showing
work remaining may be expected to fall. The
amount of work may be assessed in any of
several ways such as user story points or
task hours. Work remaining in Sprint
Backlogs and Product Backlogs may be
communicated by means of a burn-down
chart.
False
True
Correct
The Definition of Done is the commitment to
Increment and a mandatory part of Scrum.
Select 2 answers.
Incorrect
If we stop every time we hit a problem when
developing a product we would rarely move
forward. Developers should practise the “art
of the possible” and do what they can to keep
going. Leaving the testing for later or
another team will increase risk and mean we
do not produce Done Increments.
If this has become an Impediment then the
Scrum Master has the responsibility to get
involved.
Correct
A Scrum Team includes 3 accountabilities.
Scrum Master, Product Owner and
Developers.
Correct
The Product Backlog is a living artifact that
evolves as the product and the environment
in which it will be used evolves. Therefore, it
is unlikely to ever be truly complete as long
as the product is being developed and
maintained.
Correct
Burn-up and Burn-down charts are not
mandatory in Scrum. The Product Owner
may find either useful.
Stakeholders
Correct
The Developers who will be doing the work
are responsible for the sizing. The Product
Owner may influence the Developers by
helping them understand and select trade-
offs.
– The Scrum Guide
What happens when a Sprint Goal becomes
obsolete?
Correct
The Product Owner has the authority to
cancel a Sprint if the Sprint Goal becomes
obsolete, although this is generally a rare
occurance.
Who can change the Sprint Backlog during a Sprint?
The Developers
The Stakeholders
Correct
The Sprint Backlog is a plan by and for the
Developers.
True
False
Incorrect
Scrum includes the Definition of Done but
not the Definition of Ready. A Definition of
Ready is a complimentary practice to Scrum.
True
False
Correct
A realistic forecast should be created in
Sprint Planning.
The entire Scrum Team is accountable for creating a
valuable, useful Increment every Sprint.
False
True
Correct
The entire Scrum Team is accountable for
creating a valuable, useful Increment every
Sprint.
Sprint Retrospective
Sprint Planning
Sprint Review
Correct
The Sprint Retrospective is timeboxed to a
maximum of three hours for a one-month
Sprint. For shorter Sprints, the event is
usually shorter.
Correct
Multiple Product Backlog items can have the
same priority whereas there can only be one
order in a Product Backlog. Order ensures
that it is clear what the Scrum Team will
work on first. Prioritisation may not make
this as transparent.
Incorrect
The purpose of the Sprint Review is to
inspect the outcome of the Sprint and
determine future adaptations.
– The Scrum Guide
No one
The Developers
Incorrect
Burn-down and Gannt chart are not
mandatory in Scrum
Correct
There’s no difference between the first
Sprint and the next ones. The main purpose
of each Sprint is to meet the Sprint Goal
through the delivery of a shippable
Increment.
Correct
When working inside timeboxes, it is best to
limit work-in-progress and get items done
before moving on. Limiting work-in-progress
is a lean concept that helps to manage waste.
Business Analysts
Testers
Software Architects
Incorrect
Within a Scrum Team, there are no sub-
teams or hierarchies.
– The Scrum Guide
True
False
Correct
The Scrum framework is purposefully
incomplete, only defining the parts required
to implement Scrum theory. Scrum is built
upon by the collective intelligence of the
people using it. Rather than provide people
with detailed instructions, the rules of Scrum
guide their relationships and interactions.
Burn-down charts.
Release burn-ups.
Code refactoring.
Incorrect
Scrum is a lightweight framework. The
practices, tools, and processes are chosen by
the Scrum Team and are dependent on their
specific situation.
True
False
Incorrect
While many Scrum Teams do this, it is not
required by Scrum. Estimation is not
mentioned in the Scrum Guide.
Selecting how much can be completed within
a Sprint may be challenging. However, the
more the Developers know about their past
performance, their upcoming capacity, and
their Definition of Done, the more confident
they will be in their Sprint forecasts.
True
False
Correct
Whilst this may be desirable, it is impossible
when doing complex work.
Correct
The Sprint Backlog should have enough
detail that the Developers can inspect their
progress a at the Daily Scrum.
An Increment is...
All work that has happened up to the
current point in time
Incorrect
Each Increment is additive to all prior
Increments and thoroughly verified,
ensuring that all Increments work together.
True
Incorrect
The “3 questions” are a popular, but optional
practices the Developers may use at the
Daily Scrum. There are many other practices
that can be used instead.
The Developers
Correct
Scrum Teams are cross-functional, meaning
the members have all the skills necessary to
create value each Sprint.
– The Scrum Guide
This means the team as a whole needs all the
skills. It does not mean every person has to
have all the skills.
The Developers
The stakeholders
Correct
The Product Owner is a for accountable for
ordering the items in the Product Backlog.
The Scrum Master is responsible for?
Incorrect
The Scrum Master is accountable for
establishing Scrum as defined in the Scrum
Guide. They do this by helping everyone
understand Scrum theory and practice, both
within the Scrum Team and the organization.
– The Scrum Guide
The Scrum Master is a management role.
False
True
Correct
The Scrum Master is a manager, but for the
Scrum framework, rather than for the people
in the Scrum Team.
False
True
Correct
By the end of the Sprint Retrospective, the
Scrum Team should have identified and
planned improvements to increase its
effectiveness.
False
True
Correct
The Scrum Master manages the Scrum
framework, not the Scrum Team.
True
Correct
The Sprint Retrospective is typically internal
to the Scrum Team. If others are present
transparency may be impacted.
False
True
Correct
Scrum does not forbid people holding more
than 1 accountability. It can often cause
problems, but sometimes it may be
appropriate.
True
False
Incorrect
Team size is recommended, rather than
mandated by Scrum. This was always true
even before the 2020 update. Here is the
current guidance from the Scrum Guide:
“The Scrum Team is small enough to remain
nimble and large enough to complete significant
work within
a Sprint, typically 10 or fewer people. In general,
we have found that smaller teams communicate
better and are more productive. If Scrum Teams
become too large, they should consider
reorganizing into multiple cohesive Scrum
Team.”
What is velocity?
Correct
Velocity is an optional, but often used,
indication of the amount of Product Backlog
turned into an Increment of product during a
Sprint by a Scrum Team
True
False
Correct
Whilst this can be done, it is not mandatory.
The Scrum Guide says this about Sprint
Planning “This is often done by decomposing
Product Backlog items into smaller work
items of one day or less. How this is done is
at the sole discretion of the Developers. ‘