Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I need to prepare an internal product release road-map for product being built via scrum methodology, and have some difficulty correlating sprints to the road-map.

The main problem is that as I don't have effort estimations for every story, because these prepared immediately before each sprint, so I don't know what will make into which sprint.

I'm fine with changing the road-map as the development goes on, but need it to give at least some indication when things planned to be released.

So what would be the best way to do this, other then guestimating the whole backlog?

Thanks for any idea.

share|improve this question
Can you consult with the head of the team that is going to work on the product? If so, the head can make good estimations for you. – superM Jul 5 '12 at 18:01
I can do so, though the below suggestion of having all team estimating the items looks more realistic. – SyBer Jul 8 '12 at 6:43
I thought you had no chance of such a meeting because you said you were going to estimate all yourself ))) – superM Jul 8 '12 at 7:02
I might have not been very clear - I'm responsible to provide this, but thanks heavens I can involve developers into this estimation. Doing it alone would be a suicide indeed :). – SyBer Jul 8 '12 at 11:10
up vote 3 down vote accepted

Last time I did something like this we got the whole team together and estimated the entire backlog. It's darned annoying, but I couldn't see any way around it.

It's all guesswork at that point, of course, because you don't even really know what you'll be doing by the end because you can guarantee that something is going to change. But it's the only way I know how to take a defensible guess at the end date.

If you can, implement the roadmap in your tracking system rather than as a list of dates on paper. That way you are emphasizing the ephemeral nature of the dates, to hopefully give your audience a better feel that these aren't 'written in stone' in any way.

share|improve this answer
Thanks, this what I was afraid of, but unfortunately it indeed seems the only way to go. – SyBer Jul 8 '12 at 11:09

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.