The agile practitioner has determined that two different team members are working on addressing the same major issue on the project. How should the agile practitioner address this?
Haha, I can just imagine the team members fighting over who gets to work on the 'most important' issue. Maybe we should just flip a coin and be done with it? All joking aside, I think option A with the burnup chart and adding it to the backlog is the way to go. Transparency is key in agile, right?
You know, I was thinking the same thing, Ressie. Identifying the root cause and risks is crucial. But I also like the idea of getting the team involved in deciding on task allocation principles. That way, they'll have a say in how issues are handled going forward. Option D is worth considering too.
I'm not sure about that, Beatriz. Wouldn't it be better to conduct a root-cause analysis and identify any related risks? That way, we can address the underlying issue and prevent it from happening again. Option C seems like the most thorough approach to me.
Hmm, this seems like a tricky situation. I'm leaning towards option B - adding the issue to the kanban board and assigning it to the team member who's made the most progress. That way, we can track the resolution and ensure it doesn't get lost in the shuffle.
Shawna
2 months agoPaul
13 days agoLanie
16 days agoElvera
22 days agoMarkus
2 months agoKenny
2 months agoKristel
2 months agoJesusita
2 months agoRessie
2 months agoCatalina
1 months agoLeoma
1 months agoBeatriz
2 months agoRefugia
24 days agoGilma
1 months agoHyman
1 months agoAlberto
2 months ago