PSM-I Practice Assessment

/80

4881

PSM-I Practice Assessment

Explore Your Scrum Knowledge: Take the Scrum Master Foundation Quiz Today!

1 / 80

Which statement best describes the Product Backlog?

It provides just enough information to enable Scrum team to start the design phase of a product

It contains all foreseeable tasks and requirements from which the Scrum Team can develop and maintain a complete project plan

It is baselined to follow change management process

It evolves as more is learned about the product and its customers, and exists as long as a product exist

When the final version of a product is rolled out, a Product Backlog is no longer needed.

2 / 80

What should the Scrum Master to when the Product Owner and Developers are not collaborating throughout the Sprint? (choose the best two answers)

Cancel the Sprint and escalate it to the higher management

Coach the sponsor to form a new Scrum Team

Bring up the concern during the next Sprint Retrospective

Coach the entire Scrum Team on value of collaboration and team goals

Let the Product Owner and Developers resolve their issue

3 / 80

What best describes the agenda of the Sprint Planning?

Why is this Sprint valuable, What can be Done this Sprint and How will the chosen work get done?

How conditions have changed and how the Product backlog should evolve

What went wrong in the last Sprint and what to do differently this Sprint

What to do and who will do it

Who is on the team and what team member roles will be

4 / 80

What happens to the NFRs (non-functional requirements) within Sprint?

They are acted upon by a dedicated team

They are addressed in the hardening Sprints

They are addressed in every Increment

They are added to a separate Product Backlog

5 / 80

What will happen if a new developer is added to an existing Scrum Team?

Its productivity is likely to stay the same

Its productivity is likely to increase

Its productivity is likely to decrease

6 / 80

Which statement about the Sprint Review is correct? (choose the best answer)

Sprint Review is a demo where developers present the items completed in the Sprint

Sprint Review is a demo to Product Owner on the work done by developers in the current Sprint

Sprint Review is where stakeholders and Scrum Team inspect the outcome of the Sprint and determine future adaptations

Sprint Review is optional in Scrum if there is nothing to be presented to the stakeholders

7 / 80

What are the characteristics of a Scrum Team? (choose the best two answers)

The Scrum Team has at least one tester

The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint

Scrum Team members have compatible personalities

Scrum recognizes no sub-team or hierarchy in the Scrum Team

The Scrum Masters tells the Scrum Team on what to do

8 / 80

What activities would a Product Owner do during an active Sprint? (select all that is applicable)

Prioritize the Sprint Backlog

Engage with the stakeholders and answer questions from the Developers

Participate at the Daily Scrum

Update the burndown chart

Participate as a team member at the Sprint Retrospective

9 / 80

What enhances the transparency of an increment?

Updating Scrum Board properly in the electronic tracking tool

Doing all work needed to meet the Definition of Done

Storing all work in a document repository

Providing regular status update to the stakeholders

10 / 80

Which statements best describes the Definition of Done? (choose the best three answers)

It controls whether the Developers have performed their tasks.

It provides a template for elements that need to be included in the technical documentation

It guides the Developers in creating a forecast at the Sprint Planning

It identifies bottlenecks and optimizes team members utilization.

It creates transparency regarding progress within the Scrum Team

It guarantees that the increment presented at the Sprint Review is ready for deployment

11 / 80

During a Sprint Retrospective, what happens to the improvement items identified?

The most important improvement item must be taken to the next Sprint

The Scrum Master decides what happens to the improvement items identified

The Product Owner decides what happens to the improvement items identified

The Scrum Team may choose improvements for the next Sprint

13 / 80

Which three statements about Scrum are true? (choose the best three answers)

Scrum is based on empirical process control theory

Scrum is a framework for developing and sustaining complex products

Scrum is a methodology, where you can pick and choose which parts of Scrum you think will work for your environment

Scrum is like traditional processes but with self-organization to replace Project managers

