22 Essential Scrum Questions and Answers for Aspiring Scrum Masters

The following 22 questions essentially cover everything Scrum involves; if you can answer all of them correctly, you already possess the basic qualities of a Scrum Master, though real competence also depends on experience because a Scrum Master works closely with people and many practical issues can only be understood through practice.

Your answers may differ, which is fine; the answers provided are based on my own experience, and your methods and interpretations might vary, reflecting Scrum's flexibility to help you find the process that best fits you rather than imposing a rigid workflow.

1. What are the benefits of adopting the Scrum model?

– Reduces the risk that changes pose to the system – Improves ROI (return on investment) – Enables continuous improvement – Allows rapid, continuous delivery of usable software products – Gives everyone a clear view of the usable product and drives ongoing enhancements throughout the iteration.

2. What organizational structure does Scrum include?

Scrum’s structure varies by project, but it typically uses 2‑4 week iterations and includes the following roles: – Scrum Master – Product Owner – Development Team

3. What is a user story in Scrum?

A user story is a short, usually one‑sentence description of a feature or functionality that captures a user’s need.

4. Which artifacts/tools are used in Scrum?

The main Scrum tools are: – Sprint Backlog – Product Backlog – Velocity Chart – Burn‑down Chart

5. Explain a Scrum sprint.

A sprint is a repeatable, standardized work cycle in which a Scrum team applies Scrum practices to develop a potentially shippable product increment, ready for review and improvement.

6. What is the optimal sprint length and how does it affect work?

Scrum typically uses 2‑4 week sprints; most teams choose a two‑week cycle because it makes planning realistic, allows the Product Owner enough time to reprioritize, and provides sufficient buffer for the team to focus on current work.

7. What is a Product Backlog?

Before a team can pull items into the Sprint Backlog, the Product Owner maintains a Product Backlog that contains new features, change requests, improvements, and defects, prioritized for future development. Items approved by the PO and team become Sprint Backlog items after possible decomposition and effort estimation.

8. What activities are performed in a Scrum planning meeting?

During planning, the team: – Analyzes the sprint’s work items and estimates effort – Breaks product backlog items into tasks – If capacity remains, selects additional high‑priority items – Clarifies unclear requirements with the Product Owner

9. What are the main responsibilities of a Scrum Master?

– Remove impediments so the team can meet sprint goals – Maximize team productivity – Introduce technical practices such as automation scripts, unit testing, and continuous integration – Facilitate collaboration between the team and the Product Owner – Ensure correct implementation of Scrum practices

10. What elements should a burn‑down chart contain?

A burn‑down chart should display work days on the horizontal axis, remaining work on the vertical axis, the ideal trend line, and the actual progress line.

11. List some shortcomings of Scrum.

– Difficult to control when project goals are unclear – Daily Scrum can feel pressure‑filled and consume time early on – Requires high technical and collaboration skills from team members – High tolerance for change can cause stakeholder discomfort – Exposes many issues; organizations with low change acceptance may experience significant disruption – Can trigger extensive transformation, leading to temporary chaos

12. What is Scrum of Scrums?

In large organizations, after the Daily Scrum, team leads meet in a Scrum of Scrums to coordinate across teams and plan joint progress.

13. What does “Increment” mean?

An Increment is the sum of all completed Product Backlog items during a sprint; at sprint end every Increment must be in a usable, potentially shippable state, regardless of whether the Product Owner decides to release it.

14. What is team velocity?

Velocity measures the amount of work a team can complete in a sprint, expressed in story points or business value. It is a key indicator of team efficiency.

15. What are Sashimi and Impediments?

Sashimi (originally “sashimi” meaning raw fish slices) is a term some teams use to denote “Done”; each team defines its own definition of Done at various levels (task, team, product). Impediments are obstacles that prevent the team from reaching the defined Done state, and the Scrum Master is primarily responsible for removing them.

16. What is Scrum Planning Poker?

Planning Poker is a quantitative estimation technique where team members use cards marked with the Fibonacci sequence to estimate effort or business value. Members reveal cards simultaneously, discuss the highest and lowest estimates, and converge on a consensus value.

17. What can a burn‑down chart reveal?

A burn‑down chart tracks sprint progress, allowing the team to see whether they are ahead or behind schedule. Teams typically review the latest chart at the end of the Daily Scrum and take corrective actions if needed.

18. What is the purpose of the Sprint Retrospective?

The Sprint Retrospective provides the team with a structured opportunity to reflect on the just‑finished sprint, identify improvements and shortcomings, and agree on actionable steps for continuous improvement.

19. How do Sprint and Iteration differ in Scrum?

“Iteration” is a generic term for any development cycle, which can be as small as a coding, compile, test, or refactor loop, or as large as a full planning‑development‑test‑release cycle. A “Sprint” is a specific Scrum iteration lasting 2‑4 weeks that includes planning, development, testing, regression, and release.

20. What does a story point represent in Scrum?

Story points quantify the relative size, complexity, and effort of a product backlog item using the Fibonacci sequence, allowing teams to estimate without directly using time units. By analyzing historical data, teams can later map story points to actual time to aid progress tracking.

21. When is Scrum not suitable?

Scrum may not work for very large teams that cannot be split into 5‑10‑person sub‑teams, or for cross‑departmental, geographically dispersed groups without reorganizing into feature‑oriented, co‑located teams.

22. What is a Daily Scrum?

A Daily Scrum is a short, stand‑up meeting where each team member answers three questions: what they did yesterday, what they plan today, and whether they face any impediments needing help. It is facilitated by the Scrum Master, who focuses on the meeting’s efficiency rather than evaluating the content of the answers.

Please follow the WeChat public account devopshub for more information on DevOps integration.

Click “Read Original” at the bottom left to visit the devopshub portal.