Scrum Interview Questions and Answers: Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. Scrum Interview Questions and Answers will help you in accessing your knowledge & skills as a Scrum Master or Product Owner.
Please read Agile Interview Questions and Answer for questions related to Agile Fundamentals.
Scrum Master Interview Questions and Answers – Part I : Click Here
Scrum Master Interview Questions and Answers – Part II : Click Here
Scrum Interview Questions and Answers
101. What may happen if a Sprint is longer than one calendar month?
Answer: Complexity may rise, Risk may increase & The definition of what is being built may change.
101. Which event is officially designated for the discussion about the possible changes to the marketplace or potential use of the product?
Answer: Sprint Review.
102. Code coverage informs us of?
Answer: The amount of code covered by tests.
103. What are the causes of naive technical debt?
Answer: Immature practices due to lack of knowledge and Irresponsible behavior.
104. What steps does test driven development follow?
Answer: Add a test. Make sure the test fails. Write some code. Make sure the test passes.
105. What happens when a Sprint is cancelled?
Answer: Any completed and “Done” Product Backlog items are reviewed. Incomplete Product Backlog Items are re-estimated and put back on the Product Backlog. Several top Product Backlog Items replace the obsolete items.
106. What is the input to the Sprint Planning? Select four.
Answer:
- The latest product Increment
- The projected capacity of the Development Team during the Sprint
- The Product Backlog
- Past performance of the Development Team
107. Why does Scrum use different terminology?
Answer: The new terminology is a constant reminder of the change the organization is going through.
108. Incremental delivery means?
Answer: Deploy functional increments over the course of the project.
109. Who developed Scrum?
Answer: Ken Schwaber and Jeff Sutherland developed Scrum.
110. What is Scrum Theory?
Answer: 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. Scrum employs an iterative, incremental approach to optimize predictability and control risk.
111. Name some Development Teams characteristics:
Answer: 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.
112. Name a few important Facts to remember about the size of the development team?
Answer: No less than 3 and no more than 9. 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 result in smaller productivity gains. Smaller Development Teams may encounter skill constraints during the Sprint, causing the Development Team to be unable to deliver a potentially releasable Increment. Having more than nine members requires too much coordination. Large Development Teams generate too much complexity for an empirical process to manage. The Product Owner and Scrum Master roles are not included in this count unless they are also executing the work of the Sprint Backlog.
113. Are the Product Owner and Scrum Master included in the size of the team?
Answer: The Product Owner and Scrum Master roles are not included in this count unless they are also executing the work of the Sprint Backlog.
114. What are good reasons to cancel a sprint?
Answer: A Sprint would be canceled if the Sprint Goal becomes obsolete. *This might occur if the company changes direction or if market or technology conditions change. *A Sprint should be canceled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense.
115. The good Sprint Review should have the following:
Answer: Attendees include the Scrum Team and key stakeholders invited by the Product Owner;
The Product Owner explains what Product Backlog items have been ‘Done’ and what has not been ‘Done’;
The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved;
The Development Team demonstrates the work that it has ‘Done’ and answers questions about the Increment;
The Product Owner discusses the Product Backlog as it stands. He or she projects likely completion dates based on progress to date (if needed);
The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning;
Review of how the marketplace or potential use of the product might have changed what is the most valuable thing to do next; and,
Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated release of the product.
116. What is the purpose of the Sprint Retrospective?
Answer: 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.
117. Is the product backlog Dynamic or Fixed?
Answer: Dynamic. The Product Backlog is a living artifact.
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.
118. When does Product Backlog refinement happen?
Answer: The Scrum Team decides how and when refinement is done.
Refinement usually consumes no more than 10% of the capacity of the Development Team.
Product Backlog items can be updated at any time by the Product Owner or at the Product Owner’s discretion.
119. What is a Burn-down Chart?
Answer: A chart showing the evolution of remaining effort against time. Burn-down charts are an optional implementation within Scrum to make progress transparent.
120. What is Burn-up Chart?
Answer: A chart showing the evolution of an increase in a measure against time. Burn-up charts are an optional implementation within Scrum to make progress transparent.
121. What is Emergence?
Answer: The process of the coming into existence or prominence of new facts or new knowledge of a fact, or knowledge of a fact becoming visible unexpectedly.
122. What is Empiricism?
Answer: Process control type in which only the past is accepted as certain and in which decisions are based on observation, experience, and experimentation. Empiricism has three pillars: transparency, inspection, and adaptation.
123. What is Engineering standards?
Answer: A shared set of development and technology standards that a Development Team applies to create releasable Increments of software.
124. What is Forecast (of functionality)?
Answer: The selection of items from the Product Backlog a Development Team deems feasible for implementation in a Sprint.
125. What is Ready?
Answer: A shared understanding by the Product Owner and the Development Team regarding the preferred level of description of Product Backlog items introduced at Sprint Planning.
Scrum Guide: Click Here
Disclaimer: All the content related to Scrum Guide is taken from scrumguides.org and is under the Attribution ShareAlike license of Creative Commons. Further information is accessible at https://creativecommons.org/licenses/by-sa/4.0/legalcode and also described in summary form at http://creativecommons.org/licenses/by-sa/4.0/.
Comments are closed.