Project Management

Project Management Central

Please login or join to subscribe to this thread

Topics: Scheduling
Does anyone have historical benchmark data that can be used as a starting point for institutions that don't have it?

I'm starting a new role supporting as project/program manager and we don't have historical data to use as a benchmark for analogous estimating. Since the nature of several of our projects is strategic I would like to compile a document with rough duration dates for common project activities that take into account as well the number of stakeholders involved (E.g: As-Is Analysis involving 2 internal stakeholders will take approximately 1 month to complete; As-Is analysis involving 5 external stakeholders will take approximately 3 months to complete) so that the teams could use as initial benchmarks and refine with their experience and future historical data.
Does anyone have an historical dataset that I can use as an initial reference for this?

Thank you
Sort By:
Manuel -

context counts, especially for more complex projects, so it might be better to do a quick high-level decomposition and use an approach such as relative sizing to come up with a high-level estimate rather than looking for other organizations' data.

I would take a slightly different approach from Kiron. IMHO, your question is overly broad. For an analogous estimate to have any potential validity to your project, it must be comparable in both terms of size, and subject matter.

You still need to decompose the problem and define what you need to accomplish, THEN you can compare it to prior work with similar goals. If your end-product is a document, vs. software, vs. brick and mortar, your data points may not be very useful.

One of the key points is who are the stakeholders? If they're all internal, then you get a lot of control over priority. If you are working for an international agency like The Red Cross, then schedules of critical stakeholders and flows may be well outside your control.

This is where I often look to Theory of Constraints. Understanding your biggest constraints first will help limit your solution space. Other constraints will further complicate your solution, but if you want a logical analogy, look to projects with similar constraints.

Please login or join to reply

Content ID:

"The secret of getting ahead is getting started. The secret of getting started is breaking your complex overwhelming tasks into small manageable tasks, and then starting on the first one."

- Mark Twain