[Jan-9th 2021] Updated Professional Scrum Master I PSM I Exam Questions (158 Q&As)

New Professional Scrum Master I PSM I Exam Questions are updated from PassQuestion! You can download the newest PassQuestion Professional Scrum Master I PSM I Questions and Answers: https://www.passquestion.com/psm-i.html (158 Q&As)

Practice Online Professional Scrum Master I PSM I Free Questions

1. When many Scrum Teams are working on the same product, should all of their increments be integrated every Sprint?

Yes, but only for Scrum Teams whose work has dependencies.

Yes, otherwise the Product Owners (and stakeholders) may not be able to accurately inspect what is done.

No, each Scrum Team stands alone.

No, that is far too hard and must be done in a hardening Sprint.

2. When can a Development Team cancel a Sprint?

It can’t. Only Product Owners can cancel Sprints.

When functional expectations are not well understood.

When the Product Owner is absent too often.

When the selected Product Backlog items for the Sprint become unachievable.

When a technical dependency cannot be resolved.

3. Which output from Sprint Planning provides the Development Team with a target and overarching direction for the Sprint?

The Sprint Backlog.

The Sprint Goal

The release plan.

Sprint Review minutes.

4. How should a Development Team deal with non-functional requirements?

Ensure every Increment meets them.

Make sure the release department understands these requirements, but it is not the Development Team’s responsibility.

Handle them during the Integration Sprint preceding the Release Sprint.

Assign them to the lead developers on the team.

5. When is a Sprint over?

When the Product Owner says it is done.

When all Product Backlog items meet their definition of “Done”.

When all the tasks are completed.

When the time-box expires.

6. Scrum has a role called “Project Manager”.

True

False

7. What are two good ways for the Development Team to make non-functional requirements visible? (Choose two.)

Put them on a separate list on the Scrum board, available for all to see.

Add them to the Product Backlog and keep the Product Owner posted on the expected effort.

Run the integration and regression tests before the end of the Sprint, and capture the open work for the Sprint Backlog of the next Sprint.

Add them to the definition of “Done” so the work is taken care of every Sprint.

8. How much time is required after a Sprint to prepare for the next Sprint?

The break between Sprints is time-boxed to 1 week for 30 day Sprints, and usually less for shorter sprints.

Enough time for the requirements for the next Sprint to be determined and documented.

Enough time for the Development team to finish the testing from the last Sprint.

None. A new Sprint starts immediately following the end of the previous Sprint.

All of the above are allowed depending on the situation.

9. In the Sprint Planning meeting, the Product Owner and the Development Team were unable to reach a clear understanding about the highest order Product Backlog items. Because of this, the Development Team couldn’t figure out how many Product Backlog items it could forecast for the upcoming Sprint. They were able to agree on a Sprint Goal, however.

Which of the following two actions should the Scrum Master support? (Choose two.)

Cancel the Sprint. Send the entire team to an advanced Scrum training and then start a new Sprint.

Forecast the most likely Product Backlog items to meet the goal and create a Sprint Backlog based on a likely initial design and plan. Once the time-box for the Sprint Planning meeting is over, start the Sprint and continue to analyze, decompose, and create additional functionality during the Sprint.

Continue the Sprint Planning meeting past its time-box until an adequate number of Product Backlog items are well enough understood for the Development Team to make a complete forecast. Then start the Sprint.

Discuss in the upcoming Sprint Retrospective why this happened and what changes will make it less likely to recur.

Ask everyone to take as much time as needed to analyze the Product Backlog first, and then reconvene another Sprint Planning meeting.

10. Which answer best describes the topics covered in Sprint Planning?

What to do and who will do it.

How conditions have changed and how the Product Backlog should evolve.

What can be done and how to do it.

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

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

11. Which of the following is required by Scrum? (Choose all that apply.)

Sprint Retrospective.

Members must be stand up at the Daily Scrum.

Sprint Burndown Chart.

Release planning.

All of the above.

12. What is the purpose of a Sprint Review?

To take time to judge the validity of the project.

To inspect the product increment with the stakeholders and collect feedback on next steps.

To review the Scrum Team’s activities and processes during the Sprint.

To build team sprint.

13. Who determines when it is appropriate to update the Sprint Backlog during a Sprint?

The Project Manager.

The Development Team.

The Scrum Team.

The Product Owner.

14. Who must attend the Daily Scrum?

The Scrum Master and Product Owner.

The Development Team.

The Development Team and Product Owner.

The Scrum Team.

The Development Team and Scrum Master.

15. When do Development Team members take ownership of a Sprint Backlog item?

At the Sprint planning meeting.

During the Daily Scrum.

Never. All Sprint Backlog Items are “owned” by the entire Development Team, even though each one may be done by an individual Development Team member.

