The goal of this 6-week study plan is to develop a deep and practical understanding of Scrum at an advanced level and successfully pass the PSM II certification exam. This plan will help you:

1. Master the Scrum Framework beyond the basics.
2. Enhance your ability to coach and facilitate Agile teams as a Scrum Master.
3. Develop expertise in scaling Scrum and managing Agile organizations.
4. Apply Agile leadership and servant leadership principles in real-world scenarios.
5. Be fully prepared for the PSM II exam, including scenario-based questions.

Study Methods Used:

• Pomodoro Technique: Each study session is 25 minutes, followed by a 5-minute break. Every four sessions, take a 15-minute break.
• Forgetting Curve Review: Planned revisions at 1-day, 1-week, and 1-month intervals to reinforce memory retention.
• Active Recall: Test yourself by explaining concepts in your own words and applying them in exercises.
• Spaced Repetition: Regularly reviewing previous topics to ensure long-term retention.
• Practical Application: Using real-world case studies, mock scenarios, and self-assessment quizzes to strengthen understanding.

Week 1: Understanding and Applying the Scrum Framework

Goal:

Develop a strong foundational and advanced understanding of Scrum, including principles, roles, artifacts, and events.

Study Schedule & Tasks

Day 1: Scrum Framework Overview

Goal: Gain a clear understanding of Scrum’s foundation and its guiding principles.

Tasks:

1. Read the Scrum Guide (Scrum.org) thoroughly. Underline key sections and write a one-page summary explaining the core of Scrum.
2. Identify Scrum Values (Commitment, Focus, Openness, Respect, and Courage) and write real-world examples of how each value is applied in teams.
3. Active Recall Exercise: Close your notes and explain Scrum’s foundation from memory.
4. 10-Question Quiz: Answer multiple-choice questions on the Scrum Framework, values, and principles.
5. Reflection: What was the most surprising concept about Scrum for you? Write a short paragraph.

Day 2: Empirical Process Control & Scrum Artifacts

Goal: Understand Transparency, Inspection, and Adaptation and their role in Scrum.

Tasks:

1. Study Empirical Process Control (Transparency, Inspection, and Adaptation) and write an example of how each principle is applied in Scrum Teams.
2. Deep dive into Scrum Artifacts:
   • Product Backlog
   • Sprint Backlog
   • Increment
   • Definition of Done (DoD)
3. Case Study Exercise: Analyze two real-world Scrum teams and identify how they applied empirical process control.
4. Mock Sprint Planning Session: Select Product Backlog Items (PBIs) and define a Sprint Goal based on a hypothetical project.
5. Spaced Repetition Review: Revisit Day 1 concepts and test recall by summarizing Scrum Values and Principles without notes.

Day 3: Scrum Roles and Responsibilities

Goal: Understand the roles and responsibilities of the Scrum Master, Product Owner, and Developers.

Tasks:

1. Compare Scrum roles vs. traditional project management roles and note key differences.
2. Servant Leadership Deep Dive:
   • Read about Servant Leadership and write down three ways a Scrum Master applies it.
   • Reflect on how Servant Leadership differs from traditional leadership.
3. Real-World Application:
   • Identify five ways a Scrum Master empowers teams.
   • Explain how a Scrum Master removes impediments in an Agile environment.
4. Role-Playing Exercise: Answer three scenario-based questions on Scrum Master decision-making.
5. Case Study: Analyze how Scrum Masters influenced successful Agile transformations.

Day 4: Scrum Events Deep Dive

Goal: Gain a comprehensive understanding of Scrum Events, their purpose, and best practices.

Tasks:

1. Study each Scrum Event (Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, Sprint).
   • Define the goal, timebox, participants, and outputs of each event.
   • Identify common anti-patterns and write solutions for them.
2. Daily Scrum Exercise:
   • Conduct a mock Daily Scrum meeting, ensuring time-boxing and alignment with Sprint Goals.
   • Analyze why Daily Scrums fail and how to improve them.
3. Sprint Retrospective Simulation:
   • Choose a retrospective format (e.g., Start-Stop-Continue) and simulate a retrospective for a past project.
4. Write three key improvements a Scrum Master can implement to enhance Sprint Reviews.
5. Spaced Repetition Review: Revisit Day 2 concepts (Empirical Process Control & Scrum Artifacts) and summarize key points from memory.

Day 5: Definition of Done (DoD) & Technical Excellence

