CAPM Practice: Demonstrate an understanding of product roadmaps

A now-next-later roadmap emphasizes priority sequence without hard date commitments — reducing pressure to hit arbitrary dates at the expense of quality. Date-based roadmaps provide timeline certainty but risk 'roadmap theater' where teams cut corners to hit dates.

**Why not A:** The distinction between now-next-later and date-based roadmaps is not about which audience they serve. Both formats can be used with teams and management alike. The real difference lies in how they express timing — relative priority horizons versus specific calendar dates.

**Why not B:** These are not the same type of roadmap. A now-next-later roadmap organizes work into time horizons based on certainty and priority, while a date-based roadmap commits to specific delivery dates. They represent fundamentally different planning philosophies, especially regarding predictability and flexibility.

**Why not C:** The distinction has nothing to do with the type of product being developed. Both software and hardware products can use either roadmap format. The choice depends on the organization's planning approach and tolerance for date commitments, not the nature of the deliverable.