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: Conhecimento da estrutura scrum e seus princípios Compreensão da metodologia ágil Proficiência no planejamento e execução de sprint Capacidade de gerenciar e priorizar o atraso do produto Experiência em escrever histórias de usuário eficazes Competência na realização de análises de iteração Proficiente em facilitar as reuniões diárias de stand-up Experiência na retrospectiva da retrospectiva Familiaridade com artefatos de scrum, como gráficos de Burndown Entendimento das funções e responsabilidades do scrum

Scrum Master Test

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

Scrum Estrutura ágil Planejamento de sprint Backlog do produto Histórias de usuário Revisão da iteração Stand-up diário Retrospectivo Artefatos de Scrum Funções de scrum Eventos Scrum

About the test:

O teste Scrum Master avalia o conhecimento e a compreensão de um candidato sobre a estrutura do Scrum, os princípios ágeis e o papel de um mestre de scrum. Os tópicos abordados incluem planejamento de sprint, gerenciamento de atraso de produtos, histórias de usuários, revisão de iteração, reuniões diárias de stand-up, retrospectivas, artefatos de scrum e funções de scrum.

Covered skills:

Scrum
Planejamento de sprint
Histórias de usuário
Stand-up diário
Artefatos de Scrum
Eventos Scrum

Estrutura ágil
Backlog do produto
Revisão da iteração
Retrospectivo
Funções de scrum

Preview this test

Ver Scorecard de amostra

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:

Capacidade de aplicar efetivamente os princípios e práticas do Scrum
Capacidade de facilitar reuniões de planejamento de sprint
Capacidade de gerenciar e priorizar o atraso do produto
Capacidade de escrever histórias de usuário claras e concisas
Capacidade de realizar revisões de iteração eficazes
Capacidade de liderar reuniões diárias de stand-up
Capacidade de facilitar sessões retrospectivas
Capacidade de entender e utilizar artefatos de scrum
Capacidade de desempenhar funções de scrum efetivamente
Capacidade de planejar e executar eventos de scrum
Capacidade de treinar e orientar membros da equipe
Capacidade de promover a colaboração e a auto-organização dentro da equipe

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

Preview this test

Ver Scorecard de amostra

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

Estes são apenas uma pequena amostra da nossa biblioteca de mais de 10.000 perguntas. As perguntas reais sobre isso Scrum Master Test será não-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)

Reason #4

1200+ customers in 75 countries

Com o Adaface, conseguimos otimizar nosso processo de seleção inicial em mais de 75%, liberando um tempo precioso tanto para os gerentes de contratação quanto para nossa equipe de aquisição de talentos!

Brandon Lee, Chefe de Pessoas, Love, Bonito

Preview this test

Ver Scorecard de amostra

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

Ver Scorecard de amostra

Preview this test

Ver Scorecard de amostra

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

Ver Scorecard de amostra

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:

Conhecimento da estrutura scrum e seus princípios
Compreensão da metodologia ágil
Proficiência no planejamento e execução de sprint
Capacidade de gerenciar e priorizar o atraso do produto
Experiência em escrever histórias de usuário eficazes
Competência na realização de análises de iteração
Proficiente em facilitar as reuniões diárias de stand-up
Experiência na retrospectiva da retrospectiva
Familiaridade com artefatos de scrum, como gráficos de Burndown
Entendimento das funções e responsabilidades do scrum

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?

