An agile project manager wants to convert the requirements document into epics, capabilities, features, and stories. Over how many iterations should the project manager estimate story duration?

In agile frameworks, stories are the smallest units of work, typically designed to be completed within a single iteration (or sprint). This practice ensures that work is delivered incrementally, allows for frequent feedback, and enables teams to adapt quickly to changing requirements. Estimating story duration for more than one iteration would contradict the core agile principle of delivering small, manageable chunks of work and would essentially turn a story into a larger feature or epic, which should be broken down further. Therefore, a story's duration should always be estimated for one iteration.