Certified Scrum Master

Scrum Master is beyond a project manager, who don't instruct team on executable actions rather focus on helping teams achieve short-term objectives. The scrum master is not meant for managing a project but he/she does monitor project on several parameters like timeboxing, planning, backlog monitoring, conduct daily stand-up meetings ; Scrum is unique and most efficient Agile methodologies which is fast, flexible, adaptive, iterative and effective practice designed to deliver quick, reliable and substantial value throughout the project. Scrum also ensures transparent communication, continuous progress, and collective accountability and creates a truly agile project.

Upon successful completion of the course, one will be able to achieve outstanding performance in teams and self-organized units of individuals and when these teams are equipped with objectives, rather than executable tasks. One will be able to significantly achieve as Scrum teaches you how to give room for the teams to develop their own tactics to meet the common objectives.

Agile Thinking

• How manufacturing has influenced software development
• The origins of agile thinking
• The Agile Manifesto
• The complexity of projects
• Theoretical Vs. Empirical processes overview
• The "Iron Triangle" of Project Management

The Scrum Framework

• The different Scrum roles
• Chickens and Pigs
• Iterative Development vs. Waterfall
• Self-Management concepts
• Full disclosure and visibility
• The Scrum Framework Overview

Implementation Considerations

• Traditional vs. Agile methods overview
• Scrum:  The Silver Bullet?
• The Agile Skeleton
• A Scrum launch checklist

Scrum Roles

• The Team Member
• The Product Owner
• The Scrum Master

The Scrum Team Explored

• The Agile Heart
• Bruce Tuckman's team life cycle
• Patrick Lencioni's Five Dysfunctions of a Team
• Team ground rules
• Getting Human Resources involved
• The impact of project switching
• The Scrum of Scrums
• Large Scale Scrum (LeSS)
• The importance of knowing when software is "done"
• Dispersed team consideration

Agile Estimating and Planning

• Product Backlog Features
• Relative Weighted Prioritization
• User Stories
• Relative Effort
• Velocity
• Planning Poker and Story Points
• Projecting a Schedule
• Why Plan in an Agile Environment?

The Product Owner:  Extracting Value: to maximize Returns

• The Priority Guide
• Product Backlog Refactoring
• Release Management

The ScrumMaster Explored

• The ScrumMaster Aura
• Characteristics of a ScrumMaster Candidate
• The Difficulties of Being a ScrumMaster
• A Day in the Life of a ScrumMaster
• The Importance of Listening
• Common Sense

Meetings and Artifacts Reference Material

• A Chart of Scrum Meetings
• The Product Backlog
• Sprint Planning
• The Sprint Backlog
• The Sprint
• The Daily Scrum
• The Sprint Review
• Why Plan?
• The Ideal Team Day
• Scrum Tools