Why you should use Scrum Master Test?

The Scrum Master Test makes use of scenario-based questions to test for on-the-job skills as opposed to theoretical knowledge, ensuring that candidates who do well on this screening test have the relavant skills. The questions are designed to covered following on-the-job aspects: Knowledge of Scrum framework and its principles Understanding of Agile methodology Proficiency in Sprint Planning and execution Ability to manage and prioritize the Product Backlog Experience in writing effective User Stories Competence in conducting Iteration Reviews Proficient in facilitating Daily Stand-up meetings Expertise in conducting Retrospectives Familiarity with Scrum Artifacts such as burndown charts Understanding of Scrum Roles and responsibilities

Scrum Master Test

Q: What topics are covered in the Scrum Master Test?

Scrum Agile Framework Sprint Planning Product Backlog User Stories Iteration Review Daily Stand-up Retrospective Scrum Artifacts Scrum Roles Scrum Events

About the test:

The Scrum Master Test evaluates a candidate's knowledge and understanding of the Scrum framework, agile principles, and the role of a Scrum Master. Topics covered include sprint planning, product backlog management, user stories, iteration review, daily stand-up meetings, retrospectives, Scrum artifacts, and Scrum roles.

Covered skills:

Scrum
Sprint Planning
User Stories
Daily Stand-up
Scrum Artifacts
Scrum Events

Agile Framework
Product Backlog
Iteration Review
Retrospective
Scrum Roles

Try practice test

Start 14-day free trial

9 reasons why

Adaface Scrum Master Assessment Test is the most accurate way to shortlist Scrum Masters

Reason #1

Tests for on-the-job skills

The Scrum Master Test helps recruiters and hiring managers identify qualified candidates from a pool of resumes, and helps in taking objective hiring decisions. It reduces the administrative overhead of interviewing too many candidates and saves time by filtering out unqualified candidates at the first step of the hiring process.

The test screens for the following skills that hiring managers look for in candidates:

Ability to effectively apply Scrum principles and practices
Ability to facilitate Sprint Planning meetings
Ability to manage and prioritize the Product Backlog
Ability to write clear and concise User Stories
Ability to conduct effective Iteration Reviews
Ability to lead Daily Stand-up meetings
Ability to facilitate Retrospective sessions
Ability to understand and utilize Scrum Artifacts
Ability to perform Scrum Roles effectively
Ability to plan and execute Scrum Events
Ability to coach and mentor team members
Ability to promote collaboration and self-organization within the team

Reason #2

No trick questions

Traditional assessment tools use trick questions and puzzles for the screening, which creates a lot of frustration among candidates about having to go through irrelevant screening assessments.

View sample questions

The main reason we started Adaface is that traditional pre-employment assessment platforms are not a fair way for companies to evaluate candidates. At Adaface, our mission is to help companies find great candidates by assessing on-the-job skills required for a role.

Why we started Adaface

Try practice test

Start 14-day free trial

Reason #3

Non-googleable questions

We have a very high focus on the quality of questions that test for on-the-job skills. Every question is non-googleable and we have a very high bar for the level of subject matter experts we onboard to create these questions. We have crawlers to check if any of the questions are leaked online. If/ when a question gets leaked, we get an alert. We change the question for you & let you know.

How we design questions

These are just a small sample from our library of 10,000+ questions. The actual questions on this Scrum Master Test will be non-googleable.

