GitHub Copilot Notes For Udemy Course

Complete Agile Scrum Master Certification Training Notes

Professional Scrum Master I (PSM I) Certification Preparation - 2024 Edition_

## 📚 Course Overview

This comprehensive training is designed to help you master the Scrum framework and Agile mindset, preparing you to pass the Professional Scrum Master I (PSM I) certification on your first attempt.

**🎯 Learning Objectives:**

- Master the Scrum framework and Agile principles
- Develop the mindset of a Professional Scrum Master
- Learn unique assessment tips and shortcuts for PSM I questions
- Practice with exclusive PSM I simulators
- Gain confidence through strategic learning approach

**📊 Study Plan:**

- **Week 1-2**: Foundation (Scrum Framework & Agile Mindset)
- **Week 3-4**: Implementation (Roles, Events, Artifacts)
- **Week 5-6**: Assessment Preparation (Practice & Strategy)
- **Week 7**: Final Review and Practice Tests

**🏆 Certification Details:**

- **Exam**: Professional Scrum Master I (PSM I)
- **Format**: Online, 80 questions, 60 minutes
- **Passing Score**: 85% (68 out of 80 questions correct)
- **Valid for**: Lifetime (no renewal required)

---

## 🏗️ 1. SCRUM FRAMEWORK FUNDAMENTALS

### What is Scrum?

Scrum is a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems.

### Three Pillars of Empiricism

1. **Transparency** - Work and challenges must be visible to those responsible for outcome
2. **Inspection** - Scrum artifacts and progress must be inspected frequently
3. **Adaptation** - If inspection reveals problems, adjustments must be made

### Five Scrum Values

1. **Commitment** - Dedicated to achieving team goals
2. **Courage** - Do the right thing and work on tough problems
3. **Focus** - Concentrate on Sprint work and team goals
4. **Openness** - Open about work and challenges
5. **Respect** - Respect each other as capable, independent people

### Definition of Done

- Shared understanding of what it means for work to be complete
- Ensures transparency and quality
- If multiple teams work on same product, they must have same Definition of Done

---

## 🧠 2. AGILE MINDSET AND PRINCIPLES

### The Agile Manifesto - Four Values

1. **Individuals and interactions** over processes and tools
2. **Working software** over comprehensive documentation
3. **Customer collaboration** over contract negotiation
4. **Responding to change** over following a plan

### Key Agile Principles

- Early and continuous delivery of valuable software
- Welcome changing requirements, even late in development
- Business people and developers work together daily
- Build projects around motivated individuals
- Face-to-face conversation is most efficient communication
- Working software is primary measure of progress
- Sustainable development pace
- Technical excellence and good design enhances agility
- Simplicity - maximize amount of work not done
- Self-organizing teams produce best results
- Regular reflection and adjustment

### Agile vs Traditional Approaches

**Traditional:** Sequential phases, heavy documentation, fixed scope, command and control
**Agile:** Iterative cycles, just enough documentation, flexible scope, self-organization

---

## 👥 3. SCRUM ROLES AND RESPONSIBILITIES

### The Scrum Team

- **One Scrum Master, One Product Owner, Developers (3-9 people)**
- Self-managing, cross-functional, no hierarchies
- Typically 10 or fewer people total

### Product Owner

**Primary Responsibility:** Maximizing the value of the product

**Key Accountabilities:**

- Developing and communicating Product Goal
- Creating and clearly communicating Product Backlog items
- Ordering Product Backlog items
- Ensuring Product Backlog is transparent and understood

**Critical Success Factors:**

- Available and engaged
- Empowered to make decisions
- Single person (not committee)
- Domain expertise
- Clear communication

### Developers (Development Team)

**Primary Responsibility:** Creating a usable Increment that meets Definition of Done every Sprint

**Key Accountabilities:**

- Participating in Sprint Planning and creating Sprint Backlog
- Conducting Daily Scrum
- Delivering potentially releasable Increment
- Ensuring quality through Definition of Done

