Les Scrum Masters mettent en œuvre le cadre Scrum pour les équipes de gestion de projet et de développement. Les personnes faisant passer l’entretien recherchent des personnes dotées d’une grande agilité mentale et de solides compétences interpersonnelles. Ils veulent obtenir des réponses qui leur permettront de décider si vous avez des compétences de leadership et si vous pouvez vous intégrer au système Scrum déjà en place dans l’entreprise.
Voici trois des questions d’entretien d’embauche les plus fréquentes pour un Scrum Master (H/F) et comment y répondre :
Comment répondre : Il s’agit d’informations de base que tout Scrum Master devrait connaître. Profitez de la question pour parler de votre formation en Scrum. Énumérez soigneusement les piliers et la manière dont ils influencent votre approche du travail. Abordez les idées reçues les plus courantes au sujet des piliers, afin de démontrer votre connaissance des développements de la théorie Scrum.
Comment répondre : À moins que vous n’ayez un scoop sur l’entreprise, il n’y a pas de bonne réponse à cette question. Certains employeurs sont attachés à la théorie Scrum et ils ne la remplaceraient pour rien au monde par un autre paradigme. D’autres sont flexibles et admettent que, dans certaines circonstances, Scrum n’est peut-être pas la meilleure théorie à utiliser. Soyez honnête et sincère. Si vous vous écartez de Scrum, expliquez pourquoi et reliez votre réponse aux principes fondamentaux de Scrum.
Comment répondre : Le Scrum Master est à la fois le chef d’équipe et le chef de projet. La personne faisant passer l’entretien souhaite évaluer vos compétences interpersonnelles. Lors d’un entretien ultérieur, la personne faisant passer l’entretien pourrait vous intégrer à l’équipe Scrum actuelle de l’entreprise et observer vos interactions avec les membres de l’équipe.
↳
Time vs effort.. teams get hung up on time based estimates. And not about the amount of effort it's going to take to accomplish a task/user story. Moins
↳
It’s about demonstrating it to them and comparing the efficacy compare to other frameworks via dissecting a story vertically to the smallest size possible. Moins
↳
I said I would talk to them about t-shirt sizing and try several ways to help them understand that story estimation has little to nothing to do with time, rather effort. I also explained that this was a challenging topic for a new team. Moins
↳
This question is sexist
↳
This is a real interview question???
↳
My babies are crate-trained. No issues.
↳
Take a root cause analysis and run with the outcome, reach out to parties involve in solving the issue and give constant update for transparency. Moins
↳
How difficult was the assessment, and would you recommend anything for prepping?
↳
assessments were not that hard in my opinion. I think the interview itself was harder Moins
↳
Ensuring quality supersedes speed
↳
Burn down charts, any other relevant quality metrics. Velocity is used to estimate basically (may use as one of the parameters to showcase performance also). Moins
↳
Customer satisfaction scores
↳
Team velocity is tracked, using the number of estimated story points, over the actual completed story points. This can be measured on the burndown chart. You can guesstimate your team velocity overtime, from the previous sprints. Moins
↳
Velocity is the total story point the team complete in a sprint. It can be tracked in the burndown chart in Jira for instance. Can be determined for an existing team by adding up velocities of 3 sprints and dividing it by 3 to get teams velocity. Moins
↳
I said that I had a little bit, as we still had a bit of a challenge on my last team comprehending the burndown chart and how to improve estimates. How to determine it would be based on the Sprints. I kind of fumbled through this one as I really hadn't ever had much velocity tracking training, I just winged it at that time. Moins
↳
What was your background check process like? How long did it take?
↳
The background check was done by a third party company I believe. It took about a week. They only came back to me with one question around verifying my college degree; I sent back a photo of my college diploma and that closed the item. Otherwise, the background check was non eventful. Moins
↳
I would start off by asking about the positive things that happened during the last sprint. Then I would ask about the things that maybe could be done better or would make the team experience smoother. Once these items are all on the table the team would work together to prioritize the improvement items and we would assign action items and owners to get the highest priority items into backlog to work on in an upcoming sprint. Moins
↳
A chicken farmer must create an environment conducive to laying eggs, but need not accomplish that task personally. Moins
↳
The clerk in the store doesn't need to know how to grow strawberries; she just needs to know the process of ringing them up and getting them to the customer. So no, Scrum Masters don't need to know, in-depth, about data warehousing an business intelligence to help a team transition to scrum. Moins
↳
No usamos métricas.
↳
Métricas de eficiencia como Velocity, Lead Time, burndown para que el equipo pueda tomar sus decisiones basados en métricas y generar el valor esperando a cada ciclo Moins
↳
Resource challenges Knowledge Management challenges
↳
I told them my challenges