🧐 Question
Medium Managing Dependencies Backlog Management Dependencies Cross-functional Teams	Try practice test
You are a Scrum Master in an organization that is transitioning to Scrum. You have multiple Scrum Teams working on different parts of a large software product. Each team is working on different features, but those features have dependencies on one another. For example, Team A is working on a feature that cannot be completed until Team B completes another feature. During the Sprint Planning, Team A chose a user story from its backlog that depends on the completion of a user story from Team B’s backlog. However, Team B can't guarantee that their user story will be done in the next sprint. What should be the Scrum Master's approach to handle this scenario following Scrum principles? A: Have Team A start working on the dependent user story with the hope that Team B finishes their part within the sprint. B: Ask Team A to choose a different user story for this sprint that doesn't depend on Team B's work. C: Arrange a joint session between Team A and Team B to revise their sprint plans, ensuring dependent user stories are completed in the same sprint. D: Merge Team A and Team B for the next sprint to ensure they work together on the dependent user stories. E: Delay the start of Team A’s sprint until Team B completes their user story.
Medium Burndown Chart 1 Metrics	Try practice test
Here’s a sprint burndown chart for team A at SpaceY Inc: Here’s a sprint burndown chart for team B at SpaceY Inc: We know the following about the graphs: - Red line is the the ideal line: projected slope that depicts how the team progress would look like - Black line is the actual effort line - Story points are represented on Y-axis - And time in weeks is represented on X-axis Which of the following statements are true about SpaceY teams: P: Team A started slowly and was moving behind schedule. Yet, they managed to finish the sprint in time Q: Team A is working hard towards meeting the deadline but isn’t updating the burndown chart throughout the process, only at the end. R: Team A’s next sprint’s capacity should be burned down or decreased so that the team can have to complete tasks/story points from the previous sprint S: Team B started slowly but eventually caught up T: Team B might have overestimated the project’s timeline
Medium Stakeholders and Estimates Stakeholders Timelines	Try practice test
Emily is a product owner for a new application being built at Whalesforce Inc. To maintain visibility into project status, Emily has cut the project into chunks which different teams will be responsible for: - DevOps team (DoT) will set up the servers. They have no dependencies and will take 4 weeks to set things up. - Design team (DT) will design the screens for the application, have no dependencies and need 3 weeks to wrap up. - Front-end team (FT) will need the designs to start the work, and will take 5 weeks to create the front-end components. - Backend team (BT) will need input from DoT and DT to start designing the backend system, and will take 3 weeks to release the backend APIs. - Security team (ST) will require server details from DoT, and will need 3 weeks to give a go-ahead. - Integration team (IT) will require the front-end components and backend API to set up the integration. They will launch the application in 3 weeks. The project is marked for internal release once IT and ST teams give a go-ahead. Emily wants to communicate the best-case estimate for the internal release of the project to the major stakeholders. Can you help her with the estimate?
Medium Story Velocity 2 Velocity Metrics	Try practice test
Seloitte hires PopTal for developing a new mobile application. PopTal team follows Agile methodology for development and estimates the whole project to take up to 1000 points. In the first sprint the team commits to work on the following stories: Story 1 - 6 points Story 2 - 10 points Story 3 - 16 points The team completes Story 1 and 3 but only completes eighty percent of Story 2. Pick the correct statements: A: The average velocity of the first sprint is 22 points B: The average velocity of the first sprint is 30 points C: Based on the average velocity, the product owner can notify the stakeholders that the project will take roughly 45 sprints to finish (assuming team size and members remain the same) D: Based on the average velocity, the product owner can notify the stakeholders that the project will take roughly 33 sprints to finish (assuming team size and members remain the same)

	🧐 Question	🔧 Skill
	Medium Managing Dependencies Backlog Management Dependencies Cross-functional Teams	2 mins Agile/Scrum	Try practice test
You are a Scrum Master in an organization that is transitioning to Scrum. You have multiple Scrum Teams working on different parts of a large software product. Each team is working on different features, but those features have dependencies on one another. For example, Team A is working on a feature that cannot be completed until Team B completes another feature. During the Sprint Planning, Team A chose a user story from its backlog that depends on the completion of a user story from Team B’s backlog. However, Team B can't guarantee that their user story will be done in the next sprint. What should be the Scrum Master's approach to handle this scenario following Scrum principles? A: Have Team A start working on the dependent user story with the hope that Team B finishes their part within the sprint. B: Ask Team A to choose a different user story for this sprint that doesn't depend on Team B's work. C: Arrange a joint session between Team A and Team B to revise their sprint plans, ensuring dependent user stories are completed in the same sprint. D: Merge Team A and Team B for the next sprint to ensure they work together on the dependent user stories. E: Delay the start of Team A’s sprint until Team B completes their user story.
	Medium Burndown Chart 1 Metrics	2 mins Agile/Scrum	Try practice test
