A company wants to develop a product roadmap to guide future development efforts. The product owner asks a business analyst IBA) to lead the analysis effort. Feature suggestions have been compiled…

Comparing implementation costs is a supporting input to the prioritization decision, not a standalone prerequisite step that comes before the backlog is organized.

Determining the value of each feature is an activity that informs prioritization and occurs as part of the prioritization process, not as a separate preceding step.

Prioritizing the features in the backlog is the first step because the product roadmap is itself an artifact that communicates strategic priority and development sequencing, and it cannot be constructed without a prioritized list. Without this initial ordering, activities such as comparing implementation costs or determining individual feature value lack the contextual ranking needed to make meaningful trade-off decisions. In BABOK's Prioritize Requirements task, establishing relative priority is the foundational activity that drives all downstream roadmap planning.

Confirming feature requests is a validation activity that applies to individual items once the backlog has been organized and prioritized, not a first step before the list has structure.