Scrum Master 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.

Get started for free

Preview questions

Screen candidates with a 30 mins test

Test duration: 30 mins

Difficulty level: Moderate

Availability: Ready to use

Questions:

15 Agile/Scrum MCQs

Covered skills:

Scrum

Agile Framework

Sprint Planning

Product Backlog

User Stories

Iteration Review

Daily Stand-up

Retrospective

Scrum Artifacts

Scrum Roles

Scrum Events

Get started for free

Preview questions

Use Adaface tests trusted by recruitment teams globally

Adaface is used by 1500+ businesses in 80 countries.

Adaface skill assessments measure on-the-job skills of candidates, providing employers with an accurate tool for screening potential hires.

Use the Scrum Master Assessment Test to shortlist qualified candidates

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

Get started for free

Preview questions

Screen candidates with the highest quality 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 15,000+ questions. The actual questions on this Scrum Master Test will be non-googleable.

🧐 Question
Medium Managing Dependencies Backlog Management Dependencies Cross-functional Teams	Solve
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	Solve
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	Solve
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	Solve
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	Solve
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	Solve
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	Solve
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	Solve
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	Solve
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	Solve
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	Solve
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	Solve
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)

Test candidates on core Scrum Master Hiring Test topics

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.

Get started for free

Preview questions

Make informed decisions with actionable reports and benchmarks

View sample scorecard

Screen candidates in 3 easy steps

Pick a test from over 500+ tests

The Adaface test library features 500+ tests to enable you to test candidates on all popular skills- everything from programming languages, software frameworks, devops, logical reasoning, abstract reasoning, critical thinking, fluid intelligence, content marketing, talent acquisition, customer service, accounting, product management, sales and more.

Invite your candidates with 2-clicks

Make informed hiring decisions

Get started for free

Preview questions

Try the most advanced candidate assessment platform

ChatGPT Protection

Non-googleable Questions

Web Proctoring

IP Proctoring

Webcam Proctoring

MCQ Questions

Coding Questions

Typing Questions

Personality Questions

Custom Questions

Ready-to-use Tests

Custom Tests

Custom Branding

Bulk Invites

Public Links

ATS Integrations

Multiple Question Sets

Custom API integrations

Role-based Access

Priority Support

GDPR Compliance

Pick a plan based on your hiring needs

The most advanced candidate screening platform.
14-day free trial. No credit card required.

From

$15

per month (paid annually)

View pricing plans

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

It's very easy to share assessments with candidates and for candidates to use. We get good feedback from candidates about completing the tests. Adaface are very responsive and friendly to deal with.

Kirsty Wood, Human Resources, WillyWeather

We were able to close 106 positions in a record time of 45 days! Adaface enables us to conduct aptitude and psychometric assessments seamlessly. My hiring managers have never been happier with the quality of candidates shortlisted.

Amit Kataria, CHRO, Hanu

We evaluated several of their competitors and found Adaface to be the most compelling. Great library of questions that are designed to test for fit rather than memorization of algorithms.

Swayam Narain, CTO, Affable