PMS1 - Example Questions
What does Burn-down Chart show?
Burn-down chart shows the evolution of remaining effort against time.
Who is responsible for all estimates in the Product Backlog?
The Development Team is responsible for all estimates in the Product Backlog. The Product Owner may influence the Development Team by helping it understand and select trade-offs, but the people who will perform the work make the final estimate.
Who is responsible for coping with incomplete artifact transparency?
The Scrum Master's job is to work with the Scrum Team and the organization to increase the transparency of the artifacts. This work usually involves learning, convincing, and change.
The Scrum Team consists of
The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master.
The purpose of ALL Sprints is to produce a Done Increment of working product. [A] False [B] True
[A]
What is Scrum?
A framework within which people can address complex adaptive problems, while delivering valuable products.
What are the three main questions each member of the Development Team should answer at the Daily Scrum?
During the Daily Scrum, the Development Team members explain: What did I do yesterday that helped the Development Team meet the Sprint Goal? What will I do today to help the Development Team meet the Sprint Goal? Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?
Who participates in the Sprint Review?
During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value.
Who creates the increment?
Only members of the Development Team create the Increment.
Scrum is founded on
Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known.
How much time does the Sprint Planning take?
Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint.
What is the Increment?
The Increment is the sum of all the Product Backlog items completed during the Sprint and the value of the increments of all previous Sprints.
Adding more resources to a Scrum project increases productivity and the delivery of value proportionally. [A] True [B] False
[F]
Imagine you are a Scrum Master. There are 10 professionals (developers and QAs) and the Product Owner. How to distribute people between development teams? Choose all applicable variants: 3 teams of 4, 3 and 3 people (each team is cross-functional) 2 teams of 6 and 4 people (the professionals after a short meeting decided this is the best variant) 2 teams of 6 and 4 people (because it is good to have all the QAs in a separate team) 1 team of 10 people (because there is no reason to divide)
: A & B Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint. Fewer than three Development Team members decrease interaction and results in smaller productivity gains. Having more than nine members requires too much coordination. The Product Owner and Scrum Master roles are not included in this count unless they are also executing the work of the Sprint Backlog.
What are Product Backlog features?
A Product Backlog is never complete. The earliest development of it only lays out the initially known and best-understood requirements. The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. As long as a product exists, its Product Backlog also exists
Sort Scrum events in the right order.
A sprint begins with Sprint Planning, then there are several Daily Scrum meetings following by Sprint Review and then Sprint Retrospective.
Who is responsible for crafting the Sprint Goal at the Sprint Planning?
After the Development Team forecasts the Product Backlog items it will deliver in the Sprint, the Scrum Team crafts a Sprint Goal.
Who is responsible for tracking the total work remaining in the Sprint Backlog to project the likelihood of achieving the Sprint Goal?
At any point in time in a Sprint, the total work remaining in the Sprint Backlog can be summed. The Development Team 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 Development Team can manage its progress.
The Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.
By the end of the Sprint Planning, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.
What are the characteristics of a Development Team?
Development Teams have the following characteristics: They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality; Development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment; 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; Scrum recognizes no sub-teams in the Development Team, regardless of particular domains that need to be addressed like testing or business analysis; there are no exceptions to this rule; and, Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.
How does Definition of "Done" help to the Scrum Team?
DoD is used to assess when work is complete on the product Increment Guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning DoD ensures artifact transparency
During each Sprint Retrospective the Scrum Team reviews the Definition of Done and changes it if necessary.
During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by adapting the definition of "Done" as appropriate.
What happens during the Sprint?
During the Sprint: No changes are made that would endanger the Sprint Goal; Quality goals do not decrease; and, Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned
Scrum recommends using only those Scrum components and rules which suit most for a particular project.
Each component within the Scrum framework serves a specific purpose and is essential to Scrum's success and usage.
Is it allowed to skip the Daily Scrum if there is nothing interesting to tell about?
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.
Definition of "Done" is created during the first Sprint and remains unchanged until the Product release.
False. During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by adapting the definition of "Done" as appropriate.
All the Scrum Teams working on the same product should have the same Sprint length.
False. Scrum does not require having aligned Sprints for multiple teams.
If an inspector determines that one or more aspects of a process deviate outside acceptable limits when an adjustment must be made?
If an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted. An adjustment must be made as soon as possible to minimize further deviation.
What should be taken into account for the Definition of "Done"?
If the definition of "done" for an increment is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum. If "done" for an increment is not a convention of the development organization, the Development Team of the Scrum Team must define a definition of "done" appropriate for the product. If there are multiple Scrum Teams working on the system or product release, the development teams on all of the Scrum Teams must mutually define the definition of "Done."
Who is responsible for creation of the Definition of "Done"?
If the definition of "done" for an increment is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum. If "done" for an increment is not a convention of the development organization, the Development Team of the Scrum Team must define a definition of "done" appropriate for the product. If there are multiple Scrum Teams working on the system or product release, the development teams on all of the Scrum Teams must mutually define the definition of "Done."
What happens during the Sprint? It is normal to have a "hardening" Sprint to remove all technical debt and prepare the Product for upcoming release.
It is not normal. Development Teams deliver an Increment of product functionality every Sprint. This Increment is usable, so a Product Owner may choose to immediately release it. So, there is nothing to prepare. Each increment contains only "Done" functionality that could be released immediately
It is a good practice to have from time to time a special technical Sprint that consists only of tasks removing the technical debt without implementing any new functionality.
It is prohibited. The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current definition of "Done."
All Development Teams working on the same Product should use the same Product Backlog.
Multiple Scrum Teams often work together on the same product. One Product Backlog is used to describe the upcoming work on the product.
What belongs solely to the Development Team?
Only the Development Team can change its Sprint Backlog during a Sprint. The Sprint Backlog is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint, and it belongs solely to the Development Team.
Who is allowed to change the Sprint Backlog during the Sprint?
Only the Development Team can change its Sprint Backlog during a Sprint. The Sprint Backlog is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint, and it belongs solely to the Development Team.
Who has the authority to cancel the Sprint?
Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master.
Please, check all opportunities to inspect and adapt.
Other than the Sprint itself, which is a container for all other events, each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection.
What does Product Backlog management include?
Product Backlog management includes: Clearly expressing Product Backlog items; Ordering the items in the Product Backlog to best achieve goals and missions; Optimizing the value of the work the Development Team performs; Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and, Ensuring the Development Team understands items in the Product Backlog to the level needed.
What part of the capacity of the Development Team does Product Backlog refinement usually consume?
Product Backlog refinement usually consumes no more than 10% of the capacity of the Development Team
What are the three most applicable characteristics of the Product Owner?
Product Value Maximizer Lead Facilitator of Key Stakeholder Involvement Product Marketplace Expert
What are the two essential features a Scrum Team should possess?
Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team.
Scrum does not allow additional meetings that are not defined in Scrum.
Scrum allows additional meetings if they facilitate achieving the Sprint Goal.
What are the three pillars that uphold Scrum?
Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.
Scrum does not describe agile processes and techniques.
Scrum is not a process or a technique for building products; rather, it is a framework within which you can employ various processes and techniques.
What are the formal Scrum events for inspection and adaptation?
Scrum prescribes four formal events for inspection and adaptation: Sprint Planning Daily Scrum Sprint Review Sprint Retrospective
How frequently should scrum users inspect Scrum artifacts and progress toward a Sprint Goal?
Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances. Their inspection should not be so frequent that inspection gets in the way of the work. Inspections are most beneficial when diligently performed by skilled inspectors at the point of work.
What are the questions the Sprint Planning answers?
Sprint Planning answers the following: What can be delivered in the Increment resulting from the upcoming Sprint? How will the work needed to deliver the Increment be achieved?
A time-box for each Scrum event.
Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. Sprint Review is a four-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. Sprint Retrospective is a three-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.
Please, select a time-box for each Scrum event.
Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. Sprint Review is a four-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. Sprint Retrospective is a three-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.
What does Cone of Uncertainty show?
The Cone of Uncertainty describes the evolution of the amount of uncertainty during a project.
The Daily Scrum time-box depends on the size of the Development team.
The Daily Scrum is a 15-minute time-boxed event for the Development Team of any size.
Who is responsible for all estimates in the Product Backlog?
The Development Team is responsible for all estimates in the Product Backlog. The Product Owner may influence the Development Team by helping it understand and select trade-offs, but the people who will perform the work make the final estimate
Other people than the Scrum Team can attend the Sprint Planning in order to provide technical or domain advice.
The Development Team may also invite other people to attend in order to provide technical or domain advice.
Select the two meetings in which people outside the Scrum Team are allowed to participate.
The Development Team may invite other people to attend the Sprint Planning in order to provide technical or domain advice. The Product Owner is responsible for inviting the Key Stakeholders to the Sprint Review meeting
The Sprint Backlog is created at the Sprint Planning. It is prohibited to add new work into the Sprint Backlog later by the Development Team.
The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Development Team works through the plan and learns more about the work needed to achieve the Sprint Goal. As new work is required, the Development Team adds it to the Sprint Backlog.
In which meetings the Key Stakeholders are allowed to participate?
The Key Stakeholders are allowed to participate only in the Sprint Review meeting. However, any member of the Scrum Team can interact with them any time.
What could be a source of requirements for any changes to be made to the product?
The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product.
It is a good practice to have at least two Product Owners on big projects.
The Product Owner is one person, not a committee, but the Product Owner may represent the desires of a committee in the Product Backlog.
What is the order of items in the Product Backlog?
The Product Owner is responsible for placing the most valuable and clear items at the top of the Product Backlog.
Who is responsible for the Product Backlog?
The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.
Who is responsible for managing the Product Backlog?
The Product Owner is the sole person responsible for managing the Product Backlog.
Who is allowed to make changes in the Product Backlog?
The Product Owner is the sole person responsible for the Product Backlog. However, he or she can delegate some work related to product backlog management to the Development Team.
Who is responsible for the monitoring of the remaining work towards the Project Goal?
The Product Owner tracks total work remaining at least every Sprint Review. The Product Owner 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.
Could the Sprint Planning be finished if only work planned for the first days of the Sprint is decomposed to units of one day or less?
The Scrum Guide requires only the work planned for the first days of the Sprint is decomposed by the end of the Sprint Planning, often to units of one day or less. However, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.
The Scrum Master does the following regarding the Daily Scrum:
The Scrum Master Ensures that the Development Team has the meeting, but the Development Team is responsible for conducting the Daily Scrum. Teaches the Development Team to keep the Daily Scrum within the 15-minute time-box. Enforces the rule that only Development Team members participate in the Daily Scrum
Who is allowed to participate in the Daily Scrum?
The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum. Other people could attend the meeting, but cannot participate
The Scrum Master is focused primarily on the Scrum Team and usually does not care about those outside the Scrum Team.
The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren't. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.
How does the Scrum Master serve the Development Team?
The Scrum Master serves the Development Team in several ways, including: Coaching the Development Team in self-organization and cross-functionality; Helping the Development Team to create high-value products; Removing impediments to the Development Team's progress; Facilitating Scrum events as requested or needed; and, Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood.
How does the Scrum Master help the Product Owner?
The Scrum Master serves the Product Owner in several ways, including: Finding techniques for effective Product Backlog management; Helping the Scrum Team understand the need for clear and concise Product Backlog items; Understanding product planning in an empirical environment; Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value; Understanding and practicing agility; and, Facilitating Scrum events as requested or needed.
How does the Scrum Master serve the Organization?
The Scrum Master serves the organization in several ways, including: Leading and coaching the organization in its Scrum adoption; Planning Scrum implementations within the organization; Helping employees and stakeholders understand and enact Scrum and empirical product development; Causing change that increases the productivity of the Scrum Team; and, Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization.
What part of the capacity of the Development Team does Product Backlog refinement usually consume? The Scrum Team consists of
The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master
What are the Scrum Artifacts?
The Scrum artifacts are Product Backlog, Sprint Backlog and Increment.
What comprises Scrum?
The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules. Each component within the framework serves a specific purpose and is essential to Scrum's success and usage.
What is the Sprint Backlog?
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.
What provides guidance to the Development Team on why it is building the Increment?
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 Development Team on why it is building the Increment.
What is the Sprint Retrospective?
The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
If an item in the Sprint Backlog cannot be finished by the end of the Sprint (it turned out there is a lot more work to do than was estimated), the Sprint is cancelled.
The Sprint is cancelled only in the case if the Sprint Goal became obsolete. If some work could not be done, the Sprint Backlog should be re-negotiated between the Product Owner and Development Team.
What is the input to the Sprint Planning?
The input to the Sprint Planning is the Product Backlog, the latest product Increment, projected capacity of the Development Team during the Sprint, and past performance of the Development Team.
The purpose of the Sprint Retrospective is to:
The purpose of the Sprint Retrospective is to: Inspect how the last Sprint went with regards to people, relationships, process, and tools; Identify and order the major items that went well and potential improvements; and, Create a plan for implementing improvements to the way the Scrum Team does its work.
What is the result of the Sprint Review?
The result of the Sprint Review is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint. The Product Backlog may also be adjusted overall to meet new opportunities.
What are the three main qualities the team model in Scrum is designed to optimize?
The team model in Scrum is designed to optimize flexibility, creativity, and productivity.
Only the Product Owner and the Development Team participate in the Sprint Planning. There is nothing to do for the Scrum Master.
The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team.
Who participates in the Sprint Planning?
The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team.
What happens when a Sprint is cancelled?
When a Sprint is cancelled, any completed and "Done" Product Backlog items are reviewed. If part of the work is potentially releasable, the Product Owner typically accepts it. All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog.
Could the Product Owner and the Scrum Master be a part of the Development Team?
Yes. Scrum does not prohibit the Product Owner or the Scrum Master do development work. However, it is not the best practice because it could create a conflict of interest.
Which statement best describes the Sprint Backlog? [A] It is created in the beginning of the Sprint [B] It contains all the remaining items from the previous Sprint [C] It is never updated during the Sprint [D] Each of its items have a designated owner
[A]
Which statement best describes the Sprint Backlog? [A] It is created in the beginning of the Sprint [B] It contains all the remaining items from the previous Sprint [C] It is never updated during the Sprint [D] Each of its items have a designated owner
[A] The Sprint Backlog is created during the Sprint Planning, which is the first event in the Sprint. There are items selected from the Product Backlog (by the Development Team), and the tasks created by decomposing the items (by the Development Team) in a Sprint Backlog. They keep adding tasks during the Sprint, so, the Sprint Backlog evolves during the Sprint. It's the Development Team's plan for the current Sprint. This plan is not detailed upfront. If the Development Team cannot deliver some of the items at the end of the Sprint, they will go back to the Product Backlog , and will be ordered again; they do not go to the next Sprint automatically. Each task is assigned to one developer or a pair of developers, but the ownership is still shared. Items are not assigned or owned by specific developers; all of them share accountability.
The Development Team cannot forecast how much work they can do in the upcoming Sprint, because of the uncertainties in the Product Backlog which the Product Owner is not able to overcome. What two actions should the Scrum Master recommend? [A] Invite everyone to discuss this problem in the next Sprint Retrospective and try to find a solution [B] Ask the developers to come up with their best guess and do not worry about the capacity [C] Extend the duration of Sprint Planning and ask them to discuss the items more and get into conclusion [D] Cancel the Sprint and start the next one when the items are clear [E] Cancel the Sprint Planning meeting, give them some time to prepare, and then hold another Sprint Planning
[A][B] The number of Product Backlog items picked in the Sprint Planning is the plan for the Sprint, but nothing happens if the team cannot deliver all of them; it's just a guess. If stakeholders start to blame the team for not delivering everything, the team will pick fewer items in the next Sprint to avoid the blame, and in return ends up with less productivity. This is however a problem that the items are not clear and it will certainly create more issues through the Sprint. Therefore, it's an important topic for the next Sprint Retrospective, when everyone should try to fix it. The Sprint Planning is timeboxed; never extended. It's also not possible to cancel the meeting and hold it another time (it's almost like extending the duration). It's nonsense to cancel the Sprint when it's not practically started. On the other hand, only the Product Owner can cancel the Sprint (when the goal becomes obsolete).
Who's in the Scrum Team? (Choose multiple answers) [A] Scrum Master [B] Team leader(s) [C] Product Owner [D] Project manager [E] Development Team
[A][C][E] Yes, some exam questions are as easy as this one. But be careful, a question might seem easy just because you didn't read it carefully.
The purpose of ALL Sprints is to produce a Done Increment of working product. [A] False [B] True
[B] The purpose of all Sprints is to create an Increment, which is "Done", a piece of working software usable for the users, "potentially releasable", and "potentially shippable". However, we do not necessarily "release" or "ship" all Increments. Remember that Scrum.org doesn't accept any special type of Sprint, such as Sprint 0, Hardening Sprint, Release Sprint, Integration Sprint, etc. All Sprints are the same.
Average items in the Product Backlog are usually... [A] Smaller than items in the Sprint Backlog [B] Larger than items in the Sprint Backlog [C] The same size as the items in the Sprint Backlog
[B] This is how it works: [A] Items with different sizes are added to the Product Backlog [B] Items are sorted based on their business value [C] Large items on the top of the Product Backlog are broken down into smaller ones to become clearer That's why the items on the top are smaller than those on the bottom. Also, because items selected for the Sprint Backlog come from the top of the Product Backlog, they are expected to be smaller than the average item in the Product Backlog. Remember that size is not a basis for ordering the Product Backlog items; it just happens automatically because of our process.
Adding more resources to a Scrum project increases productivity and the delivery of value proportionally. [A] True [B] False
[F] Normally, if you double the resources (team members), your productivity will increase less than twice; in other words, it's not proportional. There's also the Brook's Law that claims "adding manpower to a late software project makes it later" (you don't need it for the exam).
