Skip to main content

Roadmap and milestones

Last post 02:38 pm August 15, 2019 by Tony Divel
3 replies
02:05 am August 15, 2019

In simplest terms, can someone please explain to me what are milestones and roadmaps and what are how are roadmaps created?


02:38 am August 15, 2019

My advice is to avoid such terms of reference if they complicate things. It might be better to consider the Product Backlog as a planning tool for value delivery. The backlog can be organized so plans are captured at various useful levels of granularity.


09:50 am August 15, 2019

A milestone is a marker of a stage in a project. They are often aligned with demonstrating or releasing a particular unit of functionality on the path for the known entire set of desired functionality. A roadmap is a plan - it often relates milestones and dependencies between them and gives stakeholders some insight into when work will be available or delivered. Both are typically used in more plan driven methodologies as they give a sense of control and planning over a project.

I'd tend to agree with Ian Mitchell. In the context of Scrum, the ordered Product Backlog can give the same insights as a roadmap, but much more aligned with the reality of complex projects. Items at the top of the Product Backlog are more well defined and will be delivered earlier. If they are sufficiently refined and there's some historical data on the team's performance, you can give very rough forecasts of when the work may be done by the team. You could consider each Sprint and it's potentially releasable Increment to be a milestone that can be used to elicit feedback and reorder the Product Backlog, with Product Backlog Refinement being used to add clarity to the near future of work.


02:23 pm August 15, 2019

I'd recommend checking out Roman Pichler's blog related to Product Management. There's some great content on Goal Oriented Product Roadmaps that help inform the order of the Product Backlog and illustrate the product and business goals on the horizon. 

Something like this tells you where you're going in terms of outcomes and high level features without getting into a ton of granularity. You can leave that for the top items of your Product Backlog.  

I find these types of roadmaps lend themselves well to the Scrum framework and helps the team gain alignment towards the bigger picture. 


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.