Professional Scrum Master

23 important questions on Professional Scrum Master

What can you say about time-boxing events?

All events are time-boxed. Once at Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an apppropriate amount of time is spent without allowing waste in the process.

What does the Sprint contain and consist of?

The heart of Scrum is a Sprint, a time-box of one month or less during which a "Done", useable, and potentially releaseable product increment is created. Sprints best have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint.
Sprints contain and consist of:
  • the Sprint Planning
  • Daily Scrums
  • the Development work
  • the Sprint Review
  • the Sprint Retrospective

Describe a Sprint

Each Sprint may be considered a project with no more than a one-month horizon. Like projects, Sprints are used to accomplish something. Each Sprint has a definition of what is to be built, a design and flexible plan that will guide building it, the work, and the resultant product.
  • Higher grades + faster learning
  • Never study anything twice
  • 100% sure, 100% understanding
Discover Study Smart

Why is a Sprint limited to one calender month?

Sprints are limited to one calender month. When a Sprint's horizon is too long the definition of what is being built may change, complexity may rise, and risk may increase. Sprints enable predictability by ensuring inspection and adaptation of progress toward a Sprint Goal at least every calender month. Sprints also limit risk to one calender month of cost.

When and by whom can a Sprint be cancelled?

A Sprint can be cancelled before the Sprint time-box is over. Only the PO has the authority to cancel the Sprint (although he or she may do so under influence from the stakeholders, the DT, or the SM.

What can be said about the Sprint Goal towards the Product Backlog?

The Sprint Goal gives the DT some flexibility regarding the functionality implemented within the Sprint. The selected PB items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the DT to work together rather than on seperate initiatives.

What is the function of the Sprint Goal for the DT?

In order to satisfy the Sprint Goal, it implements the functionality and technology. If the work turns out to be different than the DT expected, they collaborate with the PO to negotiate the scope of SB within the Sprint.

What is a Daily Scrum?

The Daily Scrum is a 15-minute time-boxed event for the DT to synchronize activities and create a plan for the next 24 hours. This is done by inspecting the work since the last Daily Scrum and forecasting the work that could be done before the next one.

How is a Daily Scrum organized?

The Daily Scrum is held at the same time and place each day to reduce complexity. During the meeting the DT members explain:
  • What did I do yesterday that helped the DT meet the Sprint Goal?
  • What will I do today to help the DT meet the Sprint Goal?
  • Do I see any impediment that prevents me for the DT from meeting the Sprint Goal?

What is the role of the SM in the DS?

The SM ensures that the DT has the meeting, but the DT is responsible for conducting the DS. The SM teaches the DT to keep the DS within the 15-minute time-box.
The SM enforces the rule that only DT members participate in the DS.

What is a Sprint Review?

A Sprint Review is held at the end of the Sprint to inspect the increment and adapt the PB if needed. During the Sprint Review, the ST and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the PB during the Sprint, attendees collaborate on the next things that could be done to optimize value. This is an informal meeting, not a status meeting, and the presentation of the increment is intended to elicit feedback and foster collaboration.

What is the duration of a Sprint Review?

This is a four-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. The SM ensures that the event takes place and the attendants understand its purpose. The SM teaches all to keep it within  the time-box.

What is the role of the SM in a Sprint Retrospective?

The SM ensures that the event takes place and that attendants understand its purpose. The SM teaches all to keep it within the time-box. The SM participates as a peer team member in the meeting from the accountability over the Scrum process.

The SM encourages the ST to improve, within the Scrum process framework, its development process and practices to make it more effective and enjoyable  for the next Sprint.

What are the deliverables of a Sprint Retrospective?

By the end of the Sprint Retrospective, the ST should have identified improvements that it will implement in the next Sprint. Implementing these improvements in the next Sprint is the adaptation to the inspection of the ST itself.
Although improvements may be implemented at any time, the Sprint Retrospective provides a formal opportunity to focus on inspection and adaptation.

How can a PB contribute to multiple ST's working on the same product?

One PB is used to describe the upcoming work on the product. A PB attribute that groups items may then be employed.

What is PB refinement?

PB refinement is the act of adding detail, estimates, and order to items in the PB. This is an ongoing process in which the PO and the DT collaborate on the details of PB items. During PB refinement, items are reviewed and revised. The ST decides how and when refinement is done.
Refinement usually consumes no more than 10% of the capacity of the DT. However PB items can be updated at any time by the PO or at the PO's discretion.

What can you say about the transparency of the PB items during refining activities?

Higher ordered PB items are usually clearer and more detailed than lower ordered ones. More precise estimates are made based on the greater clarity and increased detail; the lower the order, the less detail. PB items that will occupy the DT for the upcoming Sprint are refined so that any one item can be reasonably be "Done" within the Sprint time-box. PB items that can be "Done" by the DT within one Sprint are deemed "Ready" for selection in a Sprint Planning. PB items usually acquire this degree of transparency through the above described refining activities.

What is the role of the PO in monitoring progress towards a goal?

At any point in time, the total work remaining to reach a goal can be summed. The PO tracks this total work remaining at least every Sprint Review. The PO compares this amount with work remaining at previous Sprint Reviews to assess progress toward completing projected work by the desired time for the goal. This information is made transparent to all stakeholders.

What can be said about the details in a SB?

The SB is a plan with enough detail that changes in progress can be understood in the Daily Scrum. The DT modifies the SB throughout the Sprint, and the SB emerges during the Sprint. This emergence occurs as the DT works through the plan and learns more about the work needed to achieve the Sprint Goal.

What can be said about making changes in the SB?

As new work is required, the DT adds it to the SB. As work is performed or completed, the estimated remaining work is updated. When elements of the plan are deemed unnacessary, they are removed.
Only the DT can change its SB during a Sprint. The SB is a highly visible, real-time picture of the work that the DT plans to accomplish during a Sprint, and it belongs solely to the DT.

Who is responsible for monitoring Sprint progress?

At any point in time of a Sprint, the total work remaining in the SB can be summed. The DT tracks this total work remaining at least for every Daily Scrum to project the likelihood of achieving the Sprint Goal. By tracking the remaining work throughout the Sprint, the DT can manage its progress.

As ST's mature, what can be expected of their definitions of "Done"?

Their definitions of "Done" will expand to include more stringent criteria for higher quality. Any one product or system should have a definition of "Done" that is a standard for any work done on it.

What can be said about implementing only parts of Scrum?

Scrum is free, roles, artifacts, events and rules are immutable. Athough implementing only parts of Scrum is possible, the result is not Scrum. Scrum exists only in its entireliy and functions well as a container for other techniques, methodologies and practices.

The question on the page originate from the summary of the following study material:

  • A unique study and practice tool
  • Never study anything twice again
  • Get the grades you hope for
  • 100% sure, 100% understanding
Remember faster, study better. Scientifically proven.
Trustpilot Logo