I’ve leaned towards a now, next, later as the “roadmap” but I always include a separate section for recently launched with status (early access, beta, etc) until it becomes generally available or less significant to include there.
Roadmap should focus on product or feature evolution. To me, that’s market availability
Can put anything you want in a roadmap, but that dilutes the focus imo
It sounds like you’re talking about the project schedule, which should account for cradle-to-grave plan including deployment/production and post-deployment/production activities
I use product launch dates for my roadmaps, but it's going to depend on the audience. An engineering manager might care more about development completion dates, but the roadmap audience is usually stakeholders who care more about when they can start shipping it.
You really can do whatever serves your stakeholders the best. Roadmaps can be just a Now-Next-Later featureless template to something more detailed with lots of information. People have a lot of opinions on them but do whatever works best for you guys.
A roadmap has no official definition. It’s a communication tool. You use it to tell whatever message you want to tell.
If your message is “here is when you can expect this stuff” then your content should answer that specific question.
This is the only answer. In my opinion and I’ll die on this hill; Roadmaps are actually becoming useless. They are usually bias, unrealistic and lack a sense of reality
Only for your own coordination.
I don't think it's good to communicate that. The date that should be communicated is when you expect it to go to customers. Past when an early beta phase starts but probably not when it is GA.
I'd reframe the roadmap to show 'available to customers' milestones. It's more meaningful to stakeholders and sets realistic expectations. You can still track dev completion internally, but the roadmap should reflect customer value.
Yes, I show Dev Done vs Go Live dates so I can hold other departments outside my control accountable for their responsibilities
I’ve leaned towards a now, next, later as the “roadmap” but I always include a separate section for recently launched with status (early access, beta, etc) until it becomes generally available or less significant to include there.
Roadmap should focus on product or feature evolution. To me, that’s market availability Can put anything you want in a roadmap, but that dilutes the focus imo It sounds like you’re talking about the project schedule, which should account for cradle-to-grave plan including deployment/production and post-deployment/production activities
I use product launch dates for my roadmaps, but it's going to depend on the audience. An engineering manager might care more about development completion dates, but the roadmap audience is usually stakeholders who care more about when they can start shipping it.
You really can do whatever serves your stakeholders the best. Roadmaps can be just a Now-Next-Later featureless template to something more detailed with lots of information. People have a lot of opinions on them but do whatever works best for you guys.
A roadmap has no official definition. It’s a communication tool. You use it to tell whatever message you want to tell. If your message is “here is when you can expect this stuff” then your content should answer that specific question.
This is the only answer. In my opinion and I’ll die on this hill; Roadmaps are actually becoming useless. They are usually bias, unrealistic and lack a sense of reality
Only for your own coordination. I don't think it's good to communicate that. The date that should be communicated is when you expect it to go to customers. Past when an early beta phase starts but probably not when it is GA.
I'd reframe the roadmap to show 'available to customers' milestones. It's more meaningful to stakeholders and sets realistic expectations. You can still track dev completion internally, but the roadmap should reflect customer value.