Certified Agile Practitioner – Scrum Master

This two-day Scrum training course teaches participants that Agile project delivery is radically different from traditional waterfall methodologies. Rather than using a command and control technique, the Agile project manager facilitates, coaches, and leads. This person is called a Scrum Master in the Scrum Agile process to denote the difference and remind the person filling this role of the new responsibilities.

Participants learn how to be a Scrum Master as well as the practices and thinking to increase the agility of a development team, a project, and an organization. The Scrum Master is the person responsible for the proper execution of Scrum and facilitating the necessary change within the engineering and overall organization. Exercises, case studies, and examples are used to bring home the realization of how to be a Scrum Master. All participants are expected to understand Scrum basics prior to attending this course.

This course focuses on the "how to" in addition to reinforcing the "what."

Printer-friendly PDF

Key Outcomes

Upon completion of this course, participants will be able to:

  • Identify and remove the communication barriers between the development team and the customer so the customer directly drives development
  • Teach, mentor, and coach the customer on how to maximize ROI and meet his/her objectives through Scrum
  • Improve the development team by facilitating creativity and empowerment
  • Improve the productivity of the development team by removing impediments and highlighting organizational inefficiencies
  • Improve the engineering practices and tools so each increment of functionality is potentially shippable

Course Outline

Agile Overview

  • Agile Framework
  • Agile Overview
  • The Agile Manifesto & Principles
  • Agile is Not Enough
  • Can Agile Fail?
  • The Best Agile

Scrum Overview

  • Roles and responsibilities
  • How It Works
  • Artifacts

The Scrum Master's Role In-Depth

  • Servant Leadership
  • Facilitation
  • Coaching the Product Owner
  • Coaching the Development Team

Keys to Success

  • OO and UML
  • Architectural Changes
  • Emergent Design
  • Adopting Principles from Lean

Product Backlog

  • Defining the Product Backlog
  • Prioritizing the Product Backlog
  • Estimates

Release Planning

  • Projecting Burndown into the Future
  • Release Planning Meeting
  • Release Layout

Spring Planning

  • Sprint Planning Meeting


  • All about the Sprint
  • Lab Sprints

Sprint Conclusion

  • Sprint Review
  • Sprint Retrospective

Other Considerations

  • Scrum in the Organization
  • Scaled Agile Framework Overview
  • Testing
  • Distributed Scrum