Goal: Understand how a well-defined DoD enhances quality and product increment readiness.

Tasks:

1. Read about the Definition of Done (DoD) and write five key elements of a strong DoD.
2. Compare Good vs. Bad DoD Examples:
   • Analyze how strong vs. weak DoD impacts product quality.
3. Deep dive into Continuous Integration (CI/CD) and Agile Testing:
   • Read about CI/CD in Agile development and explain how it ensures high-quality software delivery.
   • Explore Test-Driven Development (TDD) & Behavior-Driven Development (BDD).
4. Self-Assessment Exercise: Compare your team’s Definition of Done to industry standards.
5. Active Recall: Without referring to notes, explain why a strong DoD prevents technical debt.

Day 6: Case Study & Application

Goal: Apply Scrum knowledge through real-world analysis and problem-solving exercises.

Tasks:

1. Read and analyze three Scrum implementation case studies: Identify successes, challenges, and key lessons.
2. Answer Reflection Questions:
   • What was the biggest obstacle faced in each case study?
   • How did the Scrum Master help resolve the issue?
   • What alternative strategies could have been applied?
3. Problem-Solving Exercise: Given a failing Agile team scenario, suggest three changes a Scrum Master could implement.
4. Review all quizzes and notes from the week.
5. Prepare for a self-explaining session:
   • Teach Scrum Framework concepts to yourself or a study partner.

Day 7: Weekly Review & Reflection

Goal: Consolidate learning through review, practice, and self-assessment.

Tasks:

1. Revise all Week 1 topics using notes, mind maps, or flashcards.
2. Conduct a self-explanation session: Explain all Scrum concepts out loud as if teaching a class.
3. Take a full-length practice test (Scrum Open Assessment from Scrum.org) and analyze incorrect answers.
4. Identify weak areas and revisit those topics.
5. Plan for Week 2: Developing People and Teams.

Week 2: Developing People and Teams

Goal:

Gain expertise in coaching, team facilitation, and leadership to support and empower Scrum Teams.

Study Schedule & Tasks

Day 8: High-Performing Scrum Teams

Goal: Understand team dynamics, self-organization, and collaboration.

Tasks:

1. Read about High-Performing Scrum Teams and write a summary of their key characteristics.
2. Study Tuckman’s Team Development Model (Forming, Storming, Norming, Performing, Adjourning) and analyze:
   • How does each stage impact Scrum Teams?
   • What role does the Scrum Master play at each stage?
3. Self-Assessment Exercise:
   • Reflect on a team you’ve worked with (or a hypothetical team).
   • Identify which stage the team was in and what actions a Scrum Master could take to help them progress.
4. Real-World Example Review:
   • Research two case studies of high-performing Agile teams and identify three success factors they had.
5. Quiz: Take a 10-question quiz on team development and Scrum Team collaboration.

Day 9: Scrum Master’s Role in Team Growth

Goal: Learn how the Scrum Master fosters self-organization, trust, and servant leadership.

Tasks:

1. Read about Servant Leadership and write down five ways a Scrum Master serves the team.
2. Compare Traditional Leadership vs. Servant Leadership:
   • What are the key differences?
   • How does a Scrum Master apply Servant Leadership in practice?
3. Conflict Resolution Deep Dive:
   • Learn about healthy vs. unhealthy conflict in Scrum Teams.
   • Study techniques like Active Listening, Nonviolent Communication (NVC), and the Thomas-Kilmann Conflict Model.
4. Scenario-Based Role Play:
   • Given a team conflict situation, write how a Scrum Master should respond to encourage collaboration.
5. Team Coaching Simulation:
   • Imagine you are coaching a team that resists Scrum.
   • Write three strategies you would use to help them adopt Agile practices.
6. Quiz: Take a 10-question quiz on coaching and Servant Leadership.

Day 10: Agile Facilitation & Coaching

Goal: Master coaching techniques and facilitation methods for Scrum events.

Tasks:

1. Read about Coaching vs. Mentoring vs. Managing and define when to use each approach in Scrum.
2. Study Powerful Questioning Techniques in coaching, including:
   • Open-ended questions to encourage self-reflection.
   • The GROW Model (Goal, Reality, Options, Will) for coaching conversations.
3. Facilitation Techniques for Scrum Events:
   • Learn how to facilitate Sprint Planning, Sprint Reviews, and Retrospectives.
   • Study techniques like Silent Brainstorming, Dot Voting, and Liberating Structures.
