Questions d'entretiens - Scrum master
2 k
Questions d'entretien pour Scrum Master partagées par les candidatsPrincipales questions d'entretien
How would you explain story points to a team who's new to Agile/Scrum?
4 réponses↳
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
As a woman do you forsee any childcare issues impacting delivery and how do you plan to deal with that?
4 réponses↳
This question is sexist
↳
This is not an issue for me.
↳
My babies are crate-trained. No issues.
1.How will you show the team performance to the higher management as velocity is not the very accurate way?
4 réponses↳
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
↳
Ensuring quality supersedes speed
How did you handle a technical situation?
4 réponses↳
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
↳
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
Have you ever tracked velocity? How would you determine a teams Sprint velocity?
3 réponses↳
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
↳
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
↳
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
How would you conduct a Scrum team retrospective?
3 réponses↳
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
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 réponses↳
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
Which one of the Scrum "events" would you remove if you had to?
2 réponses↳
All scrum events have specific purpose in the scrum as per scrum guide. I would not remove any events, Moins
↳
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. Moins
Burn down chart User story journey
2 réponses↳
Technical went well But manager round was full of sarcacism
↳
How many round of interviews were there?
Name some challenges you face on the job
2 réponses↳
Resource challenges Knowledge Management challenges
↳
I told them my challenges