**Team Characteristics:**

- Cross-functional skills
- Self-organizing
- Collective ownership
- T-shaped professionals
- Collaborative

### Scrum Master

**Primary Responsibility:** Ensuring Scrum is understood and enacted

**Serving the Scrum Team:**

- Coaching team members in self-management and cross-functionality
- Helping team focus on creating high-value Increments
- Removing impediments to team's progress
- Ensuring Scrum events are positive, productive, and timeboxed

**Serving the Product Owner:**

- Helping find techniques for effective Product Goal and backlog management
- Helping establish empirical product planning
- Facilitating stakeholder collaboration

**Serving the Organization:**

- Leading, training, and coaching organization in Scrum adoption
- Planning and advising Scrum implementations
- Helping understand empirical approach
- Removing barriers between stakeholders and teams

---

## ⏰ 4. SCRUM EVENTS AND CEREMONIES

### The Sprint (Container Event)

- **Duration:** 1 month or less, consistent length
- **Purpose:** Create potentially releasable Increment
- **Key Rules:** No changes that endanger Sprint Goal, quality doesn't decrease
- **Cancellation:** Only Product Owner can cancel (rare, when Sprint Goal becomes obsolete)

### Sprint Planning

- **Timebox:** 8 hours max (1-month Sprint), 4 hours (2-week Sprint)
- **Participants:** Entire Scrum Team
- **Three Topics:**
  1. **Why** is this Sprint valuable? (Sprint Goal)
  2. **What** can be Done this Sprint? (Sprint Backlog Selection)
  3. **How** will the chosen work get done? (Sprint Plan)

### Daily Scrum

- **Timebox:** 15 minutes (always, regardless of Sprint length)
- **Participants:** Developers only (others may observe)
- **Purpose:** Inspect progress toward Sprint Goal, adapt Sprint Backlog
- **Focus:** Sprint Goal progress, not status reporting

### Sprint Review

- **Timebox:** 4 hours max (1-month Sprint), 2 hours (2-week Sprint)
- **Participants:** Scrum Team + Stakeholders
- **Purpose:** Inspect Sprint outcome, determine future adaptations
- **Activities:** Demonstrate work, gather feedback, update Product Backlog

### Sprint Retrospective

- **Timebox:** 3 hours max (1-month Sprint), 1.5 hours (2-week Sprint)
- **Participants:** Scrum Team only
- **Purpose:** Plan ways to increase quality and effectiveness
- **Focus:** People, relationships, process, tools

### Product Backlog Refinement

- **Not a formal event:** Ongoing activity
- **Effort:** ~10% of Development Team capacity
- **Purpose:** Add detail, estimates, and order to Product Backlog items

---

## 📦 5. SCRUM ARTIFACTS

### Product Backlog

- **Definition:** Emergent, ordered list of what is needed to improve the product
- **Commitment:** Product Goal
- **Owner:** Product Owner
- **Characteristics:** Living document, ordered by value, detailed appropriately

### Sprint Backlog

- **Definition:** Sprint Goal + Selected Product Backlog items + Plan for delivery
- **Commitment:** Sprint Goal
- **Owner:** Developers
- **Updates:** Modified throughout Sprint as more is learned

### Increment

- **Definition:** Concrete stepping stone toward Product Goal
- **Commitment:** Definition of Done
- **Characteristics:** Additive to prior Increments, thoroughly verified, potentially releasable

### Commitments Explained

- **Product Goal:** Future state of product, target for planning
- **Sprint Goal:** Single objective for Sprint, provides guidance
- **Definition of Done:** Quality measures for product, shared understanding

---

## 🤝 6. SCRUM MASTER SKILLS AND TECHNIQUES

### Essential Skills