4. Interactive Exercise:
   • Select one Sprint Retrospective format and design a mock retrospective agenda.
5. Real-World Case Study:
   • Analyze how an experienced Scrum Master used facilitation to improve a dysfunctional team.
6. Quiz: Take a 10-question quiz on Agile coaching and facilitation techniques.

Day 11: Sprint Retrospectives & Continuous Improvement

Goal: Understand how Retrospectives drive team improvement and innovation.

Tasks:

1. Read about the role of Sprint Retrospectives and write why they are crucial for team improvement.
2. Study Different Retrospective Formats:
   • Start-Stop-Continue
   • 4Ls (Liked, Learned, Lacked, Longed for)
   • Mad-Sad-Glad
   • Sailboat Exercise
3. Facilitation Exercise:
   • Choose a retrospective format.
   • Prepare a mock Retrospective for a Sprint that had delays and technical challenges.
4. Kaizen & Continuous Improvement:
   • Learn about Kaizen principles and how they apply to Agile teams.
   • Identify three ways a Scrum Master fosters continuous improvement.
5. Self-Reflection Exercise:
   • Identify one area where you can improve as a Scrum Master and write an action plan.

Day 12: Conflict Resolution & Team Challenges

Goal: Learn how to handle team conflicts, dysfunctions, and performance issues.

Tasks:

1. Identify Common Scrum Team Challenges:
   • Lack of collaboration
   • Low accountability
   • Stakeholder interference
   • Frequent scope changes
2. Study Conflict Resolution Models:
   • Thomas-Kilmann Conflict Model (Competing, Collaborating, Avoiding, Accommodating, Compromising).
   • Conflict Mapping (Identify root causes).
3. Scenario-Based Practice:
   • Choose a team dysfunction scenario and write a Scrum Master’s intervention strategy.
4. Case Study Analysis:
   • Review how a Scrum Master helped a struggling team become high-performing.
5. Spaced Repetition Review: Revisit Day 8 and 9 concepts through active recall.

Day 13: Case Study & Mock Scenario

Goal: Apply Scrum Master skills in real-world case studies and situational questions.

Tasks:

1. Read two real-world case studies of team transformation in Agile environments.
2. Analyze:
   • What problems did the teams face?
   • What actions did the Scrum Masters take?
   • What alternative solutions could have been applied?
3. Write Your Own Case Study:
   • Describe a Scrum Team experiencing difficulties and propose an intervention strategy.
4. Scenario-Based Questioning:
   • Answer three advanced situational questions on coaching and facilitation.

Day 14: Weekly Review & Quiz

Goal: Consolidate learning through review, practice, and self-assessment.

Tasks:

1. Review all Week 2 concepts using notes, mind maps, or flashcards.
2. Conduct a self-explanation session: Teach Agile coaching and facilitation concepts aloud without notes.
3. Take a 20-question practice test on coaching, facilitation, and leadership.
4. Analyze incorrect answers and reinforce weak areas.
5. Plan for Week 3: Managing Products with Agility.

Week 3: Managing Products with Agility

Goal:

Gain expertise in Agile product management, backlog management, prioritization techniques, and stakeholder collaboration.

Study Schedule & Tasks

Day 15: Product Ownership & Value Delivery

Goal: Understand how product ownership aligns with Agile value delivery.

Tasks:

1. Read about Product Ownership in Scrum:
   • What is the role of a Product Owner (PO)?
   • How does the PO collaborate with the Scrum Master and Developers?
2. Product Vision & Strategy Exercise:
   • Define what makes a strong product vision.
   • Study examples of good and bad product visions.
   • Create a mock product vision statement for an Agile project.
3. Value Delivery in Agile:
   • Study how Agile prioritizes customer and business value over scope and deadlines.
   • Read about Lean Thinking and the concept of MVP (Minimum Viable Product).
   • Identify three ways Scrum ensures high-value delivery.
4. Case Study:
   • Analyze a real-world Product Owner’s role in delivering a successful product.
5. Quiz: Take a 10-question quiz on product ownership concepts.

Day 16: Product Backlog & Prioritization

Goal: Master backlog management techniques to help Scrum teams stay focused and aligned.

Tasks:

1. Read about the Product Backlog:
   • Study how the backlog evolves through refinement and prioritization.
   • Learn how stakeholders influence backlog items.
