Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

PMI Exam PMI-ACP 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

Contribute your Thoughts:

Shawna
2 months 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
13 days ago
It's all about collaboration and transparency in agile, so I think option A is the best approach here.
upvoted 0 times
...
Lanie
16 days 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
22 days ago
Yeah, that would definitely be a fair way to decide. But I agree, transparency is important in agile.
upvoted 0 times
...
...
Markus
2 months 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
2 months ago
I think conducting a root-cause analysis and identifying related risks is also important for addressing the issue.
upvoted 0 times
...
Kristel
2 months ago
I agree with Jesusita. It's important for the customer to prioritize the issue.
upvoted 0 times
...
Jesusita
2 months ago
I think we should implement a burnup chart and add the issue to the product backlog.
upvoted 0 times
...
Ressie
2 months 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 months ago
Let's go with option C then. It seems like the most comprehensive solution.
upvoted 0 times
...
Leoma
1 months ago
I agree with you, Maria. Conducting a root-cause analysis can help us understand the issue better.
upvoted 0 times
...
...
Beatriz
2 months 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
24 days ago
Definitely. It will also help in maintaining transparency and accountability within the team.
upvoted 0 times
...
Gilma
1 months 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 months ago
I agree. It will help avoid duplication of work and ensure efficient resolution.
upvoted 0 times
...
Alberto
2 months 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
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77