Here’s a sprint burndown chart for team A at SpaceY Inc: Here’s a sprint burndown chart for team B at SpaceY Inc: We know the following about the graphs: - Red line is the the ideal line: projected slope that depicts how the team progress would look like - Black line is the actual effort line - Story points are represented on Y-axis - And time in weeks is represented on X-axis Which of the following statements are true about SpaceY teams: P: Team A started slowly and was moving behind schedule. Yet, they managed to finish the sprint in time Q: Team A is working hard towards meeting the deadline but isn’t updating the burndown chart throughout the process, only at the end. R: Team A’s next sprint’s capacity should be burned down or decreased so that the team can have to complete tasks/story points from the previous sprint S: Team B started slowly but eventually caught up T: Team B might have overestimated the project’s timeline
	Medium Stakeholders and Estimates Stakeholders Timelines	2 mins Agile/Scrum	Try practice test
Emily is a product owner for a new application being built at Whalesforce Inc. To maintain visibility into project status, Emily has cut the project into chunks which different teams will be responsible for: - DevOps team (DoT) will set up the servers. They have no dependencies and will take 4 weeks to set things up. - Design team (DT) will design the screens for the application, have no dependencies and need 3 weeks to wrap up. - Front-end team (FT) will need the designs to start the work, and will take 5 weeks to create the front-end components. - Backend team (BT) will need input from DoT and DT to start designing the backend system, and will take 3 weeks to release the backend APIs. - Security team (ST) will require server details from DoT, and will need 3 weeks to give a go-ahead. - Integration team (IT) will require the front-end components and backend API to set up the integration. They will launch the application in 3 weeks. The project is marked for internal release once IT and ST teams give a go-ahead. Emily wants to communicate the best-case estimate for the internal release of the project to the major stakeholders. Can you help her with the estimate?
	Medium Story Velocity 2 Velocity Metrics	3 mins Agile/Scrum	Try practice test
Seloitte hires PopTal for developing a new mobile application. PopTal team follows Agile methodology for development and estimates the whole project to take up to 1000 points. In the first sprint the team commits to work on the following stories: Story 1 - 6 points Story 2 - 10 points Story 3 - 16 points The team completes Story 1 and 3 but only completes eighty percent of Story 2. Pick the correct statements: A: The average velocity of the first sprint is 22 points B: The average velocity of the first sprint is 30 points C: Based on the average velocity, the product owner can notify the stakeholders that the project will take roughly 45 sprints to finish (assuming team size and members remain the same) D: Based on the average velocity, the product owner can notify the stakeholders that the project will take roughly 33 sprints to finish (assuming team size and members remain the same)

	🧐 Question	🔧 Skill	💪 Difficulty	⌛ Time
	Managing Dependencies Backlog Management Dependencies Cross-functional Teams	Agile/Scrum	Medium	2 mins	Try practice test
You are a Scrum Master in an organization that is transitioning to Scrum. You have multiple Scrum Teams working on different parts of a large software product. Each team is working on different features, but those features have dependencies on one another. For example, Team A is working on a feature that cannot be completed until Team B completes another feature. During the Sprint Planning, Team A chose a user story from its backlog that depends on the completion of a user story from Team B’s backlog. However, Team B can't guarantee that their user story will be done in the next sprint. What should be the Scrum Master's approach to handle this scenario following Scrum principles? A: Have Team A start working on the dependent user story with the hope that Team B finishes their part within the sprint. B: Ask Team A to choose a different user story for this sprint that doesn't depend on Team B's work. C: Arrange a joint session between Team A and Team B to revise their sprint plans, ensuring dependent user stories are completed in the same sprint. D: Merge Team A and Team B for the next sprint to ensure they work together on the dependent user stories. E: Delay the start of Team A’s sprint until Team B completes their user story.
	Burndown Chart 1 Metrics	Agile/Scrum	Medium	2 mins	Try practice test