2. Prioritization Techniques:
   • MoSCoW (Must, Should, Could, Won’t Have)
   • WSJF (Weighted Shortest Job First)
   • Impact Mapping
   • Cost of Delay
3. Backlog Refinement Exercise:
   • Create a mock product backlog with at least 10 items.
   • Use MoSCoW and WSJF to prioritize backlog items.
   • Identify which items should be split into smaller, manageable stories.
4. Common Backlog Issues & Solutions:
   • Address overloaded backlogs.
   • Identify unclear acceptance criteria.
   • Solve issues with low stakeholder engagement.
5. Quiz: Take a 10-question quiz on backlog refinement and prioritization.

Day 17: Customer Collaboration & Stakeholder Engagement

Goal: Learn how to engage stakeholders and collaborate effectively in Agile environments.

Tasks:

1. Study the Importance of Stakeholder Engagement in Scrum:
   • Identify different types of stakeholders.
   • Learn how to balance competing stakeholder demands.
2. Sprint Review as a Collaboration Tool:
   • Read how Sprint Reviews encourage continuous feedback.
   • Identify common Sprint Review mistakes and solutions.
   • Plan a mock Sprint Review agenda for an ongoing project.
3. Handling Difficult Stakeholders:
   • Study common stakeholder challenges, including:
     • Unrealistic expectations
     • Resistance to Agile practices
     • Scope changes
   • Write down three strategies to manage difficult stakeholders.
4. Stakeholder Role-Playing Exercise:
   • Assume the role of a Scrum Master and engage in a mock discussion with a demanding stakeholder.
   • Respond to questions about backlog priorities and project progress.
5. Quiz: Take a 10-question quiz on stakeholder engagement.

Day 18: Forecasting & Agile Roadmaps

Goal: Learn how to create Agile roadmaps and improve forecasting for product development.

Tasks:

1. Understand Agile Forecasting:
   • How does Agile approach forecasting differently from traditional methods?
   • Why do fixed long-term deadlines not work in Agile?
2. Types of Agile Roadmaps:
   • Feature-Based Roadmap
   • Outcome-Based Roadmap
   • Now-Next-Later Roadmap
   • Lean Roadmaps
3. Practical Roadmap Exercise:
   • Create an Agile roadmap for a mock product development project.
   • Define short-term, medium-term, and long-term objectives.
4. Velocity-Based Forecasting:
   • Study velocity and capacity planning.
   • Understand how past Sprint velocity helps teams forecast future work.
5. Monte Carlo Simulation for Predictability:
   • Learn about probabilistic forecasting.
   • Study how Monte Carlo simulations improve predictability.
6. Quiz: Take a 10-question quiz on Agile forecasting and roadmaps.

Day 19: Technical Debt & Quality Management

Goal: Learn how to manage technical debt and ensure product quality in Agile.

Tasks:

1. Understand Technical Debt:
   • What is technical debt, and how does it accumulate?
   • How does technical debt affect Agile delivery and team performance?
2. Managing Technical Debt:
   • Learn strategies like refactoring, automation, and incremental improvements.
   • Study how a Scrum Master helps teams balance new features with tech debt management.
3. Quality in Agile:
   • Read about Test-Driven Development (TDD), Behavior-Driven Development (BDD), and Continuous Integration/Continuous Delivery (CI/CD).
   • Learn how Definition of Done (DoD) enforces quality standards.
4. Risk Management Exercise:
   • Identify three potential risks in an Agile project.
   • Write an action plan for managing these risks.
5. Quiz: Take a 10-question quiz on technical debt and quality management.

Day 20: Case Study – Managing Agile Products

Goal: Analyze real-world Agile product management case studies.

Tasks:

1. Read two case studies about Agile teams managing large-scale products.
2. Identify key challenges faced by Product Owners:
   • Managing stakeholder expectations
   • Handling backlog prioritization conflicts
   • Balancing technical debt vs. new features
3. Write an analysis:
   • What worked well?
   • What could have been done differently?
   • How did Scrum Masters help ensure success?
4. Mock Discussion:
   • Assume the role of a Scrum Master.
   • Prepare a 5-minute briefing to explain Agile backlog prioritization to a leadership team.
5. Review & Summarize:
   • Summarize key learnings from Days 15-20.

Day 21: Weekly Review & Quiz

Goal: Reinforce learning through review, testing, and self-explanation.

