Free Scrum PSM-I Practice Exam with Questions & Answers | Set: 5

According to the Scrum Guide, the Developers are accountable for managing the progress of work during a Sprint, as they are responsible for creating a valuable Increment that meets the Definition of Done and the Sprint Goal. The other options are not valid, as they imply that the Product Owner, the Scrum Master, or the most junior member of the team are accountable for managing the progress of work, which is not consistent with Scrum.

According to the Scrum Guide, three behaviors that demonstrate that a team is self-organizing are creating their own sprint backlog, having all the skills needed to create a releasable Increment, and collaboratively selecting their own work during the Sprint. The other options are not behaviors that demonstrate self-organization, as they are either contrary to Scrum values and principles (such as stakeholders walking in at the Daily Scrum or working within functional boundaries) or unnecessary for self-organization (such as the Product Owner not being at Sprint Retrospectives or the Development Team inviting external people to the Sprint Planning).

According to the Scrum Guide 1 , the Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Developers on why it is building the Increment. It also provides a basis for inspecting and adapting during the Sprint Review and Sprint Retrospective. The Sprint Goal is a result of Sprint Planning, as is the Sprint Backlog.

According to the Scrum Guide, the Development Team should do two things during the first Sprint: develop at least one piece of functionality and create an increment of potentially releasable software. These are the goals of every Sprint, regardless of its order. The other options are not things that the Development Team should do during the first Sprint, as they are either out of scope (such as making a plan for the rest of the project or defining major product features and release plan architecture) or unnecessary (such as analyzing, describing, and documenting requirements for subsequent Sprints).

The correct answer is C, because the Scrum Guide states that “the Development Team usually starts by designing the system and the work needed to convert the Product Backlog into a working product Increment. Work planned for the first days of the Sprint by the Development Team is decomposed by the end of this meeting, often to units of one day or less. The Development Team self-organizes to undertake the work in the Sprint Backlog, both during Sprint Planning and as needed throughout the Sprint.” Therefore, enough work should be defined during the Sprint Planning event so that the Development Team can create its best forecast of what it can do, and to start the first several days of the Sprint.

According to the Scrum Guide, the purpose of a Sprint is to produce a valuable useful Increment that meets the Definition of Done and the Sprint Goal. This means that the Developers work on items from the Product Backlog that deliver value to the stakeholders and align with the product vision. The other option is not valid, as it implies that producing an Increment is not the purpose of a Sprint.

The correct answers are B, E, and F, because these activities would probably help the team in starting up. Having the Scrum Team members introduce themselves and give a brief background of their skills and work history helps build trust and rapport among them. Ensuring the team understands they need a definition of “Done” helps create transparency and alignment on the quality standards for the product. Asking the Product Owner to discuss the product or project, its history, goals, and context, as well as answer questions helps clarify the vision and value of the product.

According to the Scrum Guide 1 , ordering Product Backlog items is solely up to the Product Owner’s discretion. The Product Owner orders items in the Product Backlog to best achieve goals and missions. To do this, they optimize value by considering various factors such as cost and benefit, risk, dependencies, date needed, etc. The Product Owner is responsible for maximizing the value of the work the Development Team does.

According to the Scrum Guide 1 , each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt. All events are time-boxed events, such that every event has a maximum duration. Once a 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 appropriate amount of time is spent without allowing waste in the process. The time-box for the Sprint Review is four hours for a one-month Sprint.

According to the Scrum Guide, the Developers are accountable for tracking the remaining work toward the Sprint Goal, as they are responsible for creating a valuable Increment that meets the Definition of Done and the Sprint Goal. The other options are not valid, as they imply that someone else outside the Development Team (such as the Scrum Master, the Product Owner, or the Project Manager) is accountable for tracking the remaining work, which is not consistent with Scrum values and principles.