Each component of Scrum serves a specific purpose, and is essential to Scrum's success and your usage of Scrum to develop complex products

14 / 80

What should a Scrum Master focus on that would probably help the newly formed Scrum Team get started? (choose the best two answers)

Ask the Product Owner to discuss the product outcome, product goal and context of product delivery

Have managers define roles and responsibilities ofeach member

Introduce incentives and escalation system for the team members

Ensure the Scrum Team understands Scrum and a Definition of Done

Ensure each member has all the skill required for product development

15 / 80

Who manages and make changes to the Product Backlog during a Sprint?

The Product Owner

The stakeholders

The Developers

The Scrum Team

The Scrum Master

16 / 80

What should Developers do in case a Product Owner is not available for Scrum events and not supportive enough for Developers?

Ask Scrum Master to coach the Product Owner on their role

Talk to sponsor, so they get a written commitment for availability from Product Owner

Cancel the sprint

Take product related decisions on behalf of the Product Owner

17 / 80

Who is responsible for ensuring that the work done on a Product Backlog Item meets the Definition of Done?

The Product Owner

The Test Team

The Developers

The Scrum Team

The Scrum Master

18 / 80

A team is considered cross-functional when:

The members can effectively multi-task on multiple Product Backlog items at the same time

The members consist of programmers, testers, business analysts, and devops engineers

The members have all the skills necessary to create value each Sprint

A group of full-stack developers shared across multiple Scrum teams

19 / 80

Who manages and updates the Sprint Backlog during a Sprint?

The Product Owner

The Project Manager

The Developers

The Scrum Team

The Scrum Master

20 / 80

A Product Owner new to the organization enquires on agenda for Sprint 0. As a Scrum Master, how will you respond?

The Scrum Guide does not define Sprint 0 and that in every Sprint, a useful and valuable Increment is produced

A Sprint 0 is used by Product Owner to refine enough Product Backlog items to fill the first 3 Sprints

A Sprint 0 is used by Lined Manager to determine the composition of the Scrum Teams so they have the capacity to deliver the completed forecast

A Sprint 0 is used by Project Manager to come up with a detailed project plan for Scrum Team to commit date, budget and scope to the stakeholders.

21 / 80

How can we identify a Scrum Team to be cross-functional?

When they are drawn from separate teams of business analysts, architects, developers and testers

When they include cross-skilled individuals who take end-to-end accountability of creating an increment of product and hence create value

When developers work closely with business analysts, architects, developers and testers who are not part of the Scrum Team

When they have a right mix of developers, business analysts, architects, developers and testers

22 / 80

Who is accountable to ensure that the Sprint Planning meeting attendees are prepared to discuss the most important Product Backlog items and how they map to the Product Goal?

The Developers

The Product Owner

The stakeholders

The Scrum Master

The organizational CEO

The Scrum Team

23 / 80

When must an increment be available, as per the Scrum Guide?

Every alternative Sprint

At the end of every Sprint at least

The Scrum Guide does not specify the timeline

After all the testing is complete Before the release Sprint

24 / 80

Who are the attendees of a Sprint Review?

The Scrum Team only

The stakeholders and Product Owner

The stakeholders and Scrum Team

The Developers and Project Manager

25 / 80

As a Scrum Master, how will you divide a group of 100 people into Scrum Teams?

Managers assign people to new teams and rotate every Sprint to spread knowledge

Help the Scrum Team in understanding the product, the product vision and the rules of the Scrum framework, and let them self-organize into Scrum Teams

Hiring Manager and Line Managers allocate people into different teams to optimize utilization

Scrum Master creates a matrix of skills, seniority, and level of experience to assign people to teams

26 / 80

What should be done with a Product Backlog item which is not done by the end of the Sprint?

It can be added to the Increment if the customer accepts it.

It is not include it in the Increment.

It can be added to the Increment if the user acceptance tests are done.

Demonstrate it in the Sprint Review meeting, if the item is presentable in its current state.

