Preguntas de entrevistas para Scrum master en Argentina
Un scrum master implementa la metodología Scrum en equipos de gestión y desarrollo de proyectos. El entrevistador busca aspirantes con agilidad mental y sólidas habilidades interpersonales. Buscan obtener respuestas que les ayuden a comprobar si tienes habilidades de liderazgo y a decidir si eres un buen candidato para el sistema Scrum existente en la empresa.
Preguntas de entrevista más frecuentes para scrum master y cómo responderlas
Estas son las tres preguntas de entrevista más comunes para el puesto de scrum master y cómo responderlas:
Pregunta n.º 1: ¿Qué significan para ti los tres pilares del método Scrum?
Respuesta recomendada: Esta es una información fundamental que todos los scrum master deberían saber. Aprovecha la pregunta para hablar sobre tu formación académica en Scrum. Enumera con cuidado los pilares y explica cómo influyen en tu forma de llevar a cabo tu trabajo. Aborda cualquier concepto erróneo común sobre los pilares para mostrar tus conocimientos sobre los avances en la teoría de Scrum.
Pregunta n.º 2: ¿Existe alguna situación en la que sustituirías otra teoría por la de Scrum?
Respuesta recomendada: A no ser que tengas información privilegiada sobre la empresa, no hay una respuesta correcta para esta pregunta. Algunas empresas siguen fielmente la teoría de Scrum y no la cambiarían por ningún otro paradigma. Otras son más flexibles y reconocen que hay situaciones en la que Scrum no sería la teoría más adecuada. Contesta de forma honesta y sincera. En el caso que digas que prefieres no optar por el método Scrum en algunos casos, explica por qué y vincula tu respuesta con los principios básicos de Scrum.
Pregunta n.º 3: ¿Cómo te comunicarías de forma eficaz con otros miembros del equipo Scrum?
Respuesta recomendada: El scrum master es el líder del equipo y el gestor de proyectos. El entrevistador evaluará tus habilidades interpersonales. Es posible que, en una ronda de entrevistas posterior, se te pida trabajar en un equipo Scrum actual de la empresa para ver cómo interactúas con los demás miembros del equipo.
Preguntas de entrevista principales
How would you explain story points to a team who's new to Agile/Scrum?
4 respuestas↳
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. Menos
↳
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. Menos
↳
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. Menos
As a woman do you forsee any childcare issues impacting delivery and how do you plan to deal with that?
4 respuestas↳
This question is sexist
↳
This is a real interview question???
↳
My babies are crate-trained. No issues.
How did you handle a technical situation?
4 respuestas↳
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. Menos
↳
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 Menos
1.How will you show the team performance to the higher management as velocity is not the very accurate way?
4 respuestas↳
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). Menos
↳
Customer satisfaction scores
Have you ever tracked velocity? How would you determine a teams Sprint velocity?
3 respuestas↳
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. Menos
↳
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. Menos
↳
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. Menos
How would you conduct a Scrum team retrospective?
3 respuestas↳
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. Menos
↳
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. Menos
Does a Scrum Master have to have experience with data warehousing in order to be a good Scrum Master for a data warehousing team?
2 respuestas↳
A chicken farmer must create an environment conducive to laying eggs, but need not accomplish that task personally. Menos
↳
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. Menos
Which one of the Scrum "events" would you remove if you had to?
2 respuestas↳
All scrum events have specific purpose in the scrum as per scrum guide. I would not remove any events, Menos
↳
The Sprint planning. Downsides: this would lead the Team to not commit to a Sprint goal, and work "sprinting" towards it. Also, possibly decrease effectiveness, due to the "Parkinson's law" effect. Upsides: still have all the other events to keep the quality and speed of work delivered. Team will move to a "kanban" work-style, still effective, but for different purpose. Menos
Que métricas usas en tu puesto actual.
2 respuestas↳
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 Menos