1. **Facilitation:** Running effective meetings and workshops
2. **Coaching:** Helping individuals and teams improve
3. **Teaching:** Educating about Scrum and Agile principles
4. **Systems Thinking:** Understanding organizational dynamics
5. **Conflict Resolution:** Helping resolve disagreements
6. **Change Leadership:** Leading organizational transformation

### Impediment Management

- **Identification:** Daily Scrum, retrospectives, observation
- **Resolution Strategies:** Direct action, escalation, facilitation, process change
- **Tracking:** Impediment backlog, age tracking, impact assessment

### Servant Leadership

- **Serves the team:** Exists to help team succeed
- **Facilitates rather than directs:** Helps team make decisions
- **Removes impediments:** Clears obstacles
- **Coaches and mentors:** Develops capabilities
- **Protects the team:** Shields from external interference

---

## 🎯 7. PSM I ASSESSMENT STRATEGY

### Exam Details

- **Questions:** 80 multiple choice
- **Duration:** 60 minutes
- **Passing Score:** 85% (68 correct)
- **Format:** Online, open book
- **Attempts:** Unlimited (pay for each after first)

### Study Strategy

**Phase 1 (Weeks 1-2): Foundation**

- Read Scrum Guide 5+ times
- Complete Scrum Open Assessment
- Focus on exact wording from Scrum Guide

**Phase 2 (Weeks 3-4): Application**

- Practice with scenarios
- Take multiple practice assessments
- Discuss concepts with others

**Phase 3 (Weeks 5-6): Assessment Prep**

- Intensive practice tests
- Time management practice
- Review weak areas

### Key Study Areas

1. **Scrum Framework (36%):** Roles, events, artifacts, empiricism
2. **Empirical Process Control (20%):** Transparency, inspection, adaptation
3. **Cross-Functional Teams (16%):** Self-organization, collaboration
4. **Lean Thinking (12%):** Value focus, waste elimination
5. **Scrum Master Role (16%):** Servant leadership, facilitation

### Test-Taking Strategies

- **Read carefully:** Look for keywords like "always," "never," "primary"
- **Use elimination:** Remove obviously wrong answers
- **Watch for Scrum Guide language:** Answers often use exact wording
- **Manage time:** 45 seconds average per question
- **Trust preparation:** First instinct often correct

---

## 📝 8. PSM I CHEAT SHEET

### Quick Reference Rules

**Team Size:**

- Scrum Team: 10 or fewer total
- Developers: 3-9 people

**Timeboxes (1-month Sprint):**

- Sprint Planning: 8 hours max
- Daily Scrum: 15 minutes (always)
- Sprint Review: 4 hours max
- Sprint Retrospective: 3 hours max

**What CAN Change During Sprint:**

- Sprint Backlog (by Developers)
- Understanding of work
- Technical approach

**What CANNOT Change:**

- Sprint Goal (without cancellation)
- Sprint length
- Team composition

**Role Accountabilities:**

- Product Owner: Maximizing product value
- Scrum Master: Ensuring Scrum effectiveness
- Developers: Creating valuable Increment

**Authority Rules:**

- Product Owner: Product decisions, Sprint cancellation
- Scrum Master: Process enforcement, impediment removal
- Developers: Technical decisions, Sprint Backlog management

---

## 🧠 9. PRACTICE QUESTIONS

### Sample Questions

**Q1: What are the three pillars of empiricism?**
A) Planning, Monitoring, Controlling
B) Transparency, Inspection, Adaptation
C) People, Process, Technology
D) Vision, Execution, Review

**Answer: B) Transparency, Inspection, Adaptation**

**Q2: Who is responsible for maximizing product value?**
A) Scrum Master B) Development Team C) Product Owner D) Project Manager

**Answer: C) Product Owner**

**Q3: What is the timebox for Daily Scrum?**
A) 30 minutes B) 15 minutes C) Variable D) 1 hour

**Answer: B) 15 minutes**

**Q4: Who can cancel a Sprint?**
A) Scrum Master B) Development Team C) Product Owner D) Any team member