Whenever a team member can accommodate more work.

16. The purpose of a Sprint is to produce a done Increment of product.

True

False

17. Who creates the definition of “Done”?

The Scrum Master as he/she is responsible for the Development Team’s productivity.

The Scrum Team, in a collaborative effort where the result is the common denominator of all members’ definition.

The Product Owner as he/she is responsible for the product’s success.

The development organization (or Development Team if none is available from the development organization).

18. Five new Scrum Teams have been created to build one product. A few of the developers on one of the Development Teams ask the Scrum Master how to coordinate their work with the order teams.

What should the Scrum Master do?

Teach the Product Owner to work with the lead developers on ordering Product Backlog in a way to avoid too much technical and development overlap during a Sprint.

Teach them that it is their responsibility to work with the other teams to create an integrated Increment.

Collect the Sprint tasks from the teams at the end of their Sprint Planning and merge that into a consolidated plan for the entire Sprint.

Visit the five teams each day to inspect that their Sprint Backlogs are aligned.

19. Which two things should the Development Team do during the first Sprint? (Choose two.)

Make up a plan for the rest of the project.

Analyze, describe, and document the requirements for the subsequent Sprints.

Develop at least one piece of functionality.

Analyze, design, and describe the complete architecture and infrastructure.

Create an increment of potentially releasable software.

20. What are three ways Scrum promotes self-organization? (Choose three.)

By not allowing documentation.

By the Development Team deciding what work to do in a Sprint.

By preventing stakeholders from entering the development room.

By removing titles for Development Team members.

By being a lightweight framework.

21. What is the key concern when multiple Development Teams are working from the same Product Backlog?

Minimizing dependencies between teams.

Clear definition of requirements.

Meeting original scope projections.

Making sure there’s enough work for everyone on every team.

Maximizing velocity.

22. What does it mean to say that an event has a time-box?

The event must happen at a set time.

The event must happen by a given time.

The event must take at least a minimum amount of time.

The event can take no more than a maximum amount of time.

23. Which outcome is expected as Scrum Teams mature?

They will improve their definition of “Done” to include more stringent criteria.

The Sprint Retrospectives will grow to be longer than 4 hours.

There is no need for a time-boxed Sprint, since time-boxes are only for new Scrum Teams.

Sprint Reviews will no longer be needed.

A Scrum Master is no longer needed since they are a mature team now.

24. The Product Owner must release each Increment to production.

When it makes sense.

To make sure the Development Team is done every Sprint.

Whenever the product is free of defects.

Without exception.

25. A properly functioning Scrum Team will have at least one Release Sprint and may well have several.

True

False

26. Scrum is a methodology that tells in detail how to build software incrementally.

True

False

27. For which is the Scrum Master responsible?

Managing the performance of the Scrum Team.

The meetings and the objectives that a Scrum Team sets for itself.

The Scrum framework being adopted and used properly.

Keeping track of resource allocation.

28. A Development Team asks their Product Owner to re-order the Product Backlog. The team is waiting for an external supplier to deliver a specific software component. Without that component there won’t be enough work in the next Sprint to occupy the full team. The Product Owner asks the Scrum Master for help.

What would be good advice to give the Product Owner?

Remind the Product Owner that his primary concern is the flow of value reflected in the ordering of the Product Backlog.

Tell the Product Owner to re-order the Product Backlog so the work involving the external component can be planned in a separate sprint.

Tell the Product Owner that the Product Backlog should be ordered to maximize utilization of the Development Team.

29. As the Sprint Planning meeting progresses, the Development Team sees that the workload is greater than they can handle.

Which two are valid actions? (Choose two.)

Recruit additional Development Team members before the work can begin.

The Development Team ensures that the Product Owner is aware, starts the Sprint, and monitors progress.

Cancel the Sprint.

Remove or change selected Product Backlog items.

The Development Team works overtime during this Sprint.

30. Currently, your Development Teams are organized to address a single layer only (for example, front end, middle tier, back end, and interfaces).

What are three things to consider when deciding to move away from such component teams toward feature teams? (Choose three.)

You cannot do Scrum without feature teams.

Productivity may suffer when making this kind of move.

Getting support from the business side first helps.

Feature teams have less communication overhead.

With feature teams, it is easier to calculate the productivity per team.

31. During a Sprint, when is new work or further decomposition of work added to the Sprint Backlog?

When the Product Owner identifies new work.

As soon as possible after they are identified.

When the Scrum Master has time to enter them.

During the Daily Scrum after the Development Team approves them.

32. What it the main reason for the Scrum Master to be at the Daily Scrum?

To gather status and progress information to report to management.

To write down any changes to the Sprint Backlog, including adding new items, and tracking progress on the burn-down.

He or she does not have to be there; he or she only has to ensure the Development Team has a Daily Scrum.

