Discuss PMI PMI-ACP Exam Topic 3 Question 87

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?

AImplement a burnup chart and add the issue resolution as a task to the product backlog for the customer to prioritize.

BAdd the issue to the kanban board and assign the it to the team member who has made the most progress on resolving it.

CConduct a root-cause analysis on the issue and identify related risks and risk response owners at the next retrospective.

DDocument all project issues in a common space and ask the team members to decide on task allocation principles.

Suggested Answer: B

Get Premium PMI-ACP Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

30 comments · newest first

Linsey 11 months ago

Wait, why not just let them collaborate instead of competing?

Cherelle 11 months ago

C could be useful too, but it feels like it might slow things down.

Cassie 12 months ago

Not sure about that, what if the other member has better insights?

Jeannine 12 months ago

Totally agree, let the one who’s closer to a solution take the lead!

Narcisa 1 year ago

I think option B makes the most sense.

Jenelle 1 year ago

I like the idea of documenting issues in a common space from option D, but I'm not sure how effective it would be for immediate task allocation. It could lead to confusion instead of clarity.

Andra 1 year ago

Conducting a root-cause analysis sounds like a thorough approach, but I wonder if we have time for that in the next retrospective. Option C might be too slow for this situation.

Marla 1 year ago

I remember a practice question where we discussed prioritizing tasks in the backlog. Option A seems like it could work, but it feels a bit indirect for resolving an immediate issue.

Eladia 1 year ago

I think option B makes sense because assigning the task to the team member who has made progress could help streamline the resolution. But I'm not entirely sure if that's the best approach.

Linn 1 year ago

I like the idea of option A, adding the issue to the product backlog and using a burnup chart to track progress. That way the customer can prioritize it, and we can keep a close eye on the resolution.

Loreta 1 year ago

I'm a bit confused by this question. I'm not sure if I fully understand the differences between the options. Maybe I'll need to review my agile practices before the exam.

Chery 1 year ago

Option C sounds like the best approach to me. Conducting a root-cause analysis and identifying risks and owners at the next retrospective will help us get to the bottom of this issue and prevent it from happening again.

Devon 1 year ago

Hmm, I'm a bit unsure about this one. I think I'd lean towards option D and get the team to decide on the task allocation principles. That way we can avoid any confusion going forward.

Tom 1 year ago

This seems like a straightforward agile issue. I'd go with option B and assign the task to the team member who has made the most progress.

Shawna 2 years ago

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?

Paul 1 year ago

↳ replying to Shawna

It's all about collaboration and transparency in agile, so I think option A is the best approach here.

Lanie 1 year ago

↳ replying to Shawna

I think adding it to the backlog for the customer to prioritize makes sense. Let them decide what's most important.

Elvera 1 year ago

↳ replying to Shawna

Yeah, that would definitely be a fair way to decide. But I agree, transparency is important in agile.

Markus 2 years ago

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.

Kenny 2 years ago

I think conducting a root-cause analysis and identifying related risks is also important for addressing the issue.

Kristel 2 years ago

I agree with Jesusita. It's important for the customer to prioritize the issue.

Jesusita 2 years ago

I think we should implement a burnup chart and add the issue to the product backlog.

Ressie 2 years ago

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.

Catalina 1 year ago

↳ replying to Ressie

Let's go with option C then. It seems like the most comprehensive solution.

Leoma 1 year ago

↳ replying to Ressie

I agree with you, Maria. Conducting a root-cause analysis can help us understand the issue better.

Beatriz 2 years ago

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.

Refugia 1 year ago

↳ replying to Beatriz

Definitely. It will also help in maintaining transparency and accountability within the team.

Gilma 1 year ago

↳ replying to Beatriz

Assigning it to the team member who has made the most progress seems like a fair way to handle it.

Hyman 1 year ago

↳ replying to Beatriz

I agree. It will help avoid duplication of work and ensure efficient resolution.

Alberto 2 years ago

↳ replying to Beatriz

That sounds like a good idea. It's important to keep track of the progress on the major issue.

PMI-ACP Exam - Topic 3 Question 87 Discussion