Scrum Master Test

About the test:

The scrum master test assesses a candidate's understanding of agile scrum principles and their ability to apply them in real life scenarios.

Covered skills:

General
Sprint
Story Points
Sprint Backlog
Sprint Planning
Sprint Length

Charts
Impediments
Sprint Retrospective
Scrum Meeting
Sprint Review

See all covered skills

Preview this test

Vis eksempler på scorecard

9 reasons why

Adaface Scrum Master Test is the most accurate way to shortlist Technical Project Managers

Reason #1

Tests for on-the-job skills

Scrum Master -testen hjelper rekrutterere og ansettelsesledere med å identifisere kvalifiserte kandidater fra et basseng med CV, og hjelper til med å ta objektive ansettelsesbeslutninger. Det reduserer den administrative overhead ved å intervjue for mange kandidater og sparer tid ved å filtrere ut ukvalifiserte kandidater.

The Adaface Scrum Master Online Test Screens Kandidater for de typiske ferdighetene Rekrutterere ser etter Scrum Master -roller:

Erfaring på et Scrum -team
Evne til å analysere og tenke raskt og å løse konflikter
Knowlederable om teknikker for å fylle ut hull i skrummet
Evne til å bestemme hva som er Scrum og hva som ikke er
Erfaring med vellykkede smidige teknikker
Evne til å jobbe med og lede et team
Sterk kommunikasjon, mellommenneskelige og mentorferdigheter

Innsikten som genereres fra denne vurderingen kan brukes av rekrutterere og ansettelsesledere for å identifisere de beste kandidatene for Scrum Master -roller. Anti-juksede funksjoner gjør at du kan være komfortabel med å gjennomføre vurderinger på nettet. Scrum Master Online -testen er ideell for å hjelpe rekrutterere med å identifisere hvilke kandidater som har ferdighetene til å gjøre det bra på jobben.

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.

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 ->

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.

Dette er bare en liten prøve fra biblioteket vårt med 10.000+ spørsmål. De faktiske spørsmålene om dette Scrum Master Test vil være ikke-googlable.

🧐 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)

Reason #4

1200+ customers in 75 countries

Med Adaface klarte vi å optimalisere vår første screeningprosess med oppover 75%, og frigjøre dyrebare tid for både ansettelsesledere og vårt talentinnsamlingsteam!

Brandon Lee, Menneskers leder, Love, Bonito

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.

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

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

Preview this test

Vis eksempler på scorecard

Om Scrum Master -roller

Scrum er et rammeverk som letter teamarbeid. Scrum oppfordrer team til å lære via opplevelser, selvorganisere mens de jobber med et spørsmål, og reflektere over deres seire og tap for kontinuerlig å forbedre seg, omtrent som et rugby-lag (hvorfra det får navnet).

En Scrum Master hjelper til med tilsyn av Scrum and Development Team. De er godt kjent med smidig tilnærming og skrum og kan utdanne andre på disse områdene. De fungerer også som en buffer mellom Scrum -teamet og produktseieren, og hjelper til med å holde teamet trygt ved å løse konflikter.

Typiske Scrum Master -ansvar inkluderer:

Lede Scrum -teamet i bruk av smidig metodikk og scrum -praksis
Hjelpe produktseieren og utviklingsteamet med å oppnå kundetilfredshet
Lede skrum- og utviklingsteamene i selvorganisering
Fjerning av hindringer og coaching Scrum -teamet for å fjerne hindringer
Hjelpe skrum- og utviklingsteamene til å identifisere og fylle ut emner i Agile Framework
Å løse konflikter og problemer som oppstår
Hjelpe Scrum -teamet med å oppnå høyere nivåer av Scrum modenhet
støtte produkteieren og gi utdanning der det er nødvendig

What roles can I use the Scrum Master Test for?

Technical Project Manager
Scrum Master

What topics are covered in the Scrum Master Test?

Smidig

Sprint

Scrum verdier

Søyler

Historier

Brukerhistorie

Gjenstander

Risikostyring

TIMEBOKSING

Episk

Oppgaver

Retrospektivt møte

Sprint 0

Spike

Produktets etterslep

Sprint Backlog

Definisjon av ferdig

DOD

Daglig skrum

Tillit stemme

Scrum av Scrums

Minimum levedyktig produkt

MVP

Minimum salgbar utgivelse

MMR

Hastighet

Tjenerleder

Omfang kryp

Preview this test

Vis eksempler på scorecard

Ansettelseslederne følte at de gjennom de tekniske spørsmålene de stilte under panelintervjuene, kunne fortelle hvilke kandidater som hadde bedre score, og differensierte med de som ikke scoret også. De er Svært fornøyd med kvaliteten på kandidatene på listen med adaface -screeningen.

85%

Reduksjon i screeningstid

Se hele casestudien

Vanlige spørsmål

Kan jeg kombinere flere ferdigheter til en tilpasset vurdering?

Ja absolutt. Tilpassede vurderinger er satt opp basert på stillingsbeskrivelsen din, og vil inneholde spørsmål om alle må-ha ferdigheter du spesifiserer.

Har du noen anti-juksende eller proktoreringsfunksjoner på plass?

Vi har følgende anti-juksede funksjoner på plass:

Ikke-googlable spørsmål
IP Proctoring
Nettproctoring
Webcam Proctoring
Deteksjon av plagiering
Sikker nettleser

Les mer om Proctoring -funksjonene.

Hvordan tolker jeg testresultater?

Den viktigste tingen å huske på er at en vurdering er et eliminasjonsverktøy, ikke et seleksjonsverktøy. En ferdighetsvurdering er optimalisert for å hjelpe deg med å eliminere kandidater som ikke er teknisk kvalifisert for rollen, det er ikke optimalisert for å hjelpe deg med å finne den beste kandidaten for rollen. Så den ideelle måten å bruke en vurdering på er å bestemme en terskelpoeng (vanligvis 55%, vi hjelper deg med å benchmark) og invitere alle kandidater som scorer over terskelen for de neste rundene med intervjuet.

Hvilken opplevelsesnivå kan jeg bruke denne testen til?

Hver ADAFACE -vurdering er tilpasset din stillingsbeskrivelse/ ideell kandidatperson (våre fageksperter vil velge de riktige spørsmålene for din vurdering fra vårt bibliotek med 10000+ spørsmål). Denne vurderingen kan tilpasses for ethvert opplevelsesnivå.

Får hver kandidat de samme spørsmålene?

Ja, det gjør det mye lettere for deg å sammenligne kandidater. Alternativer for MCQ -spørsmål og rekkefølgen på spørsmål er randomisert. Vi har anti-juksing/proctoring funksjoner på plass. I vår bedriftsplan har vi også muligheten til å lage flere versjoner av den samme vurderingen med spørsmål med lignende vanskelighetsnivåer.