To make sure every team member answers the three questions.

33. You have six teams using a traditional method to deliver a product. Your management has asked you to start using Scrum. In the initial project there were separate plans and teams for the layers of a software system, i.e. one for the front-end, one for the middle tier, one for the back-end, and one for the interfaces and services. This resembles what is known as component teams. But you have read that it’s a good idea to have teams organized by feature.

What are the advantages of keeping component teams while starting Scrum?

There’s less initial disruption than organizing into new teams. As they start, they will discover what works best, and how to potentially re-organize towards this.

Component teams generally have the skills needed to create a working Increment of software that provides business value.

Because they have worked together for some time, they are likely able to start producing shippable Increments faster that new feature teams would.

There are fewer cross-team dependencies than working in feature teams.

34. How should Product Backlog items be chosen when multiple Scrum Teams work from the same Product Backlog?

The Scrum Team with the highest velocity pulls Product Backlog items first.

The Development Teams pull in work in agreement with the Product Owner.

The Product Owner should provide each team with its own Product Backlog.

Each Scrum Team takes an equal numbers of items.

The Product Owner decides.

35. How often should Development Team membership change?

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

Never, because it reduces productivity.

As needed, with no special allowance for changes in productivity.

Every Sprint to promote shared learning.

36. Who should make sure everyone on the Development Team does his or her tasks for the Sprint?

The Project Manager.

The Product Owner.

The Scrum Master.

The Development Team.

All of the above.

37. When is it most appropriate for a Development Team to change the definition of “Done”?

During Spring Planning.

Prior to starting a new Sprint.

During the Sprint Retrospective.

Prior to starting a new project.

38. The Daily Scrum is an event that happens every day.

What would be three key concerns if the frequency were to be lowered to every two or three days? (Choose three.)

A The Scrum Master loses the ability to update the Gantt Chart properly.

B The Sprint Plan may become inaccurate.

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

D The Product Owner cannot accurately report progress to the stakeholders.

E Impediments are raised and resolved more slowly.

F Opportunities to inspect and adapt the Sprint Backlog are lost.

39. Which statement best describes Scrum?

A defined and predictive process that confirms to the principles of Scientific Management.

A complete methodology that defines how to develop software.

A cookbook that defines best practices for software development.

A framework within which complex products in complex environments are developed.

40. Which Scrum Values are exhibited by not building Product Backlog items that have low business value? (Choose three.)

Economic Value Added.

Respect.

Focus.

Earned Value.

Courage.

41. Who creates a Product Backlog Item’s estimate?

The Development Team after clarifying requirements with the Product Owner.

The Product Owner with input from the Development Team.

The most senior people in the organization, including architects and subject matter experts.

The Scrum Master.

The Development Team, alone.

42. Who starts the Daily Scrum?

The person coming in last. This encourages people to be on time and helps to stay within the time-box.

Whoever the Development Team decides should start.

The person who has the token.

The Scrum Master. This ensures that the Development Team has the meeting and stays within the time-box.

The person who last broke the build.

43. You are the Scrum Master on a newly formed Scrum Team.

Which three of the following activities would probably help the team in starting up? (Choose three.)

Introduce a bonus system for the top performers in the team.

Have the Scrum Team members introduce themselves to each other and give a brief background of their skills and work history.

Have the development managers for each Development Team member introduce their direct reports and go over their responsibilities on the Scrum Team.

Ensure the Scrum Team members have compatible personalities.

Ensure the team understands they need a definition of “Done”.

Ask the Product Owner to discuss the product or project, its history, goals, and context, as well as answer questions.

44. A Development Team selects a set of Product Backlog items for a Sprint Backlog with the intent to get the selected items “Done” by the end of the Sprint.

Which three phrases best describe the purpose of a definition of “Done”? (Choose three.)

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 creates transparency over the work inspected at the Sprint Review.

It trucks the percent completeness of a Product Backlog item.

It guides the Development Team is creating a forecast at the Sprint Planning.

It defines what it takes for an Increment to be ready for release.

45. Select two ways in which technical debt impacts transparency. (Choose two.)

When calculated and estimated, the total amount of technical debt shows exactly how long until the Product Owner can release the Increment.

It leads to false assumptions about the current state of the system, specifically of an Increment being releasable at the end of a Sprint.

As development progresses and code is added, the system becomes more difficult to stabilize, which results in future work being slowed down in unpredictable ways.

It enhances transparency for the Product Owner as a Development Team is not allowed to do additional feature development in a Sprint as long as there is technical debt.

46. Which of these may a Development Team deliver at the end of a Sprint?

Failing unit tests, to identify acceptance tests for the next Sprint.

An increment of software with minor known bugs in it.

An increment of working software that is “done”.

