The 2-day Certified ScrumMaster course introduces attendees to the values, principles, and practices of agile and the agile-based empirical Scrum product development framework. Successful completers can become Certified ScrumMasters, a first step in the journey of learning Scrum and becoming proficient in its use.
Attendees also learn the paradigm shifts that occur when organizations move from traditional linear / defined development environments to the empirical agile environment and strategies and tactics used to support and manage the change that occurs. Participants also will learn about the 3 Scrum roles (Team Member, Product Owner, and ScrumMaster), the 4 Scrum meetings (Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective) and process of building product in a time-boxed iteration called a Sprint. Students will assume responsibility for their learning in the course and will work in small teams. The course includes a detailed Scrum project simulation and other exercises that will reinforce course concepts. Participants will have opportunity to explore and apply self-organization and self-direct concepts that contribute most effectively to building a high performing team environment where quality can be built into a product through the empricial process of inspecting and adapting processes and products.
After completing this course, the student should be able to:
· Demonstrate the appropriate understanding and application of Scrum roles, practices, principles, and values
· Apply appropriate analysis about how empirical the approach to project work should be (when to use Scrum)
· Appreciate the skills, desired styles, and responsibilities of the Team, Product Owner and ScrumMaster
· Accept and explain the rationale behind the absence of a project manager in Scrum
· Apply Scrum estimating and planning techniques and practices
· Understand the use and presentation of certain data used for inspecting and adapting to improve team performance and the product
· Understand the criticality of building trust within and between Scrum teams and between teams and management
· Understand the essence of team self-organization and self-direction to build high perfroming teams, and the necessity of servant leadership
· Identify and deal with smells (pitfalls) that the organization and its teams may encounter that may impede the use of Scrum