27 / 80

A Developer identifies a potential data security risk and informs the Scrum Master. What action should the Scrum Master recommend?

Wait until the Sprint Retrospective to update the Definition of Done

Notify the data security team to handle it in a separate Sprint

Ask the Developer to share the issue with the Scrum Team at the earliest

Add a Product Backlog item to address the security issue

28 / 80

29 / 80

If five new Scrum Teams were to work on one product, which of the statements are valid?

There should be five Product Owners, one for each Scrum Team

The product has one Product Backlog and one Product Owner

There should be five Product Backlogs and five Product Owners

There should be five Product Backlogs and one Product Owner to manage them

30 / 80

Who is accountable for creating the valuable, useful increment every Sprint?

The Scrum Master

The Scrum Team

The Product Owner

The Developers

31 / 80

During the Sprint (choose the best three answers)

Quality does not decrease

Scope doesn't change

The Scrum Master may choose to change the scope

The Product Backlog is refined as needed

No changes are made that would endanger the Sprint Goal

32 / 80

When might a Sprint be abnormally terminated?

When the Sprint Goal cannot be achieved

When the Developers cannot complete all items from Sprint Backlog

When the Sprint Goal becomes obsolete

When the Scrum Team experiences a lot of changes in Sprint Backlog

33 / 80

What is the primary responsibility of a Scrum Master? (select all that is applicable)

Ensure the Scrum events are kept within the timebox

Coach the team members on self-management and cross-functionality

Ensure developers are delivering everything committed in the Sprint Backlog

Ensure Product Owners is available full time with developers

Ensure inspection and adaption is happening as needed or requested

34 / 80

"Hardening" Sprint is meant to remove all technical debt and prepare the Product for upcoming release.

False

True

35 / 80

The Product Owner is having difficulties managing the Product Backlog. How can a Scrum Mater help the PO in this case?

Delay start of the Sprint until the Product Owner prioritizes the Product Backlog

Delegate the work to the Business Analyst within the Scrum Team

Coach the Product Owner in understanding that the goal of ordering the Product Backlog is to maximize the flow of value

Encourage the Product Owner to work with the Developers to see which items technically are fastest to implement

36 / 80

Who attends Daily Scrum?

The entire Scrum Team

Developers and Product Owner

Developers and Scrum Master

Developers only

The Scrum Team and anyone interested

37 / 80

What are the consequences if the frequency of Daily Scrum is reduced from daily to every third day (choose the best two answers)

Opportunities to inspect and adapt the Sprint Backlog are lost

The Scrum Master loses the ability to update Sprint status report property

Impediments are raised and resolved more slowly

The Product Owner cannot accurately report progress to the stakeholders

Too much work is spent updating the Scrum board before the meeting

38 / 80

What is the timebox for the Daily Scrum meeting?

As long as the objective of the event is met

Timeboxed to a maximum of 15 minutes, irrespective of the Sprint duration

Timeboxed to a maximum of 15 minutes for one-month Sprint, and is usually shorter for shorter Sprints

Depends on the size of Scrum Team and progress to be discussed

39 / 80

What is the timebox for the Sprint Planning meeting?

As along as the objective of the event is met

Timeboxed to a maximum of 4 hours for one-month Sprint, and is usually shorter for shorter Sprints

Timeboxed to a maximum of 8 hours for one-month Sprint, and is usually shorter for shorter Sprints

Depends on the size of Sprint Backlog and Sprint Goal formation

40 / 80

The Sprint Retrospective is an opportunity for the Scrum Team to discuss: (Select all that is applicable.)

Methods of communication

Its Definition of Done

Refine the Product Backlog

Skills needed to improve the Developers' ability to deliver

Sprint Backlog for the next Sprint

41 / 80

What is the timebox for the Sprint Review meeting?

As along as the objective of the event is met

