Starting with the origins of agile development and building systematically through the disciplines promoted by Scrum, this Certified ScrumMaster (CSM) training course delivers a comprehensive understanding of the Scrum methodology and a focused review of the specific behaviors, responsibilities, and mindset expected of a ScrumMaster. This two-day course is ideal for those actively practicing or aspiring to practice the ScrumMaster role, and is highly valuable for anyone involved in Scrum teams or organizations transitioning to agile delivery.
Even the most carefully developed project plans encounter disruption. Shifting market conditions, budget realignments, staff changes, or evolving requirements can derail the best-laid plans and erode both customer confidence and team morale. Scrum is the agile development framework that enables teams to deliver usable software iteratively throughout the project lifecycle, adapting fluidly to new requirements as they emerge.
Please Note: This course has an attendance and virtual camera requirement.
- Attendance is required for the full duration of the course. Instructors will verify each student's participation to confirm completion.
- Webcam use is required for all students throughout the course.
Who Should Attend:
Current Scrum Team Members not yet certified:
- Business customers, users, or partners
- Product Owners
- Team Members
- Acting ScrumMasters who have not yet obtained certification
Professionals in organizations considering a move to Scrum:
- Project Managers and Project Leads
- Project Sponsors
- IT Managers and Directors
- Business Analysts
- Developers and Programmers
How You Will Benefit:
- Explain and facilitate the three core Scrum roles: Team Member, Product Owner, and ScrumMaster
- Apply the foundational concepts of Scrum to real project work
- Use empirical thinking as a guide for decision-making throughout the project
- Understand your team's productivity and lead continuous improvement efforts
- Communicate the importance of organizational alignment on what constitutes "done"
- Appreciate that the ScrumMaster role can be simultaneously the most rewarding and the most demanding on a project
- Embrace conflict resolution as an essential ScrumMaster tool
- Work on real-world Scrum projects
- Apply the full Scrum framework effectively
- Know when software has met the definition of "done" under Scrum
What You Will Cover:
Part 1: Scrum Theory
- Empiricism and the three empirical pillars of transparency, inspection, and adaptation
- The benefits of iterative and incremental delivery
- The Scrum Framework and Scrum Values
- Scrum's alignment with the Agile Manifesto
Part 2: The Scrum Team
- The collective responsibilities of the Scrum Team
- The specific responsibilities of the Product Owner, Developers, and Scrum Master
- The importance of a single Product Owner who owns the Product Backlog
- Delivering a working Increment
- The advantages of a cross-functional, self-managing team structure
Part 3: Scrum Events and Activities
- The value of timeboxing in Scrum
- The purpose and structure of a Sprint
- Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective in practice
- Product Backlog Refinement and inspecting-and-adapting events
- Conditions under which a sprint may be canceled
- Why the Daily Scrum is not a status meeting
Part 4: Scrum Artifacts and Commitments
- The purpose of the Product Backlog, Sprint Backlog, and Increment
- Product Goals, Sprint Goals, and the Definition of Done as commitments
- How the Product Backlog evolves over time
- Managing multiple teams working on a shared Product Backlog
Part 5: ScrumMaster Core Competencies
- Facilitation and facilitating effective decision-making
- Teaching, coaching, and mentoring within the team and organization
Part 6: Service to the Scrum Team, Product Owner, and Organization
- How the ScrumMaster serves and supports the Scrum Team
- Understanding and addressing technical debt
- Supporting the Product Owner in managing the backlog
- Identifying and removing organizational impediments affecting Scrum Teams
- Understanding why the Scrum framework does not include a Project Manager role