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

To the best of my understanding the schedule for the project is derived using the effort estimates for the individual tasks (in person hours), and the number of relevant resources used for the particular task.

As discussed in this question, we are starting a project using a new platform, featuring a brand new API and feature-set. How do we estimate the schedule of the tasks involved in the project, knowing only the top level task breakdown? Also, if some efforts are allocated to the tasks, the estimations would have a wide probability distribution. What is the best way to communicate the same to management?

share|improve this question
up vote 6 down vote accepted

I usually give an R&D (Research and Development) estimate for unfamiliar territory. In this, I promise an actual estimate upon the elapsing of the R&D time limit. I spend the R&D time creating prototypes and proof of concepts, and then finally my overall architecture. By that time, you should be familiar enough to make a good estimate. Giving an estimate without communicating that you will have to spend time in R&D is asking for upset employers. They may not like this response, but I promise you they will hate the alternative-- i.e. you make a timeline that you have no idea that you can meet and you inevitably fail to meet it.

share|improve this answer

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.