A single document, if that is what the Scrum Master asked for.

47. How much of the Sprint Backlog must be defined during the Sprint Planning event?

Just enough tasks for the Scrum Master to be confident in the Development Team’s understanding of the Sprint.

The entire Sprint Backlog must be identified and estimated by the end of the Sprint Planning meeting.

Enough so the Development Team can create its best forecast of what is can do, and to start the first several days of the Sprint.

Just enough to understand design and architectural implications.

48. Who is responsible for managing the progress of work during a Sprint?

The Scrum Master.

The Development Team.

The Product Owner.

The most junior member of the Team.

49. A Development Team is required to deliver a done Increment by the end of a Sprint. Select two statements that explain what “Done” means. (Choose two.)

All work the Development Team is willing to do.

Ready for integration.

No work left from the definition of “Done”.

Whatever the Product Owner defines as quality.

All work to create software that is ready to be released to end users.

50. What two factors are best considered when establishing the Sprint length? (Choose two.)

The organization has mandated similar length sprints.

The level of uncertainty over the technology to be used.

The frequency at which team formation can be changed.

The risk of being disconnected from the stakeholders.

51. Which of the following are true about the length of the Sprint? (Choose two.)

The length of the Sprint should be proportional to the work that is done in between Sprints.

It is best to have Sprints of consistent length throughout a development effort.

Sprint length is determined during Sprint Planning, and should hold the time it will take to code the planned features in the upcoming Sprint, but does not include time for any testing.

Sprint length is determined during Sprint Planning, and should be long enough to make sure the Development Team can deliver what is to be accomplished in the upcoming Sprint.

All Sprints must be 1 month or less.

52. What are two responsibilities of testers in a Development Team? (Choose two.)

Verifying the work of programmers.

Everyone in the Development Team is responsible for quality.

Tracking quality metrics.

Finding bugs.

Scrum has no “tester” role.

53. The CEO asks the Development Team to add a “very important” item to a Sprint that is in progress.

What should the Development Team do?

Add the item to the current Sprint and drop an item of equal size.

Add the item to the current Sprint without any adjustments.

Inform the Product Owner so he/she can work with the CE

Add the item to the next Sprint.

54. What is the role of management in Scrum?

To facilitate the Scrum Teams with insights and resources that help them improve.

To monitor the Development Team’s productivity.

To identify and remove people that aren’t working hard enough.

To continually monitor staffing levels of the Development Team.

55. Which technique is the best way the Scrum Master can ensure that the Development Team communicates effectively with the Product Owner?

Monitor communications between them and facilitate direct collaboration.

Teach the Development Team to talk in terms of business needs and objectives.

Teach the Product Owner about the technologies employed during the Sprints.

Act as a go-between for them.

56. The time-box for a Daily Scrum?

Two minutes per person.

15 minutes.

15 minutes for a 4 week sprint. For shorter Sprints it is usually shorter.

4 hours.

The same time of day every day.

57. Which phrase best describes a Product Owner?

Go-between development team and customers.

Value optimizer.

Requirements engineer.

Team manager.

58. The length of a Sprint should be:

Short enough to keep the business risk acceptable to the Product Owner.

Short enough to be able to synchronize the development work with other business events.

No more than one calendar month.

All of these answers are correct.

59. During a Sprint Retrospective, for what is the Product Owner responsible?

Participating as a Scrum Team member.

Summarizing and reporting the discussions to the stakeholders that he/she represents in the Scrum Team.

Capturing requirements for the Product Backlog.

The Product Owner should not take part in Sprint Retrospectives.

60. Marian is the Product Owner envisioning a project for a new release of her product. She made a projection of a release date based upon a sustained velocity of 17 completed units of work per Sprint. Over the first 3 Sprints, the average velocity was 13 for work that the Development Team estimated as 90% done. The Development Teams, feeling the need to meet the plan, figured that a velocity of 17 was within their reach.

A good way to continue is:

The Development Team makes sure that all of the selected scope per Sprint is as “Done” as possible. The undone work is estimated and added to the Sprint Backlog of the next Sprint, so it doesn’t mess up the Product Backlog.

Add enough people to the Development Team for the deadline to be made.

The opportunity to inspect and adapt is lost. Opaqueness has replaced transparency. Predictability has dropped below zero. The produced software is not usable. As the rules of Scrum have not been respected, it is the Scrum Master’s duty to assess whether repair is possible, or a restart with a more reliable team. If not, the Scrum Master should cancel the project.

The Development Team should remind Marian to find funding for enough Release Sprints in which the remaining work can be done.

Question 1 of 60

[Jan-9th 2021] Updated Professional Scrum Master I PSM I Exam Questions (158 Q&As)

Practice Online Professional Scrum Master I PSM I Free Questions

Leave a Reply Cancel reply