PSM-II Exam Dumps Pass with Updated 2024 Certified Exam Questions [Q17-Q38] – IT Certification Exam Questions & Answers

Rate this post

PSM-II Exam Dumps Pass with Updated 2024 Certified Exam Questions

PSM-II Exam Questions – Real & Updated Questions PDF

The PSM II exam covers a wide range of topics, including facilitation techniques, coaching and mentoring, conflict resolution, and team dynamics. It also focuses on the role of the Scrum Master in scaling Scrum, working with stakeholders, and ensuring the team’s continuous improvement. Passing the PSM II exam is a significant achievement and demonstrates a Scrum Master’s ability to lead and guide a Scrum team in complex and challenging situations.

Q17. Steven is a Scrum Master of a Scrum Team that is new to Scrum. At the halfway point of the Sprint, the Product Owner comes to Steven telling him that he is concerned the Development Team will not be able to complete the entire Sprint Backlog by the end of the Sprint.
What should Steven do in this situation?

Motivate the Development Team to meet their commitment to the Product Owner.

Coach the Product Owner that with complex software development, you cannot promise the entire scope that was forecast during Sprint Planning. As more is learned during the Sprint, work may emerge that affects the Sprint Backlog.

Advise the Product Owner that the Development Team owns the Sprint Backlog and it is up to them to meet their commitments. No one tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality.

Add more people to the Development Team to meet the Product Owner’s expectations.

Q18. When does a Sprint end?

When there is no work remaining in the Sprint Backlog.

When the time-box expires.

It depends on the Product Owner.

Immediately after the conclusion of the Sprint Review.

Q19. Who must ensure that the work done for a Product Backlog item conforms to the Definition of “Done?”

The test team.

The Scrum Team.

The Scrum Master.

The Product Owner.

The Development Team.

Q20. Who is responsible for ensuring the Product Backlog items are understood to the level needed?

The Business Analyst.

The Scrum Master.

The Development Team.

The Product Owner.

Q21. Which four of the following risks to product development are addressed by Scrum?
(choose the best four answers)

The timescale of the planned work.

The stability and complexity of the technology.

The complexity and unpredictability of the requirements.

The skills and working relationships of the people on the teams.

The definition of incentive and bonus strategies by Human Resources for all team members.

The clear definitions of stages and gateways in the overall governance model.

Q22. Every Development Team should have the competencies and skills needed to deliver a Done Increment in a Sprint.

True

False

Q23. Steven is a Scrum Master for three Scrum Teams building the same product and working from the same Product Backlog. Management wants to standardize how velocity is calculated across all three teams in order to identify which teams are high performing and which teams need more support.
What would be the best two responses Steven could provide to management? (Choose two.)

There is no direct relationship between velocity and value.

Standardizing velocity across teams is a good way to understand which teams are producing the most value.

Providing incentives based on velocity can increase the Scrum Team’s motivation to produce more value.

Velocity is the amount of business functionality that a Scrum Team creates in a Sprint. It is unique to that team and used as an input to Sprint Planning.

Q24. Which role is responsible for determining when it is most appropriate to update the Sprint Backlog?

The Product Owner

The Development Team

The Scrum Team

The Scrum Master

Q25. Scrum promotes self-organization.
Which of these statements would NOT support self-organizing?

The Development Team deciding what work to do in a Sprint.

Removing the need for documentation.

Being a lightweight framework.

Removing titles for Development Team members.

Q26. Select the correct Scrum Team roles defined in Scrum.

Development Team, Scrum Master, Product Owner

Engineers, Business Analyst, Product Owner

Stakeholders, Scrum Master, Project Manager, Product Owner

Product Manager, Business Analyst, Development Team, Stakeholders

Q27. According to Scrum theory, how should a group of fifty people be divided into multiple Development Teams?

Allow the team leads to divide and select teams.

Understanding the product, the product vision and the Scrum framework, the group self-organizes into teams.

Create a skills matrix, identify role levels, and years of experience to assign people to teams.

The teams will rotate members every Sprint to spread knowledge.

Q28. A Scrum Team has been working on a product for several iterations and has an average velocity of 55 units of
‘done’ work per Sprint. A second team will be added to work on the same product.
What might be the impact on the original team?

Their velocity is likely not affected and will remain at 55.

Their velocity is likely to drop and be less than 55.

Their velocity is likely to rise and be more than 55.

Q29. During the Sprint Review the Product Owner introduces the functionality that is likely to be done over the next Sprints. The Chief Security Officer reminds everyone that through the envisioned functionality, sensitive personal user data will be stored. This might be the subject of external security audits. He reminds everyone of important non-functional requirements with regards to security. These were not applicable and not considered previously What are two effective ways the Scrum Team can manage these high-security concerns?
(choose the best two answers)

They are discussed, determined, and documented in parallel Sprints to not disturb the actual feature development Once analyzed, they should be applied to the work already done before further feature development can continue.

The impact of these security concerns on past and future work needs to be determined before new Sprints can start. A list of security-related Product Backlog items needs to be passed on to the Product Owner before starting the next Sprint