Timeboxed to a maximum of 4 hours for one-month Sprint, and is usually shorter for shorter Sprints

Timeboxed to a maximum of 3 hours for one-month Sprint, and is usually shorter for shorter Sprints

Depends on the size of Sprint Backlog and Increment to be presented

42 / 80

In the middle of Sprint, Developers realize they don't have the tools and infrastructure to completely finish each selected Product Backlog Item? What should a Scrum Master do? (choose the best two answers)

Suggest Developers to focus on creating required infrastructure instead of delivering an increment

Coach the Scrum Team members to improve its skills, tools and infrastructure over time and adjust the Definition of Done accordingly

Request the Product Owner to accept partially done increments until the infrastructure is available

Actively do nothing

Have the Scrum Team establish a Definition of Done that is actually possible to achieve given current circumstances

43 / 80

Who is responsible for starting the Daily Scrum?

The Product Owner

The Scrum Master

Anyone whom the Scrum Master nominates

Anyone that the developers mutually decide upon

44 / 80

When is it most appropriate for Scrum Team to update the Definition of "Done"?

During Sprint Planning

During Daily Scrum

During Sprint Review

During the Sprint Retrospective

45 / 80

What factors should a Product Owner consider while ordering the Product Backlog? (select 2 answers)

Whatever maximizes the value of the Product

Lowest effort items at the top and greatest effort items at the bottom

The most valuable items should be at the top of the Product Backlog

Whichever Developers are easiest to implement

The least valuable and least refined items should be at the top

46 / 80

What sizing technique does a Scrum Master recommend to the Product Owner?

Product Backlog items must always be estimated in story points

Sizing of Product Backlog items are made by the Developers

Estimates are made by the Product Owner based on value of Product Backlog item

In Scrum, there is no need to size a Product Backlog item

47 / 80

When multiple Scrum Teams are working on the same Product, how should they select the Product Backlog Items within a Sprint?

Each Scrum Team would select an equal number of items

The Product Owner will present the Product Backlog and the Developers will select the items they will work on

The Product Owner assigns the work to each team

The Scrum Master assigns the work to each team

Each Scrum Team creates a separate Product Backlog for themselves

48 / 80

Product Owner can delegate some of their responsibilities to others. Which of the following the Product Owner cannot delegate to others? (choose the best two answers)l

Attending the Sprint Retrospective

Ordering the Product Backlog

Developing and communicating the Product Goal

Attending the Sprint Review

49 / 80

What should the Scrum Master suggest to a developer who identifies data security Issues within the product?

Ask the developer to raise this with Information Security Office

Ask the developer to share the issue with the rest of the Scrum Team as soon as possible

Create a Product backlog item for the security issue

Add issue to the Definition of Done

Delay further development and deployment until the issue is fixed

50 / 80

What is the timebox for the Sprint Retrospective meeting?

As along as the objective of the event is met

Timeboxed to a maximum of 4 hours for one-month Sprint, and is usually shorter for shorter Sprints

Timeboxed to a maximum of 3 hours for one-month Sprint, and is usually shorter for shorter Sprints

Depends on the size of Scrum Team and improvements items to be discussed

51 / 80

What is the primary responsibility of the Scrum Master during the Daily Scrum?

To ensure Developers provide their status update

To ensure Daily Scrum is happening effectively within the timebox

To take inputs required to prepare a status report for stakeholders

All the above

52 / 80

What happens if the forecasted items are not completed by the end of the Sprint?

The Sprint length holds and the Developers continuously learn what is actually possible to do within a sprint of this length.

The Sprint length is extended temporarily to complete the remaining work.

The Sprint length is extended and future Sprints use this new duration

53 / 80

What does it mean when an event is considered timeboxed?

An event should take a minimum set time

An event that must happen by a specific time

An event cannot take more than a maximum amount of time

An event should start at a specific time

54 / 80

What activities would a Scrum Team perform in between the end of the current Sprint and the start of the next Sprint?