Here’s a sprint burndown chart for team A at SpaceY Inc: Here’s a sprint burndown chart for team B at SpaceY Inc: We know the following about the graphs: - Red line is the the ideal line: projected slope that depicts how the team progress would look like - Black line is the actual effort line - Story points are represented on Y-axis - And time in weeks is represented on X-axis Which of the following statements are true about SpaceY teams: P: Team A started slowly and was moving behind schedule. Yet, they managed to finish the sprint in time Q: Team A is working hard towards meeting the deadline but isn’t updating the burndown chart throughout the process, only at the end. R: Team A’s next sprint’s capacity should be burned down or decreased so that the team can have to complete tasks/story points from the previous sprint S: Team B started slowly but eventually caught up T: Team B might have overestimated the project’s timeline
	Stakeholders and Estimates Stakeholders Timelines	Agile/Scrum	Medium	2 mins	Try practice test
Emily is a product owner for a new application being built at Whalesforce Inc. To maintain visibility into project status, Emily has cut the project into chunks which different teams will be responsible for: - DevOps team (DoT) will set up the servers. They have no dependencies and will take 4 weeks to set things up. - Design team (DT) will design the screens for the application, have no dependencies and need 3 weeks to wrap up. - Front-end team (FT) will need the designs to start the work, and will take 5 weeks to create the front-end components. - Backend team (BT) will need input from DoT and DT to start designing the backend system, and will take 3 weeks to release the backend APIs. - Security team (ST) will require server details from DoT, and will need 3 weeks to give a go-ahead. - Integration team (IT) will require the front-end components and backend API to set up the integration. They will launch the application in 3 weeks. The project is marked for internal release once IT and ST teams give a go-ahead. Emily wants to communicate the best-case estimate for the internal release of the project to the major stakeholders. Can you help her with the estimate?
	Story Velocity 2 Velocity Metrics	Agile/Scrum	Medium	3 mins	Try practice test
Seloitte hires PopTal for developing a new mobile application. PopTal team follows Agile methodology for development and estimates the whole project to take up to 1000 points. In the first sprint the team commits to work on the following stories: Story 1 - 6 points Story 2 - 10 points Story 3 - 16 points The team completes Story 1 and 3 but only completes eighty percent of Story 2. Pick the correct statements: A: The average velocity of the first sprint is 22 points B: The average velocity of the first sprint is 30 points C: Based on the average velocity, the product owner can notify the stakeholders that the project will take roughly 45 sprints to finish (assuming team size and members remain the same) D: Based on the average velocity, the product owner can notify the stakeholders that the project will take roughly 33 sprints to finish (assuming team size and members remain the same)

Reason #4

1200+ customers in 75 countries

With Adaface, we were able to optimise our initial screening process by upwards of 75%, freeing up precious time for both hiring managers and our talent acquisition team alike!

Brandon Lee, Head of People, Love, Bonito

Try practice test

Start 14-day free trial

Reason #5

Designed for elimination, not selection

The most important thing while implementing the pre-employment Scrum Master Test in your hiring process is that it is an elimination tool, not a selection tool. In other words: you want to use the test to eliminate the candidates who do poorly on the test, not to select the candidates who come out at the top. While they are super valuable, pre-employment tests do not paint the entire picture of a candidate’s abilities, knowledge, and motivations. Multiple easy questions are more predictive of a candidate's ability than fewer hard questions. Harder questions are often "trick" based questions, which do not provide any meaningful signal about the candidate's skillset.

Science behind Adaface tests

Reason #6

1 click candidate invites

Email invites: You can send candidates an email invite to the Scrum Master Test from your dashboard by entering their email address.

Public link: You can create a public link for each test that you can share with candidates.

API or integrations: You can invite candidates directly from your ATS by using our pre-built integrations with popular ATS systems or building a custom integration with your in-house ATS.

Reason #7

Detailed scorecards & benchmarks

View sample scorecard

Try practice test

Start 14-day free trial

Reason #8

High completion rate

Adaface tests are conversational, low-stress, and take just 25-40 mins to complete.

This is why Adaface has the highest test-completion rate (86%), which is more than 2x better than traditional assessments.

Reason #9

Advanced Proctoring

Learn more

Preview this test

View sample scorecard

About the Scrum Master Online Test

Why you should use Pre-employment Scrum Master Test?

