Agile SCRUM Master

Course Objectives

  • By the end of the course, participants will have a deep understanding of Scrum principles and their practical application.
  • The course is essential for professionals looking to enhance their Agile project management skills.
  • Participants will gain valuable insights into Agile methodologies, increasing their efficiency and effectiveness in project delivery.
  • Upon completion, attendees will be well-prepared to take on the role of a Scrum Master and lead Agile teams successfully.

Participant’s Profile

Scrum training is appropriate for:

  • Team members interested in understanding Agile and implementing Scrum
  • Project Managers and Leads
  • Project Sponsors
  • IT Managers and Executives
  • Business Analysts
  • Developers/Programmers
  • Designers
  • Project team members
  • Business customers
  • Business users
  • Product owners

Requirements to the Participants

  • Attendees must have at least two years of relevant full-time work experience.

Length of the Course

  • 15 hours (3 days)

Evaluation

  • Attendance: 20%
  • Class Activities: 30%
  • Final Project: 50%

Certification

  • Agile Scrum Master certification from Scrum Master Institute.

Learning Outcomes

At the end of this training, you will be able to:

  • Understand the theory and principles behind Scrum and empiricism.
  • Help Scrum Teams deliver value to their organization.
  • Understand how each part of the Scrum framework ties back to the principles and theory.
  • Understand uncertainty and complexity in product delivery.
  • Understand the meaning and importance of the Scrum values.
  • Learn what "Done" means and why it is crucial to transparency.
  • Know how to use the Product Backlog to plan with agility.
  • Understand the importance of self-managing teams, interpersonal skills needed, and the Scrum Master role.
  • Clarify the leadership role a Scrum Master plays on the team.
  • Learn the skills, traits, and behavior shifts required to be a Scrum Master.

Course Content

  • Introduction to Agile and Scrum
  • Scrum Framework: Roles, Events, and Artifacts
  • Scrum Values and Principles
  • Managing the Product Backlog
  • Effective Sprint Planning and Execution
  • Facilitation Skills for Scrum Masters
  • Servant Leadership and Team Coaching
  • Scaling Scrum in Organizations
  • Common Challenges and Best Practices
  • Final Project and Case Studies

 
Topic Description
1. Overview of Agile and Scrum
  • Demonstrate the advantages of "responding to change" in Agile compared to "following a plan" in traditional project management.
  • Describe how Scrum values (courage, focus, commitment, respect, openness) relate to artifacts, events, and roles in Scrum.
  • List and explain the three pillars of Scrum — Transparency, Inspection, Adaptation.
  • Explain the differences between a framework and a methodology and understand why Scrum is called a framework.
  • List 5 ways to develop Agile thinking.
  • Illustrate 2 differences between Agile and Scrum and explain why these terms cannot be used interchangeably.
2. Three Roles in Scrum
  • Explain the roles and responsibilities of the Scrum Master and Product Owner.
  • List 3 differences between the Scrum Master and Product Owner and understand why these roles should not overlap.
  • Discuss how the Product Owner acts as a bridge between the development team and stakeholders.
  • Understand why the Scrum Master is not an active participant but a facilitator in Scrum events and ceremonies.
  • List 3 drawbacks of a development team consisting of fewer than 3 or more than 10 members.
3. Scrum Ceremonies
  • Explain the "why" and "how" of sprint planning, daily Scrum, sprint review, and retrospective.
  • Understand why the scope and duration of the sprint are fixed.
  • List 3 ways to avoid sprint backlog overflow.
  • Define sprint goals and discuss 5 benefits of having a sprint goal.
  • Understand how the Scrum Master and Product Owner should coordinate with the team, and list 5 points to improve such communications.
  • Discuss 3 disruptive consequences of canceling a sprint and how to avoid it.
  • List 10 sprint anti-patterns (e.g., sprint cancellation, variable sprint length) and understand how they affect delivery and lead time.
4. Scrum Artifacts
  • List and demonstrate 5 key characteristics of a well-formed product backlog (e.g., estimated, prioritized).
  • Discuss 2 responsibilities of the Product Owner, Scrum Master, and development team in creating and maintaining the product backlog.
  • The purpose of having a product backlog and the best approaches to refining it.
  • Analyze and discuss the ideal time and effort to be devoted to refining the product backlog.
  • Demonstrate 3 activities (e.g., budget and timeline, release schedule) that occur during the sprint review.
  • List 5 sprint review anti-patterns (e.g., delayed acceptance) and their negative impact.
5. Sprint Execution
  • Explain the difference between problem-solving meetings and daily stand-ups.
  • Explain the benefits of collaborating with the Product Owner.
  • List 3 drawbacks of excessive collaboration with the Product Owner.
  • Demonstrate 3 ways to overcome barriers and collaborate.
  • Demonstrate creating a sprint burn-down chart.
  • Explain 3 approaches to improving team efficiency.
6. Daily Scrum and Sprint Retrospective
  • Explain the importance of the 15-minute timebox for daily Scrum meetings.
  • List 3 differences between traditional meetings and daily stand-ups.
  • Describe 2 roles played by the Scrum Master, Product Owner, and development team in the daily Scrum.
  • List 3 critical questions related to the daily Scrum agenda.
  • List 2 responsibilities of the Scrum Master, Product Owner, and development team during the sprint retrospective.
7. Release Planning
  • Identify and understand the steps involved in release planning.
  • List 3 benefits of well-organized release planning.
  • List 3 outcomes of release planning.