A Scrum team failed to meet the Sprint objectives. One of the key members of the team fell ill and was away for two days right at the beginning of the four week Sprint.
What is the most likely reason that the team did not meet the Sprint objectives?
I'm leaning towards C as well. When you lose a critical team member like that, especially at the start, it's going to require some serious re-planning to get back on track. The team must not have been prepared for that kind of disruption.
The team being over-worked seems like a possible reason, but I'm not sure that's the most likely one here. With a key member out, I think the planning issue is probably the bigger factor.
I'm a bit confused on this one. Could it be that the team is lacking skills? If they were missing a key skillset with that team member out, that could have really impacted their ability to get the work done.
Hmm, this seems like a tricky one. I'm thinking it might be the team not planning the Sprint effectively, since the loss of a key member right at the start could have really thrown off their plans.
I'm pretty confident the answer is C - the team did not plan the Sprint effectively. Losing a key member right at the start is a major disruption, so they must not have accounted for that properly in their planning.
B) The team is lacking skills. Losing a key member for two days is a significant setback, so the team may not have had the necessary skills to compensate.
Gianna
3 months agoMerilyn
3 months agoMillie
3 months agoBarrett
4 months agoCaitlin
4 months agoAzalee
4 months agoMalcom
4 months agoTamra
4 months agoArlette
5 months agoGregoria
5 months agoKirk
5 months agoKenneth
5 months agoJames
5 months agoLyla
5 months agoAn
1 year agoReita
1 year agoMarvel
1 year agoNakita
1 year agoRene
1 year agoBrice
1 year agoChaya
1 year agoDalene
1 year agoCherelle
1 year agoMarisha
1 year agoTrevor
1 year agoLinn
1 year agoWilford
1 year agoBelen
1 year agoIndia
1 year agoSherell
1 year ago