Tasks:

1. Review all Week 3 concepts using notes, mind maps, or flashcards.
2. Self-Explanation Exercise: Teach Agile product management concepts aloud without notes.
3. Take a full-length practice test (Scrum Open Assessment + additional questions on Agile product management).
4. Analyze incorrect answers and reinforce weak areas.
5. Plan for Week 4: Developing and Delivering Products Professionally.

Week 4: Developing and Delivering Products Professionally

Goal:

Develop a deep understanding of Agile engineering practices, including Test-Driven Development (TDD), CI/CD, DevOps, and Definition of Done (DoD).

Study Schedule & Tasks

Day 22: Definition of Done (DoD) & Quality Assurance

Goal: Understand the importance of a strong Definition of Done (DoD) and its role in quality assurance.

Tasks:

1. Read about the Definition of Done (DoD) and explain why it is a critical part of Scrum.
2. Compare Good vs. Bad DoD Examples:
   • How does a weak DoD lead to technical debt?
   • What does a strong DoD include?
3. Assess an Example DoD:
   • Given a sample DoD, identify three areas for improvement.
   • Rewrite the DoD to ensure it meets Scrum quality standards.
4. Connection Between DoD and Agile Testing:
   • Study Acceptance Criteria, Unit Testing, and Automated Testing.
   • Explain how DoD ensures quality in Agile products.
5. Mock Exercise:
   • Assume the role of a Scrum Master.
   • Facilitate a team discussion to improve their DoD.
6. Quiz: Take a 10-question quiz on DoD and quality assurance.

Day 23: Agile Engineering Practices

Goal: Learn about modern Agile software engineering techniques that ensure high-quality products.

Tasks:

1. Test-Driven Development (TDD):
   • Study the Red-Green-Refactor cycle.
   • Write a simple test case before implementation (pseudo-code allowed).
2. Behavior-Driven Development (BDD):
   • Read about Given-When-Then format for defining test cases.
   • Write a BDD scenario for a login feature.
3. Continuous Integration (CI):
   • Learn how frequent code integration and automated testing prevent defects.
   • Study Jenkins, GitHub Actions, and GitLab CI/CD pipelines.
4. Refactoring & Technical Debt Reduction:
   • Identify three common technical debt issues.
   • Write a plan for gradual refactoring without disrupting development.
5. Mock Exercise:
   • Review a code snippet with technical debt.
   • Suggest refactoring improvements based on Agile engineering principles.
6. Quiz: Take a 10-question quiz on Agile engineering best practices.

Day 24: Continuous Delivery & DevOps

Goal: Learn about automated deployment strategies, DevOps culture, and continuous delivery pipelines.

Tasks:

1. Understand DevOps & Continuous Delivery:
   • What is DevOps, and how does it enhance Scrum?
   • Why do Scrum and DevOps complement each other?
2. Study the Continuous Delivery Pipeline:
   • Learn about Build, Test, Deploy, and Release automation.
   • Study how Blue-Green Deployment and Canary Releases reduce risk.
3. Infrastructure as Code (IaC):
   • Read about Terraform, Kubernetes, and Docker for Agile infrastructure.
   • Understand how automation improves deployment efficiency.
4. Security & DevSecOps:
   • Learn how to integrate security testing into CI/CD pipelines.
   • Study automated security scanning tools (e.g., SonarQube, OWASP ZAP).
5. Mock Exercise:
   • Design a basic DevOps pipeline for a Scrum project (outline only).
   • Identify potential bottlenecks and solutions.
6. Quiz: Take a 10-question quiz on DevOps and Continuous Delivery.

Day 25: Scaling Agile Engineering Practices in Large Organizations

Goal: Understand how to scale Agile technical practices across multiple teams.

Tasks:

1. Learn About Scaling Agile Engineering:
   • Study LeSS, SAFe, and Nexus frameworks and their technical implications.
   • Identify how CI/CD pipelines are adapted in enterprise environments.
2. Cross-Team Collaboration in Large-Scale Scrum:
   • How do teams synchronize releases and integrate work?
   • Study Nexus Integration Team’s role in scaled Scrum.
3. Feature Toggles & Branching Strategies:
   • Learn about Git Feature Branching vs. Trunk-Based Development.
   • Understand how Feature Toggles enable gradual rollouts.
4. Mock Exercise:
   • Create a plan for cross-team technical collaboration.
   • Define how multiple teams should manage dependencies and shared codebases.
