Practice Free PSM I Exam Online Questions
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 . Opportunities to insect and adapt the Sprint Backlog are lost.
- B . Impediments are raised and resolved more slowly.
- C . The Product Owner cannot accurately report progress to the stakeholders.
- D . Too much work is spent updating the Scrum board before the meeting.
- E . The Scrum Master loses the ability to update the Gantt chart properly.
- F . The Sprint plan may become inaccurate.
A,B,F
Explanation:
According to the Scrum Guide1, the Daily Scrum is an event for the Developers of the Scrum Team. The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. The Daily Scrum optimizes the probability that the Developers will meet the Sprint Goal. Every day, the Developers should understand how they intend to work together as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment by the end of the Sprint. If the frequency of the Daily Scrum were to be lowered to every two or three days, some key concerns would be:
Opportunities to inspect and adapt the Sprint Backlog are lost, which may result in wasted work or missed dependencies.
Impediments are raised and resolved more slowly, which may hinder the progress and quality of the work.
The Sprint plan may become inaccurate, as changes in requirements, risks, or priorities are not reflected in a timely manner.
The other options are not valid concerns, as they are not aligned with Scrum values and principles.
Reference: Scrum Guide
To get started in terms of what to build, Scrum requires no more than a Product Owner with enough ideas for a first Sprint, a Development Team to implement those ideas and a Scrum Master to help guide the process.
- A . True
- B . False
A
Explanation:
According to the Scrum Guide1, Scrum does not require or provide any specific techniques or methods for product definition. Rather, Scrum provides a framework with roles, rules, and events within which complex products can be developed. To get started in terms of what to build, Scrum requires no more than a Product Owner with enough ideas for a first Sprint, a Development Team to implement those ideas and a Scrum Master to help guide the process.
Reference: Scrum Guide
For the purpose of transparency, when does Scrum say a new increment of working software must be available?
- A . After the acceptance testing phase.
- B . Before the release Sprint.
- C . Every 3 Sprints.
- D . At the end of every Sprint.
- E . When the Product Owner asks to create one.
D
Explanation:
According to the Scrum Guide1, an Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, an Increment must be usable. Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism. However, an Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value. For the purpose of transparency, when does Scrum say a new increment of working software must be available? At the end of every Sprint.
Reference: Scrum Guide
In accordance with Scrum theory, how should a group of 100 people be divided into multiple Development Teams?
- A . Understanding the product, the product vision and the rules of the Scrum framework, the group divides itself into teams.
- B . It doesn’t really matter because you can rotate the teams every Sprint to spread knowledge.
- C . Check with the allocation department to see who has worked together before and make these the first teams.
- D . Create a matrix of skills, seniority, and level of experience to assign people to teams.
A
Explanation:
The correct answer is A, because in accordance with Scrum theory, a group of 100 people should be divided into multiple Development Teams by understanding the product, the product vision and the rules of the Scrum framework, and then dividing itself into teams. This approach respects the self-organization and empowerment of the people who will do the work, and allows them to form cross-functional and collaborative teams that can deliver value.
If burndown charts are used to visualize progress, what does a trend line through a release burndown chart indicate?
- A . The evolution of the cost spent on the project.
- B . When all work will be completed to the Scrum Team can be released for other work.
- C . When the work remaining will likely be completed if nothing changes on the Product Backlog or the Development Team.
- D . When the project will be over if the Product Owner removes work that is equal in effort to any new work that is added.
C
Explanation:
a burndown chart is a graphical representation of work left to do versus time. It is very useful for predicting when all of the work will be completed. It is often used in agile software development methodologies such as Scrum. However, burndown charts can be applied to any project containing measurable progress over time. A release burndown chart tracks progress across multiple Sprints towards a product release. It shows how much work remains in the Product Backlog at any given time during the release cycle. A trend line through a release burndown chart indicates when the work remaining will likely be completed if nothing changes on the Product Backlog or the Development Team.
Every Development Team should have:
- A . At least one representative from each major software engineering discipline (like QA, Dev, UX).
- B . The competencies and skills needed to deliver a Done Increment in a Sprint.
- C . One Lead Developer and no more than 8 other members.
B
Explanation:
According to the Scrum Guide1, the Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint. Development Teams are structured and empowered by the organization to organize and manage their own work. The resulting synergy optimizes the Development Team’s overall efficiency and effectiveness. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity.
Reference: Scrum Guide
What is the purpose of a Sprint Review?
- A . To take time to judge the validity of the project.
- B . To inspect the product increment with the stakeholders and collect feedback on next steps.
- C . To review the Scrum Team’s activities and processes during the Sprint.
- D . To build team sprint.
What is the function or purpose of management in Scrum? (choose the best answer)
- A . To identify and remove people that are not working hard enough.
- B . To monitor the productivity of the Developers.
- C . To present the Scrum Teams with insights and resources that help them improve.
- D . To continually monitor staffing levels of the Scrum Team.
C
Explanation:
The best answer is
C. The function or purpose of management in Scrum is to present the Scrum Teams with insights and resources that help them improve. According to the article What is the Function or Purpose of Management in Scrum?, management is still critical to providing vision, securing resources, hiring talent, training teams, removing roadblocks, and continuously improving. Management also encourages collaboration and establishes Scrum Team autonomy, which are essential for Scrum’s values and principles.
A, B and D are not good answers because they imply a command-and-control approach that contradicts Scrum’s values of respect, openness, and self-organization. Management in Scrum is not supposed to micromanage, judge, or interfere with the work of the Developers, but rather support them and enable them to deliver value.
Scrum has a role called “Project Manager”.
- A . True
- B . False
B
Explanation:
The correct answer is B, because there is no role called “Project Manager” in Scrum. The Scrum Guide states that “Scrum recognizes no titles for Development Team members other than Developer, regardless of the work being performed by the person; there are no exceptions to this rule.” Therefore, Scrum has only three roles: Product Owner, Scrum Master, and Developer.
In order to achieve the benefits of Scrum, it is important to enact the value of commitment.
What two actions demonstrate the commitment of Scrum Team members? (Choose two.)
- A . Always deliver the items in the Sprint forecast.
- B . Help the other Scrum Team members.
- C . Do your best
- D . Send out a daily status report.
- E . Work late.
B,C
Explanation:
According to the Scrum Guide1, there are five values that guide decisions within Scrum teams:
Commitment
Focus
Openness
Respect
Courage
In order to achieve the benefits of Scrum, it is important to enact these values. Two actions that demonstrate the commitment of Scrum Team members are:
Help the other Scrum Team members, as they work together as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment by the end of the Sprint.
Do your best, as they strive to deliver a potentially releasable Increment that meets the definition of “Done” and provides value to the stakeholders.
