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

Visualizza la scorecard campione

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

Lo Scrum Master Test aiuta i reclutatori e i responsabili delle assunzioni a identificare i candidati qualificati da un pool di curriculum e aiuta a prendere decisioni oggettive di assunzione. Riduce il sovraccarico amministrativo di intervistare troppi candidati e risparmia tempo filtrando candidati non qualificati.

##Com

Esperienza in una squadra di scrum
Capacità di analizzare e pensare rapidamente e di risolvere il conflitto
Con una conoscenza delle tecniche per colmare le lacune nella mischia
Capacità di determinare cosa è la mischia e cosa non lo è
Esperienza con tecniche agili di successo
Capacità di lavorare e guidare una squadra
Comunicazione forte, interpersonali e mentoring

Le intuizioni generate da questa valutazione possono essere utilizzate dai reclutatori e dai responsabili delle assunzioni per identificare i migliori candidati per i ruoli Master Scrum. Le funzionalità anti-cheatri consentono di sentirti a tuo agio con le valutazioni conducenti online. Il test online di Scrum Master è ideale per aiutare i reclutatori a identificare quali candidati hanno le competenze per fare bene sul lavoro.

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.

Questi sono solo un piccolo campione della nostra biblioteca di oltre 10.000 domande. Le domande reali su questo Scrum Master Test sarà non googleabile.

🧐 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

Con Adaface, siamo stati in grado di ottimizzare il nostro processo di screening iniziale di oltre il 75%, liberando un tempo prezioso sia per i responsabili delle assunzioni che per il nostro team di acquisizione di talenti!

Brandon Lee, Capo delle persone, 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

Visualizza la scorecard campione

Informazioni sui ruoli di Scrum Master

Scrum è un framework che facilita il lavoro di squadra. Scrum incoraggia i team ad imparare attraverso le esperienze, si auto-organizza mentre lavora su un problema e riflette sulle loro vittorie e perdite per migliorare continuamente, proprio come una squadra di rugby (da cui si chiama).

Un Master Scrum aiuta nella supervisione del team di Scrum and Development. Sono esperti di approccio e scrum agili e possono educare gli altri in queste aree. Servono anche come cuscinetto tra il team Scrum e il proprietario del prodotto, contribuendo a mantenere la squadra al sicuro risolvendo i conflitti.

Le responsabilità tipiche di scrum master includono:

Guidare il team Scrum nell'uso della metodologia agile e delle pratiche di mischia
Aiutare il proprietario del prodotto e il team di sviluppo a raggiungere la soddisfazione del cliente
guidare i team di scrum e di sviluppo nell'auto-organizzazione
Rimozione degli impedimenti e allenando la squadra di Scrum sulla rimozione di impedimenti
Aiutare i team di mischia e di sviluppo a identificare e riempire gli spazi vuoti nel quadro Agile
Risoluzione di conflitti e questioni che si verificano
Aiutare il team Scrum a raggiungere livelli più elevati di maturità di mischia
Supportare il proprietario del prodotto e fornire istruzione dove necessario

What roles can I use the Scrum Master Test for?

Technical Project Manager
Scrum Master

What topics are covered in the Scrum Master Test?

Agile

Sprint

Valori di mischia

Pilastri

Storie

Storia dell'utente

Artefatti

Gestione del rischio

Timeboxing

Epico

Compiti

Incontro retrospettivo

Sprint 0

Arpione

Backlog del prodotto

Backlog Sprint

Definizione Done

Dod

Scrum quotidiana

Voto di fiducia

Mischia di scrums

Prodotto minimo praticabile

Mvp

Rilascio minimo commerciabile

Mmr

Velocità

Leader del servitore

Scope Creep

Preview this test

Visualizza la scorecard campione

I responsabili delle assunzioni hanno ritenuto che attraverso le domande tecniche che hanno posto durante le interviste del panel, sono stati in grado di dire quali candidati avevano punteggi migliori e si sono differenziati con coloro che non hanno segnato. Sono molto soddisfatto Con la qualità dei candidati selezionati con la proiezione di Adaface.

85%

Riduzione del tempo di screening

Visualizza il caso di studio completo

FAQ

Posso combinare più competenze in una valutazione personalizzata?

Si assolutamente. Le valutazioni personalizzate sono impostate in base alla descrizione del tuo lavoro e includeranno domande su tutte le competenze indispensabili che specificate.

Hai in atto delle caratteristiche anti-cheat o procuratore?

Abbiamo in atto le seguenti caratteristiche anti-cheat:

Domande non googiche
Proctoring IP
procuratore web
Proctor di webcam
Rilevamento del plagio
Sicuro browser

Leggi di più sulle caratteristiche di procuratore.

Come interpreto i punteggi dei test?

La cosa principale da tenere a mente è che una valutazione è uno strumento di eliminazione, non uno strumento di selezione. Una valutazione delle competenze è ottimizzata per aiutarti a eliminare i candidati che non sono tecnicamente qualificati per il ruolo, non è ottimizzato per aiutarti a trovare il miglior candidato per il ruolo. Quindi il modo ideale per utilizzare una valutazione è decidere un punteggio di soglia (in genere il 55%, ti aiutiamo a benchmark) e invitiamo tutti i candidati che segnano al di sopra della soglia per i prossimi round di intervista.

Per quale livello di esperienza posso usare questo test?

Ogni valutazione di Adaface è personalizzata per la descrizione del tuo lavoro/ personaggio del candidato ideale (i nostri esperti in materia sceglieranno le domande giuste per la tua valutazione dalla nostra biblioteca di oltre 10000 domande). Questa valutazione può essere personalizzata per qualsiasi livello di esperienza.

Ogni candidato riceve le stesse domande?

Sì, ti rende molto più facile confrontare i candidati. Le opzioni per le domande MCQ e l'ordine delle domande sono randomizzate. Abbiamo anti-cheatri/procuratore in atto. Nel nostro piano aziendale, abbiamo anche la possibilità di creare più versioni della stessa valutazione con questioni di difficoltà simili.