Exam PMI-ACP topic 1 question 75 discussion

I would go for (A) here. It is quite common that a task takes more time than originally estimated. No reason to postpone its implementation.

The best course of action for the project team is A. Continue working on the task until it is completed. Reasoning: Commitment to the Sprint Goal: If the task is already on the iteration backlog, it was committed to during sprint planning. The team should strive to complete what was committed to in the current sprint. Collaboration and Adjustment: The team can discuss how to adjust other work in the sprint to accommodate the additional time required for the task. This might involve reassigning tasks or negotiating with the product owner about what can be realistically completed within the sprint. Avoiding Disruption: Stopping work on the task or adding resources mid-sprint can cause disruption and may not be practical. The team should aim to complete the task to avoid carrying unfinished work into the next iteration, which could cause further delays.

I think C would be good approach. Swarming - move resource in team to hindered task, could be right solution in this case. Compared with C, other options have following issues, I think. Option-A: team already understand that they can't finish targeted task/story with current pace. So taking Option-A approach result "remaining WIP" that is no value item in this sprint. Option-B: removed task owner = no member work on this task. Team committed to work on this story but they won't do from now on without telling anything to Product Owner. D: same reason of Optin-B, they should consult with Product Owner at first. if the text of Option-D includes something additional condition that "team contacted to Product Owner to reprioritize sprint backlog and agreed achieving level in this sprint", I agree with Option-B (best one).

I vote A., it's not uncommon for tasks to take longer than estimated. This is normally negotiated with the PO in case the task would take up too much of the Sprint's allotted time-frame, and would need to be broken down into smaller tasks or migrated back to the Product backlog.

(checked with ChatGPT) The most appropriate course of action is: D. Stop working on the task and include it in the next iteration. This aligns with Agile principles, specifically the concept of timeboxing and the importance of delivering a potentially shippable product increment at the end of each iteration. If a task is deemed unlikely to be completed within the current iteration, it is generally more effective to stop working on it, include it in the next iteration's backlog, and focus on delivering the highest-priority items within the current timebox. Option A suggests continuing to work on the task until it is completed, which may compromise the timebox and disrupt the planned delivery schedule.

go with A

D = correct The remaining work that is not completed within the current sprint, has to be added in the next one. If it is important it has to be prioritized. It is confusing that is missing information - does this information task can be done within the current sprint (among others, considering the importance) or it can be done at all in the current sprint? Anyway, more logical to me is D.

Vote A

Option C. Agile teams value responding to change and adapting their plans based on feedback and insights gained during the iteration. Therefore, if the team realizes that a task will take more time than originally estimated, they should adjust their plans to address this issue. Adding resources, such as additional team members or tools, can help the team complete the task within the iteration's timeframe while maintaining the expected quality standards. This approach supports collaboration, continuous improvement, and delivering value to the customer.

“swarming” to describe collective problem solving—this can take the form of multiple people pitching in to help finish a task, remove a bottleneck, or move a deliverable across the line to production readiness. "A" not good -> "until it is completed" ???

A is correct.

eliminate(A) to continue to finish the task may exceed the iteration timebox eliminate(B) to remove the task will reduce value. eliminate(C) the issuse is wrong estimation resulting in no enough to complete it, not skill set of the team. I go for (D) Stop working on the task witch will delay the timebox and plan it in the next iteration. Then the timebox legnth keeps the same. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

eliminate(A) to continue to finish the task will exceed the iteration timebox eliminate(B) to remove the task will reduce value. eliminate(C) the issuse is wrong estimation resulting in no enough to complete it, not skill set of the team. (D) Stop working on the task that will delay the timebox and plan it in the next iteration. This iteration goal is still value delivery, because it does not mention the impact of value delivery

A sure

A: correct. B: if we do like this, who will confident to give the estimation and owner for the task in the project? C: This question is saying that the actual task is lager than estimated. if ask other member involve to this important task: will we reduce the completion time? lost focus on switching task? other task can finish within the sprint? D: Move to next iteration will help to the completion time equal estimated time? is it still important if we can move to next sprint?

The keyword is IMPORTANT task...i.e the task could affect that sprint goal within the time box allotted, so it should be stopped and included in the next iteration.

A. No doubt leftovers will be putting back to backlog but it it not necessary to stop building the same.