What is Scrum? A framework within which people can address complex adaptive problems, while delivering valuable products. 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. The Scrum Team consists of 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 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. 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. What are the characteristics of a Development Team? 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. A time-box for each Scrum event. Sprint Planning is time-boxed to a maximum of 8 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 4-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. Sprint Retrospective is a 3-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. 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. 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. 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 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. 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. 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 How does the Scrum Master serve the Organization? 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. 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. 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. 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. What does Burn-down Chart show? Burn-down chart shows the evolution of remaining effort against time. Scrum does not allow additional meetings that are not defined in Scrum. Scrum allows additional meetings if they facilitate achieving the Sprint Goal. 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 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. 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 are the formal Scrum events for inspection and adaptation? Sprint Planning Daily Scrum Sprint Review Sprint Retrospective What happens 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 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. 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. 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. 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. 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. 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. 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. The rules of Scrum bind together the events, roles, and artifacts, governing the relationships and interaction between them. The Scrum Master does the following regarding the Daily Scrum: 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 What are Product Backlog features? Never complete. The earliest development of it only lays out the initially known and best-understood requirements. Evolves as the product and the environment in which it will be used evolves. 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 How does the Scrum Master help the Product Owner? Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible; 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 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 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. 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 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. 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.” 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. 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. 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. 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 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.” 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. 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 reestimated and put back on the Product Backlog. 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. 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. 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. What does Product Backlog management include? 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. Who is responsible for managing the Product Backlog? The Product Owner is the sole person responsible for managing the Product Backlog. 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 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. 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. Who is responsible for the Product Backlog? The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering. 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: A. B. C. D. 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 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. What does Cone of Uncertainty show? The Cone of Uncertainty describes the evolution of the amount of uncertainty during a project. What are the three most applicable characteristics of the Product Owner? Product Value Maximizer Lead Facilitator of Key Stakeholder Involvement Product Marketplace Expert 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 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. The Daily Scrum time-box depends on the size of the Development team. No, the Daily Scrum is a 15-minute time-boxed event for the Development Team of any size. 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. 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. How much time does the Sprint Planning take? Sprint Planning is time-boxed to a maximum of 8 for a one-month Sprint. 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. 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. 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? 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 How does the Scrum Master serve the Development Team? 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. 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 questions the Sprint Planning answers? What can be delivered in the Increment resulting from the upcoming Sprint? How will the work needed to deliver the Increment be achieved? What does the word “development” mean in the context of Scrum? 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. 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. Where can Scrum be used? 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. Scrum has been used extensively, worldwide, to: Research and identify viable markets, technologies, and product capabilities; Develop products and enhancements; Release products and enhancements, as frequently as many times per day; Develop and sustain Cloud (online, secure, on-demand) and other operational environments for product use; and, Sustain and renew products. 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.” 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 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 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. Who creates the increment? Only members of the Development Team create the Increment. 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. 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? The Sprint Backlog makes visible all the work that the Development Team identifies as necessary to meet the Sprint Goal. To ensure continuous improvement, it includes at least one high priority process improvement identified in the previous Retrospective meeting. Five Scrum Values commitment, courage, focus, openness and respect. Average items in the Product Backlog are usually Larger than items in the Sprint Backlog This is how it works: Items with different sizes are added to the Product Backlog Items are sorted based on their business value 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. Which statement best describes the Sprint Backlog? Created in the beginning of the Sprint, 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. Adding more resources to a Scrum project increases productivity and the delivery of value proportionally. False. Normally, if you double the resources (team members), your productivity will increase less than twice; in other words, it’s not proportional. The purpose of ALL Sprints is to produce a Done Increment of working product. True. 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. 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? Invite everyone to discuss this problem in the next Sprint Retrospective and try to find a solution Ask the developers to come up with their best guess and do not worry about the capacity 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). Scrum Teams should normalize their estimates, so that management can measure and compare their performance. False. It’s almost impossible to make the estimate units (e.g. story points) comparable, and only creates problems such as padding if you try to. Besides that, the “management” is not supposed to measure their “performance”; they should be focused on the value generated in the project. Which of the following is not timeboxed? Product Backlog refinement. All events are timeboxed: Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. The Product Backlog refinement is a continuous activity. Who can attend the Daily Scrum? Anyone “can attend” any meeting. Daily Scrum is only for the Development Team, so no one else is “required to attend”, and if they do, they are not supposed to “participate”; they just listen and watch. There should be a hardening Sprint every few Sprints, to resolve dependencies and fix open bugs. False. There’s only one type of Sprint, and its goal is to create a potentially releasable Increment of software that brings value to the customer. There’s no Sprint zero, hardening Sprint, integration Sprint, release Sprint, etc. Who should create the Sprint Goal? The Sprint Goal is created at the Sprint Planning meeting by the whole Scrum Team. When multiple teams are working on the same project, there should be one Definition of Done for all of them. False. Each team might be working on a different part of the product (e.g. desktop application, mobile application, web application), or simply have different styles of work, and therefore require different Definitions of Done. This is all right, as long as their definitions are compatible and have the capacity to create one Integrated Increment each Sprint. The definitions should also contain all the minimum requirements coming from the organization. Note: When multiple teams are working on the same project, all their outputs will be combined into one Integrated Increment. They also have only one Product Backlog, and one Product owner. What should be done between two Sprints? Nothing; there’s no time between the two. There’s no time between one Sprint and the next. Ordering the Product Backlog items and estimating the amount of work of new items that is needed for the next Sprint Planning is done during the previous ones, in a continuous process called Product Backlog refinement (or Product Backlog grooming). Who’s the project manager in Scrum? No one. Scrum doesn’t have a project manager role. The project management activities are distributed among the three Scrum roles. Who estimates the work of the newly identified items? All estimates are done by the Development Team, since they are the ones who know how to do the work. Which of the following are common Product Owner activities during the Sprint? (Choose 2 answers) The Product Owner keeps communicating with the stakeholders, creates new items in the Product Backlog, revises the order of items, answers questions, makes sure that everyone has the right understanding of items, and checks the completed items with the Development Team to ensure they are Done based on the Definition of Done. Creating and prioritizing tasks, running Daily Scrums, and measuring the Sprint performance are the Development Team’s responsibility. Which output of the Sprint Planning provides the overall direction for the Sprint? The Sprint Goal is the overall direction for the Sprint; something more than the sum of all items in the Sprint Backlog. It’s used to see how we adjust the work defined in the Sprint Backlog. When do Development Team members volunteer to own a Sprint Backlog item? The Developers share the ownership of the items and tasks in the Sprint Backlog. Tasks are assigned to the Developers (by themselves), but they all stay accountable (own the task). Items are not assigned to Developers, as each item consists of multiple tasks that need varying expertise. To summarize: • • • • Items are not owned by individuals/pairs Items are not assigned to individuals/pairs Tasks are not owned by individuals/pairs Tasks are indeed assigned to individuals/pairs (they volunteer to take responsibility for tasks) It’s a good practice to use Pair Programming in Agile, which is when two developers work on the same piece of code. One developer writes code and the other observes and gives suggestions. After a while, they switch places. Note: “tasks” are usually called “work”. Who decides on the technical approach? This is completely up to the self-organized Development Team to decide on the way they work and on the technical aspects of the project. Which two (2) things does the Development Team do during the first Sprint? Deliver an increment of releasable software and Develop and deliver at least one piece of functionality. The heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created. This applies to every Sprint Who is required to attend the Daily Scrum? Only the people doing the work described on the Sprint Backlog need to inspect and adapt at the Daily Scrum. If the Scrum Master or Product Owner is also on the Development Team, they will need to be at the Daily Scrum. Otherwise, the Scrum Master simply has to make sure the Development Team knows how to conduct a Daily Scrum and does so. The length of a Sprint should be: All of these choices are appropriate considerations in determining the length of a Sprint. Short enough to keep the business risk acceptable to the Product Owner. Short enough to be able to synchronize the development work with other business events. No more than one month. An organization has decided to adopt Scrum, but management wants to change the terminology to fit with terminology already used. What will likely happen if this is done? Without a new vocabulary as a reminder of the change, very little change may actually happen. The organization may not understand what has changed with Scrum and the benefits of Scrum may be lost. Management may feel less anxious. Development Team membership should change: As needed, while taking into account a short term reduction in productivity. Teams typically go through some steps before achieving a state of increased performance. Changing membership typically reduces cohesion, affecting performance and productivity in the short term. What does it mean to say that an event has a time-box? Time-boxed events are events that have a maximum duration. Why is the Daily Scrum held at the same time and same place? The Daily Scrum is held at the same time and place each day to reduce complexity. It is mandatory that the product increment be released to production at the end of each Sprint. False. The product increment should be usable and releasable at the end of every Sprint, but it does not have to be released. When many Development Teams are working on a single product, what best describes the definition of “done?” Scrum requires an Increment to be releasable. This is an Increment of product. Many teams working on a single product are expected to deliver such an Increment During a Sprint, a Development Team determines that it will not be able to finish the complete forecast. Who should be present to review and adjust the Sprint work selected? During the Sprint, scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned. Who should know the most about the progress toward a business objective or a release, and be able to explain the alternatives most clearly? The Product Owner is the sole person responsible for managing the Product Backlog, which includes that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next. Who has the final say on the order of the Product Backlog? The Product Owner is the sole person responsible for managing the Product Backlog When does the next Sprint begin? A new Sprint starts immediately after the conclusion of the previous Sprint. When is a Sprint over? When the time-box is over. Who is responsible for managing the progress of work during a Sprint? The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog. Which statement best describes the Sprint Review? It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next. During the Daily Scrum, the Scrum Master’s role is to: The Scrum Master ensures that the Development Team has the meeting, but the Development Team is responsible for conducting the Daily Scrum. The Scrum Master teaches the Development Team to keep the Daily Scrum within the 15-minute time-box. The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum. How much work must a Development Team do to a Product Backlog item it selects for a Sprint? The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team’s current definition of “Done”. When multiple teams work together on the same product, each team should maintain a separate Product Backlog. False. Products have one Product Backlog, regardless of how many teams are used. Any other setup makes it difficult for the Development Team to determine what it should work on. What are the two primary ways a Scrum Master keeps a Development Team working at its highest level of productivity? A Scrum Master is a servant-leader for the Development Team. Facilitation and removing impediments serves a team in achieving the best productivity possible. What is the role of Management in Scrum? Support the Product Owner with insights and information into high value product and system capabilities. Support the Scrum Master to cause organizational change that fosters empiricism, self-organization, bottom-up intelligence, and intelligent release of software. Management has no active role in the actual product development through Scrum. However, management external to the Scrum team is incredibly important in setting the vision and strategy to guide the overall direction of the organization. What is the main reason for the Scrum Master to be at the Daily Scrum? The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum. Which statement best describes a Product Owner’s responsibility? The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. The Sprint Goal is a result of Sprint Planning, as is the Sprint Backlog True Which output from Sprint Planning provided the Development Team with a target and overarching direction for the Sprint? The Sprint Goal Which two of the following are true about the Scrum Master role? Choose 2 answers The Scrum Master helps those outside the team interact with the Scrum Team. The Scrum Master teaches the Development Team to keep the Scrum meetings to their timebox. Which outcome is expected as Scrum Teams mature? They will improve their definition of "Done" to include more stringent criteria. Which technique is the best way the Scrum Master can ensure that the Development Team communicates effectively with the Product Owner? Teach the Development Team to talk in terms of business needs and objectives. Which two ways of creating Development Teams are consistent with Scrum's values? Choose 2 answers Bring all the developers together and let them self-organize into Development Teams. Existing teams propose how they would like to go about organizing. The Product Owner determine how many Product Backlog items the Development Team selects for a Sprint? False 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 3 answers Impediments are raised and resolved more slowly. Opportunities to inspect and adapt the Sprint Backlog are lost. The Sprint plan becomes inaccurate. Which topics should be discussed in the Sprint Review? Sprint Results How is management external to the Scrum Team involved in the Daily Scrum? The Development Team self-manages and is the only management required at the Daily Scrum. The Development Team informs the Scrum Master that the IT manager has asked for a status report during the Sprint. The Scrum Master will: Talk to the IT manager and explain that progress in Scrum comes from inspecting an increment at the Sprint Review. As the Sprint Planning meeting progresses, the Development Team sees that the workload is greater than they can handle. Which two are valid actions? Choose 2 answers Remove or change selected Product Backlog items. Recruit additional Development Team members before the work can begin. Which answer best describes the topics covered in Sprint Planning? What can be done and how to do it. Which of these may a Development Team deliver at the end of a Sprint? An increment of working software that is "done". What are two ways that architecture and infrastructure are handled in Scrum? They are added to the Product Backlog and addressed in early Sprints, while always requiring at least some business functionality, no matter how small. They are implemented along with functional development of the product. If two Scrum Teams are added to a project that previously had only one Scrum Team, what will be the immediate impact on the first Scrum Team's productivity? Productivity will stay the same. As a Scrum Master, how would you divide a group of 100 people into multiple Development Teams? Tell the group about the product, the product vision, and rules of the Scrum framework. They then form into teams. A Development Team selects a set of Product Backlog items for a Sprint Backlog with the intent to get the selected items done by the end of the Sprint. Select two statements that explain what done means. Choose 2 answers No work left from the definition of "Done". All work to create software usable by end users. When many Development Teams are working on a single product, what best describes the definition of "Done"? All Development Teams must have a definition of "Done" that makes their combined work potentially releasable. As the Development Team starts work during the Sprint, it realizes it has selected too much work to finish in the Sprint. What should it do? As soon as possible in the Sprint, work with the Product Owner to remove some work or Product Backlog items. When can a Development Team cancel a Sprint? It can't. Only Product Owners can cancel Sprints. When a Development Team determines that is has over-committed itself for a Sprint, who has to be present when reviewing and adjusting the Sprint work selected? The Product Owner and the Development Team Every Development Team should have: The competencies and skills needed to deliver a Done Increment in a Sprint. You have just been hired by a company new to Scrum. Your management has assigned you to be the Scrum Master of six new Scrum Teams. These teams will build one product. Select two conditions you should strive for in this scenario. Choose 2 answers There should be only one Product Owner. The product has one Product Backlog. The Product Owner makes sure the team selects enough from the Product Backlog for a Sprint to satisfy the stakeholders. False Which best describes the Product Backlog? It is allowed to grow and change as more is learned about the product and its customers. What three factors are best considered when establishing the Sprint length? Choose 3 answers The risk of being disconnected from the stakeholders. The ability to go to market with a product release The frequency that team composition can be changed Which three of the following are feedback loops in Scrum? Sprint Review Refinement Meeting Sprint Retrospective When may a Development Team change its engineering practices? Whenever needed A Development Team selects a set of Product Backlog items for a Sprint Backlog with the intent to get the selected items "Done" by the end of the Sprint. Which three phrases best describe the purpose of a definition of "Done"? Choose 3 answers It creates transparency over the work inspected at the Sprint Review. It defines what it takes for an increment to be ready for release. It guides the Development Team in creating a forecast at the Sprint Planning. A new developer is having continuing conflicts with existing Development Team members and creating a hostile environment. If necessary, who is responsible for removing the team member? The Scrum Master is responsible, because he/she removes impediments. Which does a self-organizing Development Team choose? How to best accomplish its work What are two good ways for a Scrum Team to ensure security concerns are satisfied? Choose 2 answers Have the Scrum Team create Product Backlog items for each concern. Add security concerns to the definition of "Done". Who is responsible for engaging the stakeholders? The Product Owner Who should make sure everyone on the Development Team does his or her tasks for the Sprint? The Development Team What does it mean for a Development Team to be cross-functional? The Development Team includes cross-skilled individuals who are able to contribute to do what is necessary to deliver an increment of software. A Scrum Master is introducing Scrum to a new Development Team. The Development Team has decided that a retrospective is unnecessary. What action should the Scrum Master take? Consult with the Product Owner to see how he/she feels about the situation. Which of the following are true about the length of the Sprint? Choose 2 answers All Sprints must be 1 month or less. It is best to have Sprints of consistent length throughout a development effort. How often should Development Team membership change? As needed, while taking into account a short term reduction in productivity. One of the Scrum events is the Daily Scrum. What are two outcomes of the Daily Scrum? Choose 2 answers An updated list of impediments for the Scrum Master to take care of. A shared understanding of the most important work to be undertaken next to achieve the best possible progress toward the Sprint goal. What are three benefits of self-organization? Choose 3 answers Increased creativity Increased commitment Increased accuracy of estimates The definition of "Done" is used to: Choose 3 answers Guide the Development Team on how many Product Backlog items to select for the Sprint. Create a shared understanding of when work is complete. Increase transparency. Who creates a Product Backlog item's estimate? The Development Team after clarifying requirements with the Product Owner. What are two guidelines a Scrum Master would use to divide a group of 100 people into multiple Development Teams? Choose 2 answers Let the Development Teams decide. Ask the developers to divide themselves into teams. When is a Product Backlog item considered complete? When the item has no work remaining in order to be released. What is the main reason for the Scrum Master to be at Daily Scrum? He or she does not have to be there, he or she only has to ensure the Development Team has a Daily Scrum. The Product Owner is not collaborating with the Development Team during the Sprint. What are two valuable actions for a Scrum Master to take? Choose 2 answers Answer 1 of 2: Inform the Product Owner's functional manager. Answer 2 of 2: Bring up the problem in the Sprint Retrospective. A Development Team pulled a Product Backlog item into the Sprint and worked on it. However, it does not meet their definition of "Done" by the end of the Sprint. What three things should happen with the incomplete Product Backlog item? Choose 3 answers Answer 1 of 3: Do not include the item in the increment this Sprint. Answer 2 of 3: Do not show it in the Sprint Review. Answer 3 of 3: Re-estimate it and return it to the Product Backlog for the Product Owner to decide what to do with it. Which are NOT appropriate topics for discussion in a Sprint Retrospective? Choose 2 answers Definition of "Done". Sprint Backlog for the next Sprint. The Product Owner must release each increment to production. When it makes sense. Choose two responsibilities of a self-organizing Development Team. Choose 2 answers Answer 1 of 2: Do the work planned in the Sprint Backlog. Answer 2 of 2: Pull Product Backlog items for the Sprint. The Development Team should have all the skills needed to: Turn Product Backlog items into an increment of potentially releasable product functionality. Which of the following are true about the Product Owner role? Choose 3 answers Answer 1 of 3: The Product Owner is one person. Answer 2 of 3: The Product Owner is accountable for ordering the Product Backlog. Answer 3 of 3: The Product Owner can be influenced by committee. Why does a Development Team need a Sprint Goal? A Sprint Goal ensures that all of the Product Backlog items selected for the Sprint are implemented. What is the primary way a Scrum Master keeps a Development Team working at its highest level of productivity? By facilitating Development Team discussions and removing impediments. A Scrum Master is working with a Development Team that has members in different physical locations. The Development Team meets in a variety of meeting rooms and has much to do logistically (for example, set up conference calls) before the Daily Scrum. What action should the Scrum Master take? Allow the Development Team to self manage and determine for itself what to do. What is the accountability of the Product Owner during Sprint 0? There is no such thing as Sprint 0. What activities would a Product Owner typically undertake in the phase between the end of the current Sprint and the start of the next Sprint? There are no such activities. The next Sprint starts immediately after the current Sprint. What are two good ways for the Development Team to make non-functional requirements visible? Choose 2 answers Add them to the definition of "Done" so the work is taken care of every Sprint. Add them to the Product Backlog and keep the Product Owner posted on the expected effort. How much work must a Development Team do to a Product Backlog item it selects for a Sprint? As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of "Done". Which is NOT a Development Team responsibility? Selecting the Product Owner. The Product Backlog is ordered by: Higher priority items are at the top. You are the Scrum Master on a newly formed Scrum Team. Which three of the following activities would probably help the team in starting up? Choose 3 answers Ensure the team understands they need a definition of "Done". Have the Scrum Team members introduce themselves to each other and give a brief background of their skills and work history. Ask the Product Owner to discuss the product or project, its history, goals, and context, as well as answer questions. When the Development Team is having trouble delivering a working increment because they don't understand a functional requirement, what should they do? Collaborate with the Product Owner to determine what is possible and acceptable. What is it most appropriate for a Development Team to change the definition of "Done"? During Sprint Planning. Who must do all the work to make sure Product Backlog items conform to the Definition of "Done"? The Scrum Team. When do Development Team members take ownership of a Sprint Backlog item? Never. All Sprint Backlog items are "owned" by the entire Development Team, even though each one may be done by an individual Development Team member. A Scrum Team is only allowed to meet with stakeholders during the Sprint Review? False. Which two things should the Development Team do during the first Sprint? Choose 2 answers - Develop at least one piece of functionality. - Create an increment of potentially releasable software. Every Scrum Team must have a Product Owner and Scrum Master? True. Outcomes are affected by their participation and availability. How should Product Backlog items be chosen when multiple Scrum Teams work from the same Product Backlog? The Development Teams pull in work in agreement with the Product Owner. What are the two primary ways a Scrum Master keeps a Development Team working at its highest level or productivity? - By removing impediments that hinder the Development Team. - By facilitating Development Team decisions. When a Development Team determines that it has over-committed itself for a Sprint, who has to be present reviewing and adjusting the Sprint work selected? The Product Owner and the Development Team. For the purpose of transparency, when does Scrum say a new increment of working software must be available? At the end of every Sprint. Choose two responsibilities of a self-organizing Development Team: Choose 2 answers - Do the work planned in the Sprint Backlog. - Pull Product Backlog items for the Sprint. What is the purpose of a Sprint Review? To inspect the product increment with the stakeholders and collect feedback on next steps. Which of the following best describes an increment of working software? Additional features in a useable state that complement those delivered in previous iterations. Cross-functional teams are optimized to work on one technical layer of the system only (eg. GUI, database, middle tier, interfaces). False The CEO asks the Development Team to add a "very important" item to a Sprint that is in progress. What should the Development Team do? Inform the Product Owner so he/she can work with the CEO. During a Sprint Retrospective, for what is the Product Owner responsible? Participating as a Scrum Team member. A Scrum Master is keeping a list of open impediments, but it is growing and he/she has been able to resolve only a small portion of the impediments. Which three techniques would be most helpful in this situation? Choose 3 answers - Alerting management to the impediments and their impact. - Consulting with the Development Team. - Prioritizing the list and working on them in order. A member of the Development Team takes the Scrum Master aside to express his concerns about data security issues. What should the Scrum Master do? Ask the person to share the issue with the team as soon as possible. During the Sprint Retrospective, the Development Team proposes moving the Daily Scrum to only occur on Tuesdays and Thursdays. Which two are the most appropriate responses for the Scrum Master? Choose 2 answers - Learn why the Development Team wants this and work with them to improve the outcome of the Daily Scrum. - Coach the team on why the Daily Scrum is important as an opportunity to update the plan. The Scrum Master observes the Product Owner struggling with ordering the Product Backlog. What is an appropriate action for the Scrum Master to take? Offer the Product Owner help in understanding that the goal of ordering the Product Backlog is to maximize value. Which three of the following are true about Scrum? - Scrum is based on empirical process control theory. - Scrum is a framework for developing and sustaining complex products. - Each component of Scrum serves a specific purpose and is essential to Scrum success and your usage of Scrum to develop complex products. How should a Development Team deal with non-functional requirements? Ensure every increment meets them. Which two activities will a Product Owner engage in during a Sprint? Choose 2 answers - Work with the stakeholders. - Answer questions from the Development Team about items in the current Sprint. Which two things are appropriate for a Scrum Master to do if the Development Team doesn't have the engineering tools and infrastructure to completely finish each selected Product Backlog item? Choose 2 answers - Coach the Development Team to improve its skills, tools and infrastructure over time and adjust the Definition of Done accordingly. - Have the Development Team establish a Definition of Done that is actually possible to achieve given current circumstances. During a Sprint Retrospective, for what is the Scrum Master responsible? Participating as a Scrum team member and facilitating as requested and needed. The Product Backlog is ordered by? Importance, where the most important items are at the top at all times. Why should the Product Owner be present at the Daily Scrum? He/She doesn't need to be there. What is a Development Team responsible for? Choose 2 answers - Resolving internal team conflicts. - Organizing the work required to meet the Sprint Goal. The length of the Sprint should be? - Short enough to be able to synchronize the development work with other business events. - Short enough to keep the business risk acceptable to the Product Owner. - No more than one calendar month. The Scrum Team has been working on a product for nine Sprints. A new Product Owner comes in, understanding he is accountable for the Product Backlog. However, he is unsure about his responsibilities. Which two activities are part of the Product Owner role according to Scrum? Choose 2 answers - Ensuring that the most valuable functionality is produced first at all times. - Interacting with stakeholders. What are three ways Scrum promotes self-organization? Choose 3 answers - By removing titles for Development Team members. - By the Development Team deciding what work to do in a Sprint. - By being a lightweight framework. Why is the Daily Scrum held at the same time and same place? The consistency reduces complexity. Which of the following are true about the Sprint Review? Choose 2 answers - Stakeholders may attend - The Product Owner presents what backlog items are "Done" When does Inspection occur? Frequently, but not so often that it gets in the way of the work In the first part of the Sprint Planning meeting, what is accomplished? - Items are selected from the Product Backlog - The Development Team decides how much work can be accomplished - The Scrum Team defines the Sprint Goal What does Scrum mean by Transparency? The process is undertandable by all stakeholders What happens if all the necessary testing doesn't occur in a Sprint? A risk of not creating a potentially shippable product occurs If a customer really wants a feature added to a Sprint, how should the Development Team respond? Ask the Product Owner to work with the customer Backlog Grooming and Backlog Refinement are the same thing. True If the Development Team doesn't like the time of the Daily Scrum, what should the Scrum Master do? Let the Development Team come up with a new time When does Adaptation occur in Scrum? - After each inspection event - During Sprint Planning - In the Daily Scrum During a Sprint, when is new work or further decomposition of work added to the Sprint Backlog? During the Daily Scrum after the Development Team approves them. Scrum Master is a "management" position True What are some consequences if a Development Team does not have a consistent definition of done from Sprint to Sprint? - The Development team may not know how many Product Backlog items it can do in a Sprint. - The Product Owner may not know what he/she is inspecting at the Sprint Review. - The Product Owner may be unable to get gauge the progress toward his/her goals. - The Development Team may not know what work is entailed in completing selected Product Backlog items. Which of the following is an example of an increment of working software? Additional features that complement those delivered in previous iterations. Which three activities will a product owner likely engage in during a Sprint? Choose 3 answers Answer questions from the Development Team about items in the current Sprint Provide feedback. Work with the stakeholders. Which of the following might the Scrum Team discuss during a Sprint Retrospective? - Methods of communication - The way the Scrum team does Sprint Planning. - Skills needed to improve the Development Team's ability to deliver. - It's Definition of Done.
