Certified ScrumMaster Learning Outcomes
Through a combination of immersive team-based learning, exercises, and real-world case studies, participants will learn:
How Agile is different from traditional waterfall development and how organizations should think differently in this new environment.
What it takes to be a good ScrumMaster, including role specifics, responsibilities within the Scrum team, and skills needed to become successful.
How artifacts like the Sprint Backlog and Burndown charts create visibility and track progress.
How to encourage your team improve their technical practices, not just processes.
How the ScrumMaster fits into an organization’s overall Agile transformation strategy on the Path to Agility®.
Earning Your CSM certification
At the end of the two days, our CST will submit the names of qualified participants to Scrum Alliance and Scrum Alliance will send a link to take the test.
Exam retake policy and associated fees
To pass the Scrum Alliance CSM certification exam, you need to get 74% of the questions correct. There are 50 questions and you will have 60 minutes to take the exam. Participants will have two attempts within 90 days of receiving the welcome email from Scrum Alliance at no cost. After two attempts or 90 calendar days, the test is $25 for each retake. The exam is an open book, open note test.
Sample CSM certification exam questions
The Development Team does not sit together and therefore rarely communicates. Due to this arrangement, they tend to segue into deep technical discussions when sharing at the Daily Scrum. What should the ScrumMaster do?
- Discuss at the next retrospective for the team to determine how best to address the issue
- Assign a technical lead to work with all the developers individually on their issues
- Extend the Daily Scrum to 60 minutes
- Schedule an additional meeting for technical discussions at another time
The Sprint Burndown Chart can be BEST described as:
- An indicator of how much time each member is spending on each task
- An indicator of how the Team is progressing towards their Sprint Goals
- A tool to track scope changes in the Sprint
- A tool to manage what the Team is doing each day
What is a good indicator that the Sprint Retrospective was productive?
- Team identified 1-3 actionable items to implement during the next Sprint
- Team discussed what worked well and what could be improved upon
- Team reviewed metrics from the previous Sprint (burndown chart, velocity, etc.)
- Team discussed all of the impediments that were surfaced in the previous Sprint