Histórias de usuário </h4 > <p> Uma história do usuário é uma descrição concisa e informal do recurso de software desejado. Ele se concentra na perspectiva do usuário final e serve como espaço reservado para uma conversa entre a equipe de desenvolvimento e as partes interessadas. Medir essa habilidade no teste permite que os recrutadores avaliem a capacidade de um mestre de scrum de criar, refinar e priorizar histórias de usuário de maneira eficaz, garantindo uma comunicação clara e entendimento compartilhado. </p> <h4> Revisão da iteração
Revisão da iteração , também conhecido como Sprint Review, é uma reunião colaborativa em que a equipe do Scrum apresenta o trabalho concluído durante um sprint para as partes interessadas. Ele oferece uma oportunidade para obter feedback, adaptar o backlog do produto e planejar as próximas etapas. Essa habilidade é medida no teste para avaliar a proficiência de um mestre de scrum para facilitar as reuniões de revisão de iteração produtiva, garantindo insights valiosos e melhorias contínuas. é uma reunião curta e de caixa de tempo realizada pela equipe Scrum para sincronizar o trabalho e identificar quaisquer impedimentos. Envolve cada membro da equipe compartilhando o que eles fizeram, o que planejam fazer e se eles têm algum desafio. Avaliar essa habilidade no teste ajuda os recrutadores a avaliar a capacidade de um mestre de scrum de facilitar stand-ups diários eficazes, garantindo transparência, colaboração e alinhamento dentro da equipe.
retrospectiva
A retrospectiva é Uma reunião estruturada em que a equipe do Scrum reflete sobre o sprint passado e identifica áreas para melhorias. Ele se concentra em aprender com experiências e melhorar continuamente o desempenho da equipe. Medir essa habilidade no teste permite que os recrutadores avaliem a proficiência de um mestre de scrum na retrospectiva que promovam um ambiente seguro para comunicação aberta, feedback construtivo e planos de melhoria acionável.
artefatos de scrum
Os artefatos Scrum são os entregas tangíveis que oferecem transparência e oportunidades de inspeção e adaptação no Scrum. Eles incluem o backlog do produto, o sprint backlog e o incremento. Avaliar essa habilidade no teste ajuda os recrutadores a avaliar a compreensão de um mestre de scrum sobre como gerenciar e utilizar efetivamente artefatos de scrum para apoiar o processo de desenvolvimento e garantir o valor do produto. Defina as responsabilidades e responsabilidades dentro da estrutura SCRUM. Essas funções incluem o Scrum Master, o proprietário do produto e a equipe de desenvolvimento. Essa habilidade é medida no teste para avaliar o conhecimento de um mestre de scrum sobre os diferentes papéis, suas interações e seu impacto na implementação do scrum e no sucesso do projeto. Cerimônias em caixa de tempo que oferecem oportunidades regulares e previsíveis de inspeção e adaptação no Scrum. Eles incluem planejamento de sprint, stand-up diário, revisão de iteração e retrospectiva. Avaliar essa habilidade no teste permite que os recrutadores avaliem a compreensão de um mestre de scrum sobre as técnicas de fins, fluxo e facilitação de cada evento de scrum, garantindo colaboração efetiva e melhoria contínua.
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.
Introdução ao Scrum
Estrutura ágil
Valores de scrum
Funções de scrum
Proprietário do produto
Scrum Master
Equipe de desenvolvimento
Eventos Scrum
Planejamento de sprint
Stand-up diário
Sprint Review
Sprint retrospectiva
Artefatos de Scrum
Backlog do produto
Sprint backlog
Histórias de usuário
Critérios de aceitação
Definição de feito
Técnicas de estimativa
Planejando poker
Dimensionamento relativo
Pontos de história
Velocidade
Gráfico de queima
Placas de tarefas
Perguntas diárias do scrum
Resolução de impedimentos
Empoderamento da equipe
Técnicas de colaboração
Manifesto ágil
Estrutura scrum
Princípios ágeis
Benefícios de scrum
Adoção de scrum
Terminologia de Scrum
Cerimônias de scrum
Métricas de Scrum
Placa scrum
Reunião de Scrum
Scrum stand-up
Rastreamento de progresso do scrum
Documentação scrum
Ferramentas Scrum
Técnicas de Scrum
Práticas recomendadas de scrum
Scrum Desafios
Estudos de caso de Scrum
Recursos Scrum
Certificação Scrum
Entrevistas de Scrum

Preview this test

Ver Scorecard de amostra

What roles can I use the Scrum Master Test for?

Scrum Master
Proprietário do produto
Treinador ágil
Gestor de projeto
Gerente de liberação

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

Proficiência em coordenar eventos de scrum
Capacidade de fornecer orientação e orientação aos membros da equipe
Capacidade de identificar e resolver os impedimentos do projeto
Especialização na condução de reuniões Scrum of Scrums
Conhecimento de técnicas de facilitação para tomada de decisão colaborativa
Experiência no gerenciamento de equipes distribuídas ou remotas
Proficiência na criação e manutenção de um relacionamento do proprietário do produto
Capacidade de treinar e orientar os proprietários de produtos na priorização
Capacidade de lidar com a dinâmica e conflitos da equipe
Experiência no uso de ferramentas e software de gerenciamento de projetos ágeis
Proficiência na realização de sessões de treinamento e workshops para ágil e scrum

Preview this test

Ver Scorecard de amostra

Os gerentes de contratação sentiram que, por meio das perguntas técnicas feitas durante as entrevistas do painel, foram capazes de dizer quais candidatos tiveram melhores pontuações e diferenciaram aqueles que não tiveram pontuações tão boas. Eles são altamente satisfeito com a qualidade dos candidatos selecionados na triagem Adaface.

85%

Redução no tempo de triagem

Veja o estudo de caso completo

Scrum Master Hiring Test Perguntas frequentes

Posso combinar várias habilidades em uma avaliação personalizada?

Sim absolutamente. As avaliações personalizadas são configuradas com base na descrição do seu trabalho e incluirão perguntas sobre todas as habilidades obrigatórias que você especificar.

Você tem algum recurso anti-trapaça ou procurador?

Temos os seguintes recursos anti-trapaça:

Perguntas não-goleadas
IP Proctoring
Web Proctoring
Proctoring da webcam
Detecção de plágio
navegador seguro

Leia mais sobre os Recursos de Proctoring.

Como interpreto as pontuações dos testes?

O principal a ter em mente é que uma avaliação é uma ferramenta de eliminação, não uma ferramenta de seleção. Uma avaliação de habilidades é otimizada para ajudá -lo a eliminar os candidatos que não são tecnicamente qualificados para o papel, não é otimizado para ajudá -lo a encontrar o melhor candidato para o papel. Portanto, a maneira ideal de usar uma avaliação é decidir uma pontuação limite (normalmente 55%, ajudamos você a comparar) e convidar todos os candidatos que pontuam acima do limiar para as próximas rodadas da entrevista.

Para que nível de experiência posso usar este teste?

Cada avaliação do Adaface é personalizada para a descrição do seu trabalho/ persona do candidato ideal (nossos especialistas no assunto escolherão as perguntas certas para sua avaliação de nossa biblioteca de mais de 10000 perguntas). Esta avaliação pode ser personalizada para qualquer nível de experiência.

Todo candidato recebe as mesmas perguntas?

Sim, facilita muito a comparação de candidatos. As opções para perguntas do MCQ e a ordem das perguntas são randomizadas. Recursos anti-traking/proctoring no local. Em nosso plano corporativo, também temos a opção de criar várias versões da mesma avaliação com questões de níveis de dificuldade semelhantes.