Conduct Sprint Planning for the upcoming Sprint Planning

Refine the Product Backlog and update the stakeholders with the upcoming Sprint work

There is no gap between the two Sprint. The next Sprint starts immediately after the current Sprint

Work with the testing and deployment team to release the increment created in the past Sprint

55 / 80

Developers are unsure how much of the Sprint Backlog be defined during the Sprint Planning meeting. What advise will you give as a Scrum Master?

Enough so the Developers can create its best forecast of what it can do, and to start the first several days of the Sprint

Sprint Backlog should be defined to complete detail so that there are no surprises Just enough tasks for the Scrum Master to be confident in the Developers' understanding of the Sprint

The entire Sprint backlog must be identified and estimated by the end of the Sprint planning meeting

Just enough to understand design and architectural implications.

56 / 80

What is the outcome of the Sprint Retrospective?

A revised Sprint Goal

A revised Sprint Backlog

A new increment ready to be released

A revised Definition of Done

A revised Product Backlog

57 / 80

When does a Product Owner participate in the Daily Scrum?

When they need an update on how the Sprint is progressing

When the Product Owner is actively working on items in the Sprint Backlog, they participate as Developers

When the Scrum Master is unavailable

Product Owner is from client side and needs transparency on progress of Sprint work

58 / 80

When is the initial Sprint Backlog formed?

Prior to the Sprint Planning meeting

During the Sprint Planning meeting

At the beginning of the project

Anytime during current sprint

59 / 80

When does the Sprint get over? (choose the best two answers)

When the timebox of the Sprint is over

When the developers have completed all the items committed during Sprint Planning

When the Sprint Retrospective is over

When the Product Owner has accepted all items worked during the Sprint

When the entire Scrum Team collectively agree

60 / 80

During one of the Sprint Reviews, a stakeholder was upset with the quality and cost of the Product being built? What could be the possible reason for this?

The stakeholder has not been attending the Daily Scrum. The Product Owner has not updated regular status report for the stakeholders

The Product Owner has not made the stakeholders aware of the progress of the project. The stakeholders have not been attending the Sprint Reviews.

The Scrum Master has not been reporting on the progress of the Scrum Team. The Product Owner has not been managing the Developers' tasks effectively. The Developers have not been improving their velocity.

The Scrum Master should not invite the stakeholder for future Sprint Reviews.

61 / 80

When does the Sprint Retrospective occur?

After every alternative Sprint

After the Sprint Planning and prior to the Sprint Review

After the Sprint Review and prior to the next Sprint Planning

When the Stakeholders ask for it

When the Scrum Team requires

62 / 80

How much work must Developers do to a Product Backlog item selected for a Sprint?

All coding work and at some testing to be taken to next Sprint

As much as they can complete within the Sprint timebox

As much to conformance with the Definition of Done

As much as they have skill in working on the item

63 / 80

What are two responsibilities of testers in a Scrum Team? (choose the best two answers)

Each Developer is accountable for quality as a professional

Tracking quality metrics

Finding bugs

Scrum has no "tester" role

Verifying the work of programmers

64 / 80

What should the Scrum Master do during the Daily Scrum?

Gather status update from developers and report to senior management

Lead the Daily Scrum bygetting status updates from each Developer

The Scrum Master does not need to attend the Daily Scrum, they only has to ensure the Developers have an effective Daily Scrum

Ensure all developers answer the three questions

Make changes to the Sprint Backlog and update the burndown chart

65 / 80

What should a Scrum Master do when Developers have decided that a Scrum Retrospective is unnecessary?

Comply with the decision of the self-managing Scrum team

Call a meeting between the Scrum Team and senior management

Consult with the Agile Coach to see how he/she feels about the situation

Begin facilitating productive and useful Scrum Retrospectives

66 / 80

Why does a Daily Scrum take place at the same time and place?

The Scrum Guide mandates Daily Scrum to take place at the same time and place