5. Quiz: Take a 10-question quiz on scaling Agile engineering.

Day 26: Risk Management in Agile Development

Goal: Learn how to identify, assess, and mitigate risks in Agile projects.

Tasks:

1. Study Agile Risk Management Approaches:
   • How does Scrum manage risk differently from Waterfall?
   • Why are short feedback loops essential for risk mitigation?
2. Identify Common Agile Risks:
   • Scope creep
   • Defects in production
   • Delayed feedback from stakeholders
   • Infrastructure failures
3. Write a Risk Response Plan:
   • Given a real-world Agile project scenario, write a risk response strategy.
   • Define which Scrum events help mitigate risks.
4. Mock Exercise:
   • Facilitate a risk discussion in a Sprint Retrospective.
5. Quiz: Take a 10-question quiz on Agile risk management.

Day 27: Case Study & Mock Scenario

Goal: Apply Agile technical practices and DevOps knowledge in real-world situations.

Tasks:

1. Read two case studies on how companies implemented Agile engineering practices.
2. Analyze:
   • What challenges did they face?
   • What technical solutions helped them succeed?
   • What role did the Scrum Master play in improving technical practices?
3. Write Your Own Case Study:
   • Describe a Scrum Team struggling with deployment delays.
   • Propose an action plan using CI/CD and DevOps practices.
4. Scenario-Based Questioning:
   • Answer three advanced situational questions on Agile technical challenges.

Day 28: Weekly Review & Quiz

Goal: Reinforce learning through review, testing, and self-explanation.

Tasks:

1. Review all Week 4 concepts using notes, mind maps, or flashcards.
2. Self-Explanation Exercise: Teach Agile engineering concepts aloud without notes.
3. Take a full-length practice test (Scrum Open Assessment + engineering-focused questions).
4. Analyze incorrect answers and reinforce weak areas.
5. Plan for Week 5: Evolving the Agile Organization.

Week 5: Evolving the Agile Organization

Goal:

Develop a deep understanding of scaling Agile, organizational agility, leadership transformation, and Agile change management.

Study Schedule & Tasks

Day 29: The Role of the Scrum Master in Organizational Agility

Goal: Understand how the Scrum Master drives organizational agility beyond the Scrum Team.

Tasks:

1. Read about Organizational Agility:
   • What does Agile transformation mean for an organization?
   • How does the Scrum Master support agility beyond the team level?
2. Scrum Master’s Role in Agile Transformation:
   • Facilitating cross-team collaboration.
   • Removing organizational impediments.
   • Coaching leadership on Agile principles.
3. Organizational Resistance to Agile:
   • Identify three common reasons organizations resist Agile.
   • Write solutions to overcome resistance.
4. Mock Exercise:
   • Assume the role of a Scrum Master helping a non-Agile team transition to Scrum.
   • Define three steps to ease the transition.
5. Quiz: Take a 10-question quiz on organizational agility.

Day 30: Organizational Culture & Agile Mindset

Goal: Learn how to shift traditional corporate cultures toward an Agile mindset.

Tasks:

1. Read about Traditional vs. Agile Organizations:
   • Siloed departments vs. cross-functional collaboration.
   • Hierarchical vs. empowered decision-making.
   • Fixed plans vs. adaptive, iterative planning.
2. Cultural Shifts for Agile Adoption:
   • How can Scrum Masters influence leadership thinking?
   • What strategies help break down resistance to Agile?
3. Common Organizational Anti-Patterns:
   • Command-and-control culture.
   • Lack of trust in self-managing teams.
   • Waterfall disguised as Agile (Agile in name only).
4. Self-Reflection Exercise:
   • Identify three cultural challenges in your organization (or a case study).
   • Propose solutions to encourage Agile values.
5. Quiz: Take a 10-question quiz on Agile mindset and cultural transformation.

Day 31: Scaling Scrum in Large Organizations

Goal: Learn how to scale Scrum beyond single teams using Agile frameworks.

Tasks:

1. Understand Scaling Frameworks:
   • LeSS (Large Scale Scrum): Lightweight, simple scaling.
   • Nexus: Focuses on integration across multiple Scrum Teams.
   • SAFe (Scaled Agile Framework): A structured approach for enterprises.
2. Key Challenges in Scaling Agile:
   • Cross-team dependencies.
   • Coordination and alignment of work.
   • Maintaining Agile values while scaling.