**Answer: C) Product Owner**

**Q5: What is the commitment for the Product Backlog?**
A) Sprint Goal B) Product Goal C) Definition of Done D) Product Vision

**Answer: B) Product Goal**

---

## 🚫 10. COMMON MISTAKES TO AVOID

### Study Mistakes

- ❌ Relying only on experience vs Scrum Guide
- ❌ Memorizing without understanding
- ❌ Insufficient practice with official assessments
- ❌ Cramming before exam
- ❌ Ignoring time management

### Exam Mistakes

- ❌ Overthinking questions
- ❌ Mixing up role responsibilities
- ❌ Timeboxing confusion
- ❌ Definition of Done vs Acceptance Criteria confusion
- ❌ Sprint changes misconceptions

### Role Anti-Patterns

**Scrum Master:**

- ❌ Acting like project manager
- ❌ Making decisions for team
- ❌ Being team secretary

**Product Owner:**

- ❌ Product Owner by committee
- ❌ Technical proxy
- ❌ Unavailable Product Owner

**Developers:**

- ❌ Individual work ownership
- ❌ Waiting for assignment
- ❌ Skill silos

---

## 📖 11. SCRUM GUIDE 2020 - KEY POINTS

### Introduction

- Scrum is lightweight framework for complex product development
- Founded on empiricism and lean thinking
- Iterative, incremental approach

### Scrum Theory

- **Empiricism:** Knowledge from experience, decisions based on observation
- **Lean Thinking:** Reduces waste, focuses on essentials

### Scrum Team Structure

- No hierarchies or sub-teams
- Cross-functional and self-managing
- One Scrum Master, One Product Owner, Developers

### Events as Inspection Opportunities

- Each event is formal opportunity to inspect and adapt
- Events designed to provoke change when needed

### Artifacts and Transparency

- Each artifact contains commitment for transparency
- Commitments reinforce empiricism and Scrum values

---

## 📚 12. GLOSSARY OF KEY TERMS

**Empiricism:** Process control based on observation, experience, experimentation
**Sprint:** Time-boxed event serving as container for other events
**Product Backlog:** Emergent, ordered list of product improvements
**Sprint Backlog:** Sprint Goal + selected items + delivery plan
**Increment:** Concrete stepping stone toward Product Goal
**Definition of Done:** Formal description of Increment quality state
**Product Goal:** Future state of product, planning target
**Sprint Goal:** Single Sprint objective providing guidance
**Cross-functional:** Having all skills needed to create value
**Self-managing:** Team decides who, what, when, how
**Servant Leadership:** Leader serves team by enabling success
**Impediment:** Anything preventing team from achieving objectives
**Velocity:** Measure of work team completes per Sprint
**Timebox:** Maximum time allocated for event
**Transparency:** Visibility of process and work to responsible parties

---

## 💡 FINAL SUCCESS TIPS

### Before the Exam

1. Take Scrum Open Assessment until 100% consistently
2. Know Scrum Guide inside and out
3. Practice time management
4. Prepare optimal environment
5. Get good rest

### During the Exam

1. Read questions carefully
2. Look for Scrum Guide language
3. Use process of elimination
4. Manage time (45 seconds/question)
5. Trust your preparation

### Key Mindset

- Think empiricism and self-organization
- Focus on servant leadership
- Remember Scrum values in scenarios
- Consider value delivery over process
- Stay calm and confident

### Red Flags in Answers

- Command and control approaches
- Violating Scrum timeboxes
- Removing team autonomy
- Contradicting Scrum Guide

### Green Flags in Answers

- Emphasizing empiricism and adaptation
- Supporting self-organization
- Aligning with Scrum values
- Using exact Scrum Guide terminology

---

**🎓 Remember: The Scrum Guide is your ultimate reference. Master it, understand the WHY behind each element, and you'll succeed on your first attempt!**

_Good luck with your PSM I certification! 🏆_