Exam PMI-ACP topic 1 question 243 discussion

Option D: Just-in-time exploration allows the team to work closely with the customer to clarify the functionality as the feature is being developed. This approach supports ongoing collaboration and feedback, which is key in Agile, particularly when requirements are unclear. Option A: Creating a spike story focuses on reducing technical risk, but in this case, the main issue is understanding the feature's functionality, not necessarily technical uncertainty. Option B: Starting an iteration 0 to investigate may cause unnecessary delays and isn’t always needed unless there are significant unknowns. Just-in-time exploration is more efficient and collaborative. Option C: While decomposing the feature into manageable user stories is important, doing so without first ensuring clarity on the functionality would not address the customer's difficulty in explaining the feature.

Requirements Are Decomposed “Just in Time” As we’ve discussed, the project requirements are broken down “justintime” or at the “lastresponsible moment” as the team gets closer to doingthe work. As shownbelow, the highest-levelrequirements (such as epics) are progressively refinedinto features, stories, and then the most detailedpieces of work—such as tasks, business rules, acceptance tests, and so on D

A = there's no need for spike. B = there's no "iteration 0" C = that would help the estimation and planning process (it comes right after the functionalities are explained by PO and understood by the team) D = correct. The functionalities have to be "just-in-time" explained and explored by the customer & the team