The Scrum Master Test makes use of scenario-based questions to test for on-the-job skills as opposed to theoretical knowledge, ensuring that candidates who do well on this screening test have the relavant skills. The questions are designed to covered following on-the-job aspects:

Knowledge of Scrum framework and its principles
Understanding of Agile methodology
Proficiency in Sprint Planning and execution
Ability to manage and prioritize the Product Backlog
Experience in writing effective User Stories
Competence in conducting Iteration Reviews
Proficient in facilitating Daily Stand-up meetings
Expertise in conducting Retrospectives
Familiarity with Scrum Artifacts such as burndown charts
Understanding of Scrum Roles and responsibilities

Once the test is sent to a candidate, the candidate receives a link in email to take the test. For each candidate, you will receive a detailed report with skills breakdown and benchmarks to shortlist the top candidates from your pool.

What topics are covered in the Scrum Master Test?

Scrum
Scrum is an agile framework used for managing complex projects. It emphasizes iterative development, teamwork, and continuous feedback. This skill is measured in the test because a Scrum Master needs to have a deep understanding of Scrum principles and practices to effectively facilitate the development process.
Agile Framework
The Agile framework is an iterative approach to project management and software development. It promotes adaptive planning, evolutionary development, and early delivery. Measuring this skill in the test helps recruiters assess a Scrum Master's ability to apply Agile principles and practices in a real-world context.
Sprint Planning
Sprint planning is a collaborative meeting where the Scrum team defines the work to be done in a sprint. It involves selecting user stories from the product backlog, estimating effort, and creating a sprint backlog. This skill is measured in the test to evaluate a Scrum Master's proficiency in guiding the team through effective sprint planning, ensuring realistic commitments and prioritization.
Product Backlog
The product backlog is a prioritized list of desired product features, enhancements, and defects. It serves as the single source of requirements for the Scrum team. Assessing this skill in the test helps recruiters gauge a Scrum Master's understanding of how to manage and refine the product backlog, ensuring that it is well-groomed and aligns with the overall product vision.
User Stories
A user story is a concise, informal description of a desired software feature. It focuses on the end user's perspective and serves as a placeholder for a conversation between the development team and stakeholders. Measuring this skill in the test enables recruiters to assess a Scrum Master's ability to create, refine, and prioritize user stories effectively, ensuring clear communication and shared understanding.
Iteration Review
Iteration review, also known as sprint review, is a collaborative meeting where the Scrum team presents the work completed during a sprint to stakeholders. It provides an opportunity to gather feedback, adapt the product backlog, and plan next steps. This skill is measured in the test to evaluate a Scrum Master's proficiency in facilitating productive iteration review meetings, ensuring valuable insights and continuous improvement.
Daily Stand-up
The daily stand-up is a short, timeboxed meeting held by the Scrum team to synchronize work and identify any impediments. It involves each team member sharing what they did, what they plan to do, and if they have any challenges. Assessing this skill in the test helps recruiters assess a Scrum Master's ability to facilitate effective daily stand-ups, ensuring transparency, collaboration, and alignment within the team.
Retrospective
The retrospective is a structured meeting where the Scrum team reflects on the past sprint and identifies areas for improvement. It focuses on learning from experiences and continuously enhancing the team's performance. Measuring this skill in the test enables recruiters to evaluate a Scrum Master's proficiency in conducting retrospectives that foster a safe environment for open communication, constructive feedback, and actionable improvement plans.
Scrum Artifacts
Scrum artifacts are the tangible deliverables that provide transparency and opportunities for inspection and adaptation in Scrum. They include the product backlog, sprint backlog, and increment. Evaluating this skill in the test helps recruiters assess a Scrum Master's understanding of how to effectively manage and utilize Scrum artifacts to support the development process and ensure product value.
Scrum Roles
Scrum roles define the accountabilities and responsibilities within the Scrum framework. These roles include the Scrum Master, Product Owner, and Development Team. This skill is measured in the test to evaluate a Scrum Master's knowledge of the different roles, their interactions, and their impact on Scrum implementation and project success.
Scrum Events
Scrum events are timeboxed ceremonies that provide regular and predictable opportunities for inspection and adaptation in Scrum. They include sprint planning, daily stand-up, iteration review, and retrospective. Assessing this skill in the test enables recruiters to evaluate a Scrum Master's understanding of the purpose, flow, and facilitation techniques for each Scrum event, ensuring effective collaboration and continuous improvement.
Full list of covered topics
The actual topics of the questions in the final test will depend on your job description and requirements. However, here's a list of topics you can expect the questions for Scrum Master Test to be based on.
Scrum Introduction
Agile Framework
Scrum Values
Scrum Roles
Product Owner
Scrum Master
Development Team
Scrum Events
Sprint Planning
Daily Stand-up
Sprint Review
Sprint Retrospective
Scrum Artifacts
Product Backlog
Sprint Backlog
User Stories
Acceptance Criteria
Definition of Done
Estimation Techniques
Planning Poker
Relative Sizing
Story Points
Velocity
Burn-down Chart
Task Boards
Daily Scrum Questions
Impediment Resolution
Team Empowerment
Collaboration Techniques
Agile Manifesto
Scrum Framework
Agile Principles
Scrum Benefits
Scrum Adoption
Scrum Terminology
Scrum Ceremonies
Scrum Metrics
Scrum Board
Scrum Meeting
Scrum Stand-up
Scrum Progress Tracking
Scrum Documentation
Scrum Tools
Scrum Techniques
Scrum Best Practices
Scrum Challenges
Scrum Case Studies
Scrum Resources
Scrum Certification
Scrum Interviews

