Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

PMI-ACP Exam - Topic 3 Question 87 Discussion

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?
B) Add the issue to the kanban board and assign the it to the team member who has made the most progress on resolving it.
A) Implement a burnup chart and add the issue resolution as a task to the product backlog for the customer to prioritize.
C) Conduct a root-cause analysis on the issue and identify related risks and risk response owners at the next retrospective.
D) Document all project issues in a common space and ask the team members to decide on task allocation principles.

PMI-ACP Exam - Topic 3 Question 87 Discussion

Actual exam question for PMI's PMI-ACP exam
Question #: 87
Topic #: 3
[All PMI-ACP Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Sol at Sep 15, 2024, 06:31 PM

Limited Time Offer

25%

Off

Get Premium PMI-ACP Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Linsey
6 months ago
Wait, why not just let them collaborate instead of competing?
upvoted 0 times
...
Cherelle
6 months ago
C could be useful too, but it feels like it might slow things down.
upvoted 0 times
...
Cassie
7 months ago
Not sure about that, what if the other member has better insights?
upvoted 0 times
...
Jeannine
7 months ago
Totally agree, let the one who’s closer to a solution take the lead!
upvoted 0 times
...
Narcisa
7 months ago
I think option B makes the most sense.
upvoted 0 times
...
Jenelle
7 months 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.
upvoted 0 times
...
Andra
8 months 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.
upvoted 0 times
...
Marla
8 months 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.
upvoted 0 times
...
Eladia
8 months 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.
upvoted 0 times
...
Linn
8 months 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.
upvoted 0 times
...
Loreta
8 months 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.
upvoted 0 times
...
Chery
8 months 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.
upvoted 0 times
...
Devon
8 months 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.
upvoted 0 times
...
Tom
8 months 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.
upvoted 0 times
...
Shawna
1 year 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?
upvoted 0 times
Paul
1 year ago
It's all about collaboration and transparency in agile, so I think option A is the best approach here.
upvoted 0 times
...
Lanie
1 year ago
I think adding it to the backlog for the customer to prioritize makes sense. Let them decide what's most important.
upvoted 0 times
...
Elvera
1 year ago
Yeah, that would definitely be a fair way to decide. But I agree, transparency is important in agile.
upvoted 0 times
...
...
Markus
1 year 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.
upvoted 0 times
...
Kenny
1 year ago
I think conducting a root-cause analysis and identifying related risks is also important for addressing the issue.
upvoted 0 times
...
Kristel
1 year ago
I agree with Jesusita. It's important for the customer to prioritize the issue.
upvoted 0 times
...
Jesusita
1 year ago
I think we should implement a burnup chart and add the issue to the product backlog.
upvoted 0 times
...
Ressie
1 year 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.
upvoted 0 times
Catalina
1 year ago
Let's go with option C then. It seems like the most comprehensive solution.
upvoted 0 times
...
Leoma
1 year ago
I agree with you, Maria. Conducting a root-cause analysis can help us understand the issue better.
upvoted 0 times
...
...
Beatriz
1 year 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.
upvoted 0 times
Refugia
1 year ago
Definitely. It will also help in maintaining transparency and accountability within the team.
upvoted 0 times
...
Gilma
1 year ago
Assigning it to the team member who has made the most progress seems like a fair way to handle it.
upvoted 0 times
...
Hyman
1 year ago
I agree. It will help avoid duplication of work and ensure efficient resolution.
upvoted 0 times
...
Alberto
1 year ago
That sounds like a good idea. It's important to keep track of the progress on the major issue.
upvoted 0 times
...
...

Save Cancel