They are added to the Product Backlog and addressed throughout the next Sprints, combined with creating the business functionality in those Sprints, no matter how small that business functionality.

During the Sprint Retrospective, the Scrum Team assesses how to add these expectations to the Definition of Done so every future Increment will live up to these requirements. If needed they can work with external specialists to better understand the requirements

They should be managed by a separate specialist team in a parallel Sprint, so they can be specifically resolved through an improved application design without hindering functional development.

Q30. Which of the following affect the outcome of a Sprint?
(choose all that apply)

The complexity of the problem being solved.

The complexity of the requirements.

The skills and working relationships of the people on the Scrum Team(s).

Q31. Which of these tools is mandatory for the Product Owner to use?

Release burnup chart.

Burndown chart.

Version control.

Project Gantt chart.

None of the above.

Q32. The Scrum Master is no longer needed when teams become self-organized.

True

False

Q33. What would be the main benefits of self-organization?

Increased rule compliance, self-accountability, commitment.

Increased rule compliance, self-accountability, output.

Increased capacity, accuracy of estimates, output.

Increased creativity, self-accountability, commitment.

Q34. Which two options describe how project budgeting and financial forecasting work in Scrum?
(choose the best two answers)

Scrum does not align with traditional accounting practices. The financial department needs to be given a fixed cost per Sprint per team.

Several Sprints may be funded as a single release, with the result of each Sprint being releasable product

The only funding is for the run cost (time and materials) of the Scrum Teams, so no budgeting process is needed_

It is ideally revisited as frequently as each Sprint to ensure value is being delivered for the investment spent.

Explanation
Short Explanation: Scrum is a framework for delivering value to customers and stakeholders in an iterative and incremental way. Scrum does not prescribe how project budgeting and financial forecasting should be performed, but it does provide some principles and practices that can help with this process.
One of these principles is that each Sprint should produce a potentially releasable product Increment that delivers value and meets the Definition of Done. This means that several Sprints may be funded as a single release, with the result of each Sprint being releasable product12. This allows the Product Owner to decide when to release the product based on the feedback from the customers and stakeholders, and the market conditions.
Another principle is that Scrum promotes transparency, inspection, and adaptation. This means that the budgeting and forecasting process should be revisited as frequently as each Sprint to ensure value is being delivered for the investment spent13. This allows the Scrum Team to inspect the outcomes of the delivered Sprint Increments, compare them with the expected benefits and costs, and adapt the product backlog and the release plan accordingly.
Scrum does not align with traditional accounting practices that require fixed scope, cost, and time. However, this does not mean that Scrum Teams do not need a budgeting process or that they only need to cover the run cost (time and materials) of the Scrum Teams. Scrum Teams still need to estimate the size and value of the product backlog items, forecast the delivery date and cost of the product or release, and track the actual spending and revenue of the product or release43. The difference is that these estimates and forecasts are based on empirical data from previous Sprints, rather than on upfront assumptions or guesses. They are also subject to change as new information emerges or new requirements arise.
References:
Scrum Guide 2020, section “The Sprint”, “The Increment”, “Empiricism”.
Tips for Effective Agile Budgeting and Forecasting | Toptal, section “Establish Context and Set Expectations”, “Budget for Value”.
Project forecasts and budgets | Microsoft Learn, section “Project forecasting”.
Planning and Budgeting in Scrum Projects – PMHut, section “Budgeting in Scrum Projects”.

Q35. You are the Scrum Master of a Scrum Team that has one Developer who disagrees with team decisions. Their disagreements are becoming disruptive and slowing progress. The Developer often returns to earlier team decisions and re-opens the issue.
What are two ways to go about this problem?
(choose the best two answers)

You organize an offsite team building activity to establish a foundation of trust. You observe whether the problem persists after the offsite activity.

You take the Developer aside to express your concern over their disagreements and tell them to act as a team player and to comply with the team’s decision.

At the Sprint Retrospective you observe whether the topic is raised. If it does not happen, you check on how comfortable everybody is with the way team decisions are made.

You go to the Human Resources department and ask them to have a
conversation with the Developer based on the issues the team has raised.

To every team member expressing this concern you suggest raising this with the full team. You offer to help initiate the conversation but not to resolve the concern yourself.

Q36. If there are multiple Scrum Teams working on the same product, all of the Scrum Teams must mutually define a Definition of Ready (DoR). The DoR is a checklist that the Product Owner must fulfill before a Product Backlog item can be presented at the Sprint Planning. This protects the Development Team from interruptions and disruptions during the Sprint.

True

False

Q37. A Scrum Team has been working on a product for several iterations and has an average velocity of 55 units of ‘done’ work per Sprint. A second team will be added to work on the same product.
What might be the impact on the original team?

Their velocity is likely not affected and will remain at 55.

Their velocity is likely to drop and be less than 55.

Their velocity is likely to rise and be more than 55.

Q38. A key concern when multiple Development Teams are working for the same Product Backlog is minimizing dependencies between teams.

True

False