Try practice test

Start 14-day free trial

What roles can I use the Scrum Master Test for?

Scrum Master
Product Owner
Agile Coach
Project Manager
Release Manager

How is the Scrum Master Test customized for senior candidates?

For intermediate/ experienced candidates, we customize the assessment questions to include advanced topics and increase the difficulty level of the questions. This might include adding questions on topics like

Proficiency in coordinating Scrum Events
Capability to provide guidance and mentoring to team members
Ability to identify and resolve project impediments
Expertise in conducting Scrum of Scrums meetings
Knowledge of facilitation techniques for collaborative decision-making
Experience in managing distributed or remote teams
Proficiency in creating and maintaining a Product Owner relationship
Capability to coach and guide Product Owners on prioritization
Ability to handle team dynamics and conflicts effectively
Expertise in using Agile Project Management tools and software
Proficiency in conducting training sessions and workshops for Agile and Scrum

Preview this test

View sample scorecard

The hiring managers felt that through the technical questions that they asked during the panel interviews, they were able to tell which candidates had better scores, and differentiated with those who did not score as well. They are highly satisfied with the quality of candidates shortlisted with the Adaface screening.

85%

reduction in screening time

View Full Case Study

Scrum Master Hiring Test FAQs

Can I combine multiple skills into one custom assessment?

Yes, absolutely. Custom assessments are set up based on your job description, and will include questions on all must-have skills you specify. Here's a quick guide on how you can request a custom test.

Do you have any anti-cheating or proctoring features in place?

We have the following anti-cheating features in place:

Non-googleable questions
IP proctoring
Screen proctoring
Web proctoring
Webcam proctoring
Plagiarism detection
Secure browser
Copy paste protection

Read more about the proctoring features.

How do I interpret test scores?

The primary thing to keep in mind is that an assessment is an elimination tool, not a selection tool. A skills assessment is optimized to help you eliminate candidates who are not technically qualified for the role, it is not optimized to help you find the best candidate for the role. So the ideal way to use an assessment is to decide a threshold score (typically 55%, we help you benchmark) and invite all candidates who score above the threshold for the next rounds of interview.

What experience level can I use this test for?

Each Adaface assessment is customized to your job description/ ideal candidate persona (our subject matter experts will pick the right questions for your assessment from our library of 10000+ questions). This assessment can be customized for any experience level.

Does every candidate get the same questions?

Yes, it makes it much easier for you to compare candidates. Options for MCQ questions and the order of questions are randomized. We have anti-cheating/ proctoring features in place. In our enterprise plan, we also have the option to create multiple versions of the same assessment with questions of similar difficulty levels.