Rooms are hard to book and this lets it be booked in advance

The consistency reduces complexity

67 / 80

How much of the Sprint Backlog must be defined during the Sprint Planning meeting?

Enough so the Developers can create its best forecast of what it can do, and to start the first several days of the Sprint

Just enough tasks for the Scrum Master to be confident in the Developers' understanding of the Sprint

The entire Sprint backlog must be identified and estimated by the end of the Sprint planning meeting

Just enough to understand design and architectural implications.

68 / 80

Who conforms to the Definition of Done?

The Developers

The Scrum Team

The Product Owner

The Scrum Master

69 / 80

What is presented in a Sprint Review?

The sum of all the Product Backlog items completed during the Sprint and the value of the increments of all previous Sprints

All the documents, piece of code and test cases produced during the current Sprint

All Sprint Backlog items, including "Done" and not completed, during the Sprint

Whatever Product Owner deem necessary

70 / 80

How often should the Scrum Team membership change?

As needed while taking into account a short-term reduction in productivity

Never, because it reduces productivity

Every Sprint to promote shared learning

As needed, with no special allowance for changes in productivity

71 / 80

What is inspected in the Sprint Review? (select all that is applicable)

Product Backlog

Definition of Done

Increment

Sprint Backlog

Progress toward the Sprint Goal

72 / 80

What does a Burn-down Chart show?

Hierarchy of tasks that comprise a project

How much work remains till the end of the Sprint

The evolution of the amount of uncertainty during a project

Dependencies, start times and stop times for project tasks

73 / 80

74 / 80

Who has the best visibility on progress of work toward the Sprint Goal?

The Product Owner

The Scrum Master

The Developers

The Stakeholders

The Scrum Team

75 / 80

Which statement best describes Scrum?

A clearly defined and predictable process that follows the principles of Computer Science.

A framework to address complex products in complex environments.

A clearly defined methodology that defines the product development process.

A manual for defining best practices for product development.

76 / 80

What does it mean when an event is considered timeboxed?

An event should take a minimum set time

An event that must happen by a specific time

An event cannot take more than a maximum amount of time

An event should start at a specific time

78 / 80

Within a few days of starting the Sprint, Developers realize they have selected too much work. What is the most appropriate action that a Scrum Master recommend?

Suggest to modify the Definition of Done to ensure all Product Backlog items can be done by the end of the Sprint.

Ask Developers to work with the Product Owner to remove some items from the Sprint Backlog as soon as possible.

Hire additional team members to handle the extra work.

Ask Developers to continue working and update the Product Owner at the Sprint Review.

79 / 80

How much of the Sprint Backlog must be defined during the Sprint Planning meeting?

The entire Sprint Backlog must be defined by the end of the Sprint Planning meeting

Enough so the Developers can create its best forecast of what they can achieve in a Sprint, and to start the first few days of the Sprint

Just enough for the Product Owner to be confident in the Developers' achieving the Sprint Goal

Just enough to provide the commitment to stakeholders

80 / 80

The Scrum Master is accountable for the effectiveness of the Scrum Team. What two ways can a Scrum Master make a Scrum Team effective? (choose the best two answers)

By keeping high value features at the top of the Product Backlog

By preventing changes to the Sprint Backlog once the Sprint begins

By causing the removal of impediments to the Scrum Team's progress

By coaching the Scrum Team in self-management and cross-functionality

Adding or removing developers based on their individual productivity

NameEmailPhone Number

Your score is

Exit

Our Courses

Our Courses

Enroll Now

Enroll Now

₹2,000 Cash Reward

₹2,000 Cash Reward

Enroll Now

Enroll Now

Diwali Offer!

Register Now

Webinars

Scrum Master Job Interview

Fill in the Form

Webinars

Scrum Master Interview Secrets: Decoding the Interviewer’s Mind

Enroll Now

Request a Call-back

Enroll Now