3. Mock Exercise:
   • Choose a scaling framework for a company with 10 Scrum Teams.
   • Define how teams will coordinate work and integrate increments.
4. Case Study:
   • Read how a company scaled Agile across multiple teams.
   • Identify lessons learned and Scrum Master’s role.
5. Quiz: Take a 10-question quiz on scaling Scrum.

Day 32: Agile Leadership & Servant Leadership

Goal: Learn how leaders must adapt to support Agile transformations.

Tasks:

1. Read about Servant Leadership in Agile Organizations:
   • How does a Servant Leader differ from a traditional leader?
   • What are three key actions Agile leaders must take?
2. Leadership in Agile vs. Traditional Companies:
   • Top-down decision-making vs. empowering teams.
   • Focus on outcomes vs. micromanaging tasks.
3. How Scrum Masters Influence Leadership:
   • Educating managers on self-organizing teams.
   • Encouraging leaders to focus on outcome-based measurements.
4. Mock Exercise:
   • You are coaching a traditional manager transitioning to Agile.
   • Write three conversation points to explain the Agile leadership mindset.
5. Quiz: Take a 10-question quiz on Agile leadership.

Day 33: Organizational Agility Metrics

Goal: Learn how to measure Agile transformation success beyond individual teams.

Tasks:

1. Study Organizational Agility Metrics:
   • Customer Satisfaction (Net Promoter Score).
   • Time-to-Market for product delivery.
   • Employee Engagement (team morale and job satisfaction).
   • Adaptability Index (how quickly an organization responds to change).
2. Common Pitfalls in Agile Metrics:
   • Avoiding vanity metrics (e.g., counting story points per developer).
   • Ensuring metrics drive real improvement, not just reporting.
3. Self-Reflection Exercise:
   • Choose one metric and create a plan for tracking it in an Agile team.
4. Case Study:
   • Analyze how a company used Agile metrics to drive better business decisions.
5. Quiz: Take a 10-question quiz on Agile metrics.

Day 34: Agile Beyond Software Development

Goal: Understand how Scrum and Agile practices apply to non-IT fields.

Tasks:

1. Read how Agile is used outside software development:
   • Marketing: Agile campaign planning, A/B testing.
   • HR (PeopleOps): Agile hiring, iterative performance reviews.
   • Finance: Rolling forecasts and adaptive budgeting.
   • Operations: Lean process improvements.
2. Case Study:
   • Read how a non-IT company successfully implemented Agile.
   • Identify key lessons learned.
3. Mock Exercise:
   • Choose one non-IT industry and create an Agile implementation plan.
4. Quiz: Take a 10-question quiz on Agile beyond IT.

Day 35: Organizational Continuous Improvement

Goal: Learn how to foster continuous learning and improvement at an organizational level.

Tasks:

1. Read about Kaizen (Continuous Improvement) in Agile organizations.
2. Scrum Masters and Continuous Learning:
   • How to implement Retrospectives beyond Scrum Teams.
   • Encouraging leadership to engage in learning and development programs.
3. Agile Maturity Assessments:
   • What is an Agile Maturity Model?
   • How to assess an organization's Agile maturity level.
4. Mock Exercise:
   • Design an Agile Maturity Assessment for a company.
   • Identify areas of improvement and an action plan.
5. Final Quiz: Take a 20-question quiz covering Week 5 topics.

Week 6: Final Exam Preparation & Mock Exams

Goal:

Develop exam readiness, refine problem-solving skills, and ensure a strong understanding of all PSM II concepts.

Study Schedule & Tasks

Day 36: Full Review of Scrum Framework & Advanced Concepts

Goal: Refresh all key Scrum principles, artifacts, roles, and events.

Tasks:

1. Re-read the Scrum Guide (Scrum.org) and take notes on any unclear areas.
2. Active Recall Exercise:
   • Without looking at notes, explain the Scrum Framework aloud.
   • Cover roles, artifacts, events, and empirical process control.
3. Quick Review of Past Quizzes:
   • Identify and revisit incorrect answers from previous quizzes.
   • Summarize the top 5 most difficult concepts and research additional explanations.
4. Mock Exercise:
   • Facilitate a Sprint Planning session (self-simulated or with a study partner).
   • Focus on Sprint Goals, Backlog Prioritization, and Commitment.
5. Short Practice Quiz: Take a 10-question quiz covering core Scrum concepts.

