In Scrum, there are three fundamental roles including the Product Owner, Scrum Master, and the Development Team.
Product Owner (PO)
The Product Owner is primarily responsible for maximizing the value of the product resulting from the work of the Development Team. They manage the product backlog, clearly express backlog items, and ensure that the backlog is transparent, visible, and clear to all.
Scrum Master (SM)
The Scrum Master is a servant-leader for the Development Team, facilitating Scrum as defined in Scrum Guide. They help everyone involved understand Scrum theory, practices, rules, and values. They also help the Development Team to self-organize, prevent distractions, and function optically.
Development Team (DT)
The Development Team is a self-organizing group responsible for delivering a potentially releasable Increment of “Done” product at the end of each Sprint.
Role | Key Responsibilities |
---|---|
PO | Manage the product backlog, stakeholders’ expectations and maximize product value. |
SM | Facilitate the Scrum process, resolve impediments, and build an ideal environment for the team. |
DT | Deliver a potentially releasable Increment of “Done” product at the end of each Sprint. |
Scrum Artifact
Scrum’s artefacts include the Product Backlog, the Sprint Backlog, and the Product Increment.
Product Backlog
The product backlog is an ordered list of everything needed in the product. It is the single source of requirements for any changes to be made to the product and is owned by the Product Owner.
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 meeting the sprint goal. The Development Team owns it.
Product Increment
The increment is the sum of all the product backlog items completed during a sprint and all previous sprints. It must be in a usable condition regardless of whether the Product Owner decides to release it.
Artifact | Description | Owner |
---|---|---|
Product Backlog | It’s an ordered list of requirements for changes to the product. | PO |
Sprint Backlog | It’s a plan for delivering the product and meeting the sprint goal. | DT |
Product Increment | Sum of all the backlog items completed during a sprint plus previous sprints. | – |
Hence, comprehensively understanding these Scrum roles and artefacts will not only cater to preparing for the Certified Scrum Professional – ScrumMaster (CSP-SM) exam but also equip you to manage and deliver successful Scrum projects efficiently.
Practice Test
True/False: In Scrum, the Product Owner is responsible for managing the project development team.
- True
- False
Answer: False
Explanation: The Product Owner is responsible for the product and the product backlog, not managing the development team. That is the role of Scrum Master.
Multiple Select: Which of the following are ceremonies in Scrum?
- A. Sprint Planning
- B. Sprint Review
- C. Sprint Retrospective
- D. Daily Scrum
- E. All of the above
Answer: E. All of the above
Explanation: All the options given are regular ceremonies in a Scrum process. They are essential for the effective functioning of Scrum.
Single Select: Who determines the priority of the product backlog in Scrum?
- A. Scrum Master
- B. Product Owner
- C. Development Team
- D. All of the above
Answer: B. Product Owner
Explanation: The priority of the product backlog is determined by the Product Owner, as they have the most context on the value each item brings to the project.
True/False: Agile and Scrum are synonymous and can always be used interchangeably.
- True
- False
Answer: False
Explanation: Agile is a broad concept encompassing various methodologies for project management, while Scrum is a specific set of practices within Agile framework.
Multiple Select: A Scrum Master is responsible for:
- A. Facilitating Scrum events as requested or needed
- B. Coaching the Development Team
- C. Building a collaborative culture
- D. All of above
Answer: D. All of above
Explanation: All mentioned roles are part of a Scrum Master responsibilities.
Single Select: What is Time Boxing in Scrum?
- A. Allocating a fixed time period to a planned activity
- B. Estimation of time for each task in a day
- C. Defining maximum time for a Scrum meeting
- D. None of the above
Answer: A. Allocating a fixed time period to a planned activity
Explanation: Time boxing is a time management technique where a time limit is assigned to an activity.
True/False: In Scrum, the product backlog items are ordered based on complexity.
- True
- False
Answer: False
Explanation: The product backlog items are prioritized based on factors like business value and urgency, not complexity.
Single Select: Who is responsible for approving or rejecting work results in Scrum?
- A. Scrum Master
- B. Development Team
- C. Product Owner
- D. Stakeholders
Answer: C. Product Owner
Explanation: It is the Product Owner’s responsibility to accept or reject work results during the Sprint Review.
True/False: Scrum advocates for a self-organizing team.
- True
- False
Answer: True
Explanation: Yes, Scrum teams are self-organizing, meaning they choose how best to accomplish their work, rather than being directed by others outside the team.
Single Select: In a Scrum, what is a “Sprint”?
- A. A fast-track learning course for the team
- B. A high-intensity coding phase
- C. The defined period in which specific work has to be completed
- D. A quick meeting at the start of each day
Answer: C. The defined period in which specific work has to be completed
Explanation: In Scrum, a Sprint is the time boxed period where specific work is completed and made ready for review.
Interview Questions
What is Scrum?
Scrum is an Agile development method used primarily in software development where development is executed in small steps with regular feedback and adjustments.
Who is responsible for managing the product backlog in Scrum?
The Product Owner is responsible for managing the product backlog in Scrum.
What is a Sprint in Scrum?
A Sprint is a time-boxed period where specific work has to be completed and made ready for review.
Name the three artifacts in Scrum?
The three artifacts in Scrum are Product Backlog, Sprint Backlog, and Product Increment.
What is the role of the Scrum Master?
The Scrum Master is a servant-leader for the Scrum Team. They help to remove impediments for the team and ensure the Scrum process is followed.
What are User Stories in Scrum?
User Stories are short, simple descriptions of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system.
What is a daily Scrum meeting?
A daily Scrum meeting, or a daily stand-up, is a 15-minute meeting held by the Scrum team to quickly discuss the work to be done that day and any potential obstacles.
What does “velocity” mean in Scrum?
Velocity in Scrum refers to the amount of work a team can complete during a single Sprint, usually estimated in story points.
Who are the members of a Scrum team?
A Scrum team typically consists of a Product Owner, Scrum Master, and the Development Team.
What are the five events in Scrum?
The five events in Scrum are the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
What is the purpose of a 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.
What is the “Definition of Done” in Scrum?
The ‘Definition of Done’ is a set of agreed criteria that must be met before a product increment is considered ‘done’.
What is meant by “backlog refinement” in Scrum?
Backlog refinement is when the Product Owner and some, or all, of the rest of the team review items on the backlog to ensure the backlog contains the appropriate items, that they are prioritized, and that the items at the top of the backlog are ready for delivery.
Who can cancel a Sprint in Scrum?
Only the Product Owner has the authority to cancel a Sprint in Scrum.
What is “Technical Debt” in Scrum?
Technical debt is the extra development work that arises when code that is easy to implement in the short run is used instead of applying the best overall solution. It reflects the implied cost of rework needed in future to rectify the hasty solutions.