Professional Scrum Master 1 (PSM1) Certification

Table of Contents

1. Introduction
2. Short Questions and Answers
3. Scrum Roles and Responsibilities
4. Scrum Events
5. Sprint Planning
6. Sprint Execution
7. Sprint Review
8. Common Challenges and Solutions

Introduction

The lecture focuses on the Professional Scrum Master 1 (PSM1) certification by discussing various questions and answers related to Scrum practices.

Short Questions and Answers

1. Should all increments from multiple Scrum teams be integrated every Sprint?

   • Correct Answer: Yes, otherwise the product owners and stakeholders may not be able to accurately inspect what is done

2. When can a development team cancel a Sprint?

   • Correct Answer: The development team can’t; only product owners can cancel Sprints

3. Output from Sprint planning for the development team’s target and direction?

   • Correct Answer: The Sprint Goal

4. How should the development team deal with non-functional requirements?

   • Correct Answer: Ensure every increment meets them

5. When is a Sprint over?

   • Correct Answer: When the time box expires

6. Does Scrum have a role called project manager?

   • Correct Answer: False

7. Ways to make non-functional requirements visible (Choose two):

   • Correct Answer: Add them to the product backlog and keep the product owner posted; Add them to the definition of done

8. Time required after a Sprint to prepare for the next Sprint?

   • Correct Answer: None, a new Sprint starts immediately following the end of the previous Sprint

9. Actions if highest ordered product backlog items are not well understood in Sprint planning (Choose two):

   • Correct Answer: Forecast likely product backlog items to meet the goal and create Sprint backlog; Discuss in the upcoming Sprint retrospective

10. Topics covered in Sprint planning?

    • Correct Answer: What can be done and how to do it

Scrum Roles and Responsibilities

1. Scrum Master: Ensures the Scrum framework is adopted and used properly
2. Product Owner: Manages and orders the product backlog
3. Development Team: Self-organizes to complete the selected work in the Sprint backlog

Scrum Events

1. Sprint Planning:

   • Set the Sprint Goal
   • Create Sprint Backlog

2. Sprint Execution:

   • Daily Scrum
   • Update progress

3. Sprint Review: Inspect the product increment with stakeholders and collect feedback

4. Sprint Retrospective: Inspect the past Sprint and plan for improvements

Sprint Planning

• Main concerns handled: What can be done in the Sprint and how to achieve it
• Duration: Time-boxed (typically 8 hours for a month-long Sprint)

Sprint Execution

• Daily Scrum: Time-boxed to 15 minutes; development team shares progress and impediments
• Ownership: All team members own the Sprint backlog items collaboratively
• Changes in Definition of Done: During Sprint Retrospective

Sprint Review

• Purpose: To inspect the product increment and gather feedback
• Participants: Scrum team and stakeholders

Common Challenges and Solutions

1. Non-functional requirements visibility

   • Add them to the product backlog
   • Include in the definition of done

2. Overloaded Sprint Backlog

   • Work with Product Owner to adjust the backlog

3. Stakeholder dissatisfaction

   • Use Sprint reviews actively to gather continuous feedback

4. Team coordination

   • Teams should integrate their increments every Sprint
   • Encourage self-organization and foster communication

Key Takeaways

• Essential for product owners to be actively engaged with the team.
• Transparency, inspection, and adaptation are core pillars of Scrum.
• All Scrum roles and events are essential for the proper execution of the Scrum framework.