Day 37: Advanced Scrum Mastery & Leadership Review

Goal: Strengthen knowledge on Scrum Master’s advanced responsibilities and leadership techniques.

Tasks:

1. Review Servant Leadership:
   • Re-read how a Scrum Master serves the team, Product Owner, and organization.
   • Identify three key leadership techniques to improve team dynamics.
2. Conflict Resolution & Coaching Exercise:
   • Answer three situational questions where a Scrum Master must handle team conflict.
   • Write how you would facilitate a coaching session to resolve the issue.
3. Scaling Agile & Organizational Change Review:
   • Summarize LeSS, SAFe, and Nexus frameworks.
   • Explain how to scale Scrum without losing Agile values.
4. Mock Scenario:
   • Assume the role of Scrum Master coaching a senior manager unfamiliar with Agile.
   • Write a 3-minute pitch explaining Agile leadership benefits.
5. Quiz: Take a 10-question quiz on Agile leadership and coaching.

Day 38: Managing Products with Agility & Agile Engineering Practices

Goal: Strengthen knowledge of backlog management, value delivery, and Agile technical practices.

Tasks:

1. Revisit Backlog Management & Prioritization Techniques:
   • MoSCoW, WSJF, Impact Mapping, Cost of Delay.
   • Write one case where each prioritization method would be most useful.
2. Review Test-Driven Development (TDD) & Continuous Delivery (CD):
   • Explain how TDD, CI/CD, and DevOps improve Scrum product quality.
   • Identify three engineering practices that support Agile development.
3. Self-Assessment Exercise:
   • Compare your team’s Definition of Done (DoD) against industry best practices.
   • Identify two improvements to enhance quality assurance.
4. Mock Exercise:
   • Facilitate a Sprint Retrospective focused on technical debt reduction.
5. Quiz: Take a 10-question quiz on Agile product management and engineering.

Day 39: Organizational Agility & Scaling Scrum

Goal: Final review of scaling frameworks, organizational agility, and Agile transformation.

Tasks:

1. Revisit Scaling Agile Concepts:
   • Compare LeSS vs. Nexus vs. SAFe.
   • Define when to use each scaling method.
2. Agile Transformation Challenges:
   • Review case studies on successful vs. failed Agile transformations.
   • Identify common failure points and how Scrum Masters prevent them.
3. Mock Scenario:
   • You are coaching a company transitioning from Waterfall to Agile.
   • Write a step-by-step change management plan.
4. Quick Recap of Agile Leadership Principles:
   • Review Servant Leadership, Coaching, and Organizational Change Management.
5. Quiz: Take a 10-question quiz on scaling Agile and organizational agility.

Day 40: Full-Length Mock Exam #1 (Timed Practice Test)

Goal: Simulate the real exam experience to assess readiness.

Tasks:

1. Take a Full-Length PSM II Practice Test (Scrum.org Open Assessment + additional scenario-based questions).
2. Time Yourself (90 minutes) – Avoid distractions to simulate real test conditions.
3. Review incorrect answers:
   • Identify weak areas.
   • Revisit corresponding Scrum Guide sections.
4. Write a Summary of Mistakes:
   • What concepts need further clarification?
   • Create a mini-study guide for weak areas.

Day 41: Review Mistakes from Mock Exam #1 & Retake Key Quizzes

Goal: Improve weaknesses identified from Mock Exam #1.

Tasks:

1. Revisit Weak Areas Identified in Mock Exam:
   • Review Scrum Guide, case studies, and notes.
   • Clarify common mistakes and adjust learning.
2. Retake quizzes from past weeks in weak areas.
3. Mock Exercise:
   • Role-play a difficult coaching conversation where a team resists Agile adoption.
   • Write how a Scrum Master should respond.
4. Short Recap Quiz: Take a 10-question quiz focusing on previously incorrect answers.

Day 42: Full-Length Mock Exam #2 (Final Exam Simulation)

Goal: Final full-length test simulation before exam day.

Tasks:

1. Take a second Full-Length PSM II Practice Test under timed conditions (90 minutes).
2. Analyze Score Improvements from Mock Exam #1:
   • Compare performance and track progress.
   • Identify remaining weak areas.
3. Review Scrum Master Best Practices:
   • Re-read difficult case studies to reinforce real-world application.
   • Revise Scrum values, roles, and scaling frameworks.