PMP Practice: Deduce project resource requirements

In an agile environment where requirements are expected to evolve significantly, the most effective approach is to identify core skill sets needed based on the general nature of the work, then build a small cross-functional team capable of adapting as the project progresses. Agile teams are designed to be flexible and self-organizing, with members who possess T-shaped skills that allow them to contribute across disciplines. Starting with core skills and a small team enables rapid iteration and learning, which is essential when customer feedback will drive requirement evolution. This approach balances the organization's need for some resource planning while maintaining agile principles of adaptability and emergent design. The closing fact that requirements will evolve significantly makes rigid upfront planning inappropriate.

**Why not A:** Creating a comprehensive WBS based on initial user stories assumes requirements are stable enough for detailed decomposition. The product owner has acknowledged that stories will evolve significantly, making a detailed WBS premature and likely to require substantial rework as requirements change.

**Why not B:** Waiting for the product owner to finalize all user stories before recruiting contradicts agile principles. In an agile project where requirements are expected to evolve based on customer feedback, waiting for complete requirements would delay the project indefinitely and ignore the emergent nature of the work.

**Why not D:** Waiting until the backlog is fully refined before determining resource needs would delay project initiation unnecessarily. In agile, the backlog is never truly "fully refined" since it continuously evolves. The team should start with core capabilities and adapt as requirements emerge.