Scrum Master
What does Product backlog management include?
1) Clearly expressing Product Backlog items; 2) Ordering the items in the Product Backlog to best achieve goals and missions; 3) Optimizing the value of the work the Development Team performs; 4) Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and, 5) Ensuring the Development Team understands items in the Product Backlog to the level needed.
What are the characteristics of a Development Team?
1) 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; 2) Development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment; 3) Scrum recognizes no titles for Development Team members, regardless of the work being performed by the person; 4) Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to be addressed like testing, architecture, operations, or business analysis; and, 5) Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.
What part of the capacity of the Development Team does Product Backlog refinement usually consume?
10% Product Backlog refinement usually consumes no more than 10% of the capacity of the Development Team.
What is the time-box for the Daily Scrum?
15 minutes
The Development Team should prepare a complete infrastructure and set of tools for the project during the first Sprint. 1. True 2. False
2 False The Development Team neither analyze, design nor describe the complete architecture and infrastructure, beforehand for the whole project. Agile processes are characterized by frequent short bursts of design, just enough to reach the Sprint Goal.
When the Development Team find itself in a situation where doesn't have the proper tools and infrastructure, what are the best two things to do? 1. The Development Team can't implement Scrum. 2. Coach the Development Team to improve its skills, tools, and infrastructure over time and adjust the Definition of Done accordingly. 3. A Sprint Zero is created to focus on infrastructure instead of creating an Increment. 4. The team must create a realistic Definition of Done under current circumstances.
2 and 4 Sprint Zero doesn´t exist in the Scrum framework and all the Sprints should be able to create an Increment of working software. The Inspections and Adaptation concepts are about making adjustments gradually through the project, this includes infrastructure and tools.
What two approaches should the Scrum Master take when your team doesn't have the proper infrastructure to do the work needed to complete the selected Product Backlog items? 1. Suspend the project. 2. Suspend the Sprint. 3. Coach the Development Team to improve infrastructure while adjusting the Definition of Done properly. 4. Create a special Sprint to get infrastructure instead of creating an increment. 5. Help the Scrum Team to create proper Sprint Goal and Definition of Done accordingly under current circumstances.
3 and 5
(Scrum Events) How long should the Sprint Planning be?
8 hours for 1-month Sprint. For shorter Sprints, the event is usually shorter. No need to decompose all the items in the Sprint Backlog. It can be done only for the first days of the Sprint.
Scrum Team consist of?
A Product Owner A Scrum Master Development Team
What are the three pillars that uphold Scrum?
Adaptation Inspection Transparency
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.
What should be taken into account for the Definition of "Done"?
Conventions, standards and guidelines of the Organization. Definition of "Done" of other Scrum Teams working on the same Product.
Who is responsible for creating Definition of Done
Development Team
Scrum is founded on ...?
Empiricism. Scrum is founded on empiricism which asserts that knowledge comes from experience and making decisions based on what is known.
Other people than the Scrum Team can attend the Sprint Planning in order to provide technical or domain advice.
False. The Development Team may also invite other people to attend in order to provide technical or domain advice.
Is it allowed to skip the Daily Scrum if there is nothing interesting to talk about?
No. 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.
How frequently should scrum users inspect Scrum artifacts and progress toward a Sprint Goal?
Not only at Sprint Review!!! Frequently, but it should not get in the way of the work. 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.
(Scrum Artifacts) Who is allowed to change the Sprint Backlog during the Sprint?
Only Development Team can change Sprint Backlog during the Sprint. The Sprint Backlog is a highly visible, realtime picture of the work that DevTeam plans to accomplish during the Sprint and it belongs solely to the DevTeam.
Who creates the increment?
Only members of the Development Team create the Increment.
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.
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.
How does the Scrum Master serve the Organization?
o 1) They lead and coach the organization in its Scrum adoption o 2) They plan Scrum implementations within the organization o 3) They help employees and stakeholders understand and enact Scrum and empirical product development o 4) They cause change that increases the productivity of the Scrum Team o 5) They work with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization
If an inspector determines that one or more aspects of a process deviate outside acceptable limits, when must an adjustment be made?
As soon as possible to minimize further deviation
What are two ways a Scrum Master serves to enable effective Scrum Teams? A)By starting and ending the meetings at the proper time. B)By facilitating Developer decision-making. C)By removing impediments that hinder the Scrum Team. D)By keeping high value features high in the Product Backlog.
B & C
What are the Scrum Artifacts? Select all applicable items.
Product Backlog Increment Sprint Backlog
Who participates in the Sprint Review?
The Scrum Master The Product Owner The Development Team The Key Stakeholders
What happens when a Sprint is cancelled? Select three.
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.
What does the word "development" mean in the context of Scrum? Select the best option.
When the words "develop" and "development" are used in the Scrum Guide, they refer to complex work including software and hardware development, development and releasing of products and enhancements, development and sustaining product operational environments, research and identifying of viable markets and technologies, and even more.
(Scrum Events) 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?
Yes, if the remaining work is also estimated, maybe in bigger units.
(Scrum Artifacts) All Development Teams working on the same Product use the same Product Backlog
Yes.
How much time by day, should the Development Team work on their tasks? 1. At least 6 real hours. 2. Around 8 hours. 3. As much as needed to complete the Sprint Backlog Items. 4. Enough to reach a constant pace and cadence.
4. Enough to reach a constant pace and cadence. Agile principles support processes which promote sustainable development, this means that every person related directly to a project should be able to maintain a constant pace indefinitely.
What is the result of the Sprint Review?
A revised Product Backlog that defines the probable Product Backlog items for the next Sprint
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.
Which two things should the Scrum Team do during the first Sprint? A)Develop a plan for the rest of the release. B)Create the complete Product Backlog to be developed in subsequent Sprints. C)Develop and deliver at least one piece of functionality. D)Determine the complete architecture and infrastructure for the product. E)Deliver an Increment of useful and valuable product.
C & E The heart of Scrum is a Sprint, which is one month or less during which a done, usable, valuable product Increment is created. This applies to EVERY SPRINT.
When does a Developer become accountable for the value of a Product Backlog item selected for the Sprint? A)Whenever a team member can accommodate more work. B)At the Sprint Planning Event. C)During the Daily Scrum. D)Never. The entire Scrum Team is accountable for creating value every Sprint.
D. Never. All members of the Scrum Team share in the accountability for creating value every Sprint.
(Scrum Artifacts) How does Definition of Done help 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
(Scrum Events) Definition of Done can be reviewed and adapted during each Sprint Retrospective?
During each Sprint Retrospective, the scrum team plans to increase product quality by improving work processes or adapting the Definition of Done, if appropriate and not in conflict with product or organization standards.
How much work must the Developers complete for each Product Backlog item they select for a Sprint? A)Analysis, design, programming, testing and documentation. B)Enough so that each Product Backlog item they select meets the Definition of Done. C)All development work and at least some testing. D)As much as it can fit into the Sprint.
Enough so that each Product Backlog item they select meets the Definition of Done.
The Scrum Master does the following regarding the Daily Scrum 1 Ensures that the Development Team has the meeting 2 If others are present at the Daily Scrum, ensures that they do not disrupt the meeting 3 Is responsible for conducting the Daily Scrum 4 Teaches the Development Team to keep the Daily Scrum within the 15-minute time-box
Ensures that the Development Team has the meeting If others are present at the Daily Scrum, ensures that they do not disrupt the meeting Teaches the Development Team to keep the Daily Scrum within the 15-minute time-box
The Daily Scrum always should take exactly 15 minutes. For example, if your team managed doing it in 5 minutes, you should spend 10 more minutes on some useful team activity like Product Backlog refinement, but not more.
False
Select the five Scrum Values.
Focus Commitment Courage Openness Respect
What does Cone of Uncertainty show?
How much is known about the Product over time, or The Cone of Uncertainty describes the evolution of the amount of uncertainty during a project.
What happens during the Sprint?
No changes are made that would endanger the Sprint Goal Quality goals do not decrease Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.
(Scrum Team) What are the three most applicable characteristics of the Product Owner?
Product Value Maximizer Lead Facilitator of Key stakeholder involvement Product Marketplace Expert
(Scrum Artifacts) What is the Sprint Backlog?
The Product Backlog items selected for this Sprint, plus the plan for delivering them
Who has the authority to cancel the Sprint?
The Product Owner
Who is allowed to make changes in the Product Backlog? Select two options.
The Product Owner The Development Team, but with permission of the Product Owner
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 promoting and supporting Scrum?
The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.
Who is responsible for coping with incomplete artifact transparency?
The Scrum Master's job is to work with Scrum Team and organization to increase the transparency of the artifacts. This work usually involves learning, convincing and change.
Check all the formal opportunities to inspect and adapt.
The Sprint Retrospective The Sprint Planning The Sprint Review The Daily Scrum 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 are the time-boxes for the Sprint Review and the Sprint Retrospective?
The Sprint Review is at most a four-hour meeting for one-month Sprints.The Sprint Retrospective is at most a three-hour meeting for one-month Sprints.
Scrum is not a process or technique. True or False?
True. Scrum is not a process or technique. Rather, it is a framework which you can employ various processes and techniques.
What is the right criteria to order the Product Backlog? 1. Items are randomly arranged. 2. Safer items are at the top, and riskier items are at the bottom. 3. The customer always decides. 4. Whatever is deemed most appropriate by the Product Owner.
4. Whatever is deemed most appropriate by the Product Owner. The decision on the order of items can be influenced by a committee, the customer, or any other stakeholder, but only the Product Owner decides what makes the most sense to optimize the value of the work being done by the Development Team.
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.
What is Scrum?
A framework within which people can address complex adaptive problems, while delivering valuable products.
When does the next Sprint begin? A)Immediately following the next Sprint Planning. B)Next Monday. C)When the Product Owner is ready. D)Immediately after the conclusion of the previous Sprint.
A new Sprint starts immediately after the conclusion of the previous Sprint.
The Scrum Master is focused primarily on the Scrum Team and usually does not care about those outside the Scrum Team.
False 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.
The Scrum Team must choose at least one high priority process improvement item, identified during the Sprint Retrospective, and place it in the Sprint Backlog.
False An earlier version of the Scrum Guide prescribed the practice of placing one improvement in the Sprint Backlog. This was removed in the 2020 update to the Scrum Guide because it was felt to be too prescriptive. However, if this practice provides value to you then you should adopt it. It is simply not prescribed anymore, but can still be valuable.
Scrum recommends using only those Scrum components and rules which suit most for a particular project.
False Each component within the Scrum framework serves a specific purpose and is essential to Scrum's success and usage.
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.
False 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."
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.
False 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.
Only the Product Owner and the Development Team participate in the Sprint Planning. There is nothing to do for the Scrum Master.
False 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.
The structure of the Daily Scrum is well-defined and constant. Every team member should answer the three main questions: What did I do yesterday? What will I do today? Do I see any impediment?
False There is no any prescribed structure. The structure of the Daily Scrum is set by the Development Team and can be conducted in different ways if it focuses on progress toward the Sprint Goal. Some Development Teams will use questions, some will be more discussion based. It is still perfectly fine to use the questions, but other ways of conducting the meeting are also possible.
It is a good practice to have at least two Product Owners on big projects.
False. The Product Owner is one person, not a committee, but the Product Owner may represent the desires of a committee in the Product Backlog.
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.
What does Burn-down chart show?
How much work remains till the end of the Sprint
Who creates the Definition of Done?
If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.
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.
What are the two essential features a Scrum Team should possess? It should choose how best to accomplish their work, rather than being directed by others outside the team It should be flexible enough to complete all the work planned for the Sprint even if some team members are on vacation It should have all competencies needed to accomplish the work without depending on others not part of the team It should use tools, processes and techniques approved by the Organization
It should choose how best to accomplish their work, rather than being directed by others outside the team It should have all competencies needed to accomplish the work without depending on others not part of the team
What is the order of items in the Product Backlog?
Less valuable and most unclear items at the bottom. The Product Owner is responsible for placing the most valuable and clear items at the top of the Product Backlog.
Imagine the following situation. At the Sprint Retrospective meeting the Scrum Team identified some improvements that can be done. What should the Scrum Team do? Select the best option.
Make sure the Sprint Backlog for the next Sprint includes at least one high priority process improvement.
The Sprint Backlog is created at Sprint Planning. Is it prohibited to add new work into the Sprint Backlog later by the Development Team.
No, not prohibited. 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.
Imagine you are a Scrum Master in a small Organization that tries to adopt Scrum. There are 10 developers and the Product Owner. How can they be divided into teams? Choose all applicable options:
Number of people in a Development Team should be between 3 and 9. Each team should be cross-functional and self-organized. 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.
(Scrum Events) What is the input to the Sprint Planning
Past performance of the DevTeam Projected capacity of the DevTeam during the Sprint The Product Backlog The latest product Increment
What are the components of Scrums?
Roles, Artifacts, Events, and Rules. Each component serves a specific purpose and is essential to Scrum's usage and success. The RULES of Scrums bind together the EVENTS, ROLES, and ARTIFACTS, governing the relationship and interaction between them.
(Scrum Team) How does the Scrum Master serve the Dev Team?
SM serves DevTeam in several ways: Coaching Dev Team in self-organization and cross-functionality Helping the DevTeam to focus on creating high value product Removing impediments to the Development Team's progress Facilitating Scrum events as requested or needed Coaching DevTeam in orgganizational environments in which Scrum is not yet fully adopted and understood.
Scrum does not allow additional meetings that are not defined in Scrum.
Scrum allows additional meetings if they facilitate achieving the Sprint Goal.
Where can Scrum be used? Check all the applicable items.
Scrum has been used to develop software, hardware, embedded software, networks of interacting function, autonomous vehicles, schools, government, marketing, managing the operation of organizations and almost everything we use in our daily lives, as individuals and societies.
What belong solely to Development Team
Sprint Backlog. Only Development Team can change Sprint Backlog during a Sprint.
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?
Who is allowed to participate in the Daily Scrum?
The Daily Scrum is an internal meeting for the Development Team. If others are present, the Scrum Master ensures that they do not disrupt the meeting.
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.
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.
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
Who participates in the Sprint Planning?
The Product Owner The Scrum Master The Development Team
Who is responsible for managing the Product Backlog?
The Product Owner is the sole person responsible for managing the Product Backlog.
Who is responsible for monitoring progress toward high-level goals?
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.
Which of the following services is appropriate for a Scrum Master in regard to the Daily Scrum? A)Ensure that all 3 questions have been answered. B)All answers apply. C)Lead the discussions of the Developers. D)Facilitate in a way that ensures each team member has a chance to speak. E)Teach the Developers to keep the Daily Scrum within the 15 minute timebox
The Scrum Master ensures that the Developers have the event, but the Developers are responsible for conducting the Daily Scrum. The Scrum Master teaches the Developers to keep the Daily Scrum within the 15-minute timebox. The Scrum Master enforces the rule that only members participate in the Daily Scrum.
How does the Scrum Master help the Product Owner? Select the three most appropriate answers.
The Scrum Master serves the Product Owner in several ways, including: 1) Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible; 2) Finding techniques for effective Product Backlog management; 3) Helping the Scrum Team understand the need for clear and concise Product Backlog items; 4) Understanding product planning in an empirical environment; 5) Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value; 6) Understanding and practicing agility; and, 7) Facilitating Scrum events as requested or needed.
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. The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).
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
Select the two meetings in which people outside the Scrum Team are allowed to participate.
The Sprint Review The Sprint Planning 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
What is the essence of Scrum?
The essence of Scrum is a small team of people. The individual team is highly flexible and adaptive. These strengths continue operating in single, several, many, and networks of teams that develop, release, operate and sustain the work and work products of thousands of people. They collaborate and interoperate through sophisticated development architectures and target release environments.
The purpose of the Sprint Retrospective is to
The purpose of the Sprint Retrospective is to: 1) Inspect how the last Sprint went with regards to people, relationships, process, and tools; 2) Identify and order the major items that went well and potential improvements; and, 3) Create a plan for implementing improvements to the way the Scrum Team does its work.
What are the three questions the Scrum Guide gives as an example that can be used at the Daily Scrum?
The structure of the Daily Scrum is set by the Development Team and can be conducted in different ways if it focuses on progress toward the Sprint Goal. Some Development Teams will use questions, some will be more discussion based. Here is an example of what might be used: 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?
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.
(Scrum Events) 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.
True. By the end of the SPRINT PLANNING, the DevTeam should be able to explain to the PO and SM how it intends to work as a self-organizing team to accomplish the Sprint Goal and create anticipated increment.