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

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

De Scrum Master -test helpt recruiters en aanwervingsmanagers gekwalificeerde kandidaten te identificeren uit een pool van cv's en helpt bij het nemen van objectieve aanwervingsbeslissingen. Het vermindert de administratieve overhead van het interviewen van te veel kandidaten en bespaart tijd door ongekwalificeerde kandidaten uit te filteren.

De adaface scrum master online testschermen kandidaten voor de typische vaardigheden die recruiters zoeken naar scrum master rollen:

Ervaring in een Scrum -team
Mogelijkheid om snel te analyseren en na te denken en conflicten op te lossen
Kennis van technieken om gaten in de scrum in te vullen
Mogelijkheid om te bepalen wat scrum is en wat niet is
Ervaring met succesvolle agile technieken
Mogelijkheid om met een team te werken en een team te leiden
Sterke communicatie, interpersoonlijke en mentorvaardigheden

De inzichten die uit deze beoordeling worden gegenereerd, kunnen worden gebruikt door recruiters en het inhuren van managers om de beste kandidaten te identificeren voor scrum master -rollen. Anti-lietfuncties stellen u in staat om comfortabel te zijn met het online uitvoeren van beoordelingen. De online online test van Scrum Master is ideaal om recruiters te helpen identificeren welke kandidaten de vaardigheden hebben om het goed te doen op het werk.

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.

Dit zijn slechts een klein monster uit onze bibliotheek met meer dan 10.000 vragen. De werkelijke vragen hierover Scrum Master Test zal niet-googelbaar zijn.

🧐 Question
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 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	2 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
	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	2 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

Met Adaface konden we ons eerste screeningproces optimaliseren met meer dan 75%, waardoor we kostbare tijd vrijmaken voor zowel wervingsmanagers als ons talent -acquisitieteam!

Brandon Lee, Hoofd van mensen, 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 & comparative results

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

Bekijk Sample Scorecard

Over Scrum Master Rollen

Scrum is een raamwerk dat teamwerk mogelijk maakt. Scrum moedigt teams aan om te leren via ervaringen, zelforganiseren tijdens het werken aan een probleem en nadenken over hun overwinningen en verliezen om voortdurend te verbeteren, net als een rugbyteam (waaruit het zijn naam krijgt).

Een scrum -meester helpt bij het toezicht van het Scrum- en Ontwikkelingsteam. Ze zijn goed thuis in Agile Approach en Scrum en kunnen anderen opleiden op deze gebieden. Ze dienen ook als een buffer tussen het Scrum -team en de producteigenaar, waardoor het team veilig wordt gehouden door conflicten op te lossen.

Typische scrum -meesterverantwoordelijkheden zijn onder meer:

Leiding van het Scrum -team in het gebruik van Agile Methodology en Scrum -praktijken
Het helpen van de producteigenaar en het ontwikkelingsteam om klanttevredenheid te bereiken
Leiding van de scrum- en ontwikkelingsteams in zelforganisatie
Het verwijderen van belemmeringen en het coachen van het scrum -team bij het verwijderen van belemmeringen
Het helpen van de scrum- en ontwikkelingsteams om lege plekken in het Agile Framework te identificeren en in te vullen
Het oplossen van conflicten en problemen die zich voordoen
Het scrum -team helpen hogere niveaus van scrum -volwassenheid te bereiken
Ondersteuning van de producteigenaar en het verstrekken van onderwijs waar nodig

What roles can I use the Scrum Master Test for?

Technical Project Manager
Scrum Master

What topics are covered in the Scrum Master Test?

Weerbaar

Sprint

Scrum -waarden

Pilaren

Verhalen

Gebruikersverhaal

Artefacten

Risicomanagement

Timeboxing

Episch

Taken

Retrospectieve bijeenkomst

Sprint 0

Piek

Product -achterstand

Sprint achterstand

Definitie van gedaan

Dod

Dagelijkse scrum

Vertrouwensstem

Scrum van scrums

Minimaal levensvatbaar product

MVP

Minimale verhandelbare release

MMR

Snelheid

Dienaar leider

Scope kruip

Preview this test

Bekijk Sample Scorecard

De aanwervingsmanagers vonden dat door de technische vragen die ze tijdens de interviews van het panel stelden, ze konden vertellen welke kandidaten betere scores hadden, en onderscheidden zich met degenen die niet zo goed scoor. Zij zijn zeer tevreden met de kwaliteit van kandidaten genomineerd met de ADAFACE -screening.

85%

Vermindering van de screeningstijd

Bekijk volledige case study

FAQ's

Kan ik meerdere vaardigheden combineren in één aangepaste beoordeling?

Ja absoluut. Aangepaste beoordelingen zijn opgezet op basis van uw functiebeschrijving en bevatten vragen over alle must-have vaardigheden die u opgeeft.

Heeft u functies tegen latere of proctoring op hun plaats?

We hebben de volgende anti-cheating-functies op zijn plaats:

Niet-googelbare vragen
IP Proctoring
Web Proctoring
Webcam Proctoring
Plagiaatdetectie
Beveilig browser

Lees meer over de Proctoring -functies.

Hoe interpreteer ik testscores?

Het belangrijkste om in gedachten te houden is dat een beoordeling een eliminatietool is, geen selectietool. Een vaardighedenbeoordeling is geoptimaliseerd om u te helpen kandidaten te elimineren die niet technisch gekwalificeerd zijn voor de rol, het is niet geoptimaliseerd om u te helpen de beste kandidaat voor de rol te vinden. Dus de ideale manier om een beoordeling te gebruiken is om een drempelscore te bepalen (meestal 55%, wij helpen u benchmark) en alle kandidaten uit te nodigen die boven de drempel scoren voor de volgende interviewrondes.

Voor welk ervaringsniveau kan ik deze test gebruiken?

Elke ADAFACE -beoordeling is aangepast aan uw functiebeschrijving/ ideale kandidaatpersonage (onze experts van het onderwerp zullen de juiste vragen kiezen voor uw beoordeling uit onze bibliotheek van 10000+ vragen). Deze beoordeling kan worden aangepast voor elk ervaringsniveau.

Krijgt elke kandidaat dezelfde vragen?

Ja, het maakt het veel gemakkelijker voor u om kandidaten te vergelijken. Opties voor MCQ -vragen en de volgorde van vragen worden gerandomiseerd. We hebben anti-cheating/proctoring functies. In ons bedrijfsplan hebben we ook de optie om meerdere versies van dezelfde beoordeling te maken met vragen over vergelijkbare moeilijkheidsniveaus.