is a big can of worms! or not!

I thought I might throw out some creative Project Management topics for discussion.

Creative projects cover a huge range of possibilities and technologies nowdays, and estimating is a key part of undertaking any project.

Even exploratory play um, R&D! has to be timeboxed in the busy world we live in.
(which leads into a separate but related topic of constraints being a creative enabler...)

Here's a couple of good articles on estimating (albeit from a sw developer perspective):
http://simpleprogrammer.com/2014/10/27/5-ways-software-developers-can-become-better-estimation/
http://www.toptal.com/agile/software-costs-estimation-in-agile-project-management

Some questions to ponder:

1. How good are you at estimating your specific skill(s) [sw, hw, 2d/3d art, writing, illustration, etc] ?
2. How do you go about estimating different project types, from web apps to 3D/2D to cross-platform whatever?
3. How do you manage estimates vs project reality?
4. What tools do you use?
5. [insert here]

My quick answers:

1. Depends on the project. The more uncertainty/risk the bigger the buffers
2. Break it down as far as possible, articulate the risks, ballpark them in task terms based on experience/skills available
3. Related to #4
4. I've used lots but I'm liking the combo of Trello + Plus for Trello atm atm. Lightweight, agile, + visual.

I forgot to explicitly mention in my #3 short answer above-> Communication! The single biggest point of project failure.

Interesting topic and a tough one!

Sometimes feels crazy to spend so much time and effort for the estimate of a "potential" project. Though that's the game, if one doesn't play one can't win. Generally the larger the project the more detailed the scope and estimate.

Generally same as you though: "The more uncertainty/risk the bigger the buffers ".

I'm always wondering if there isn't a way to convert a rough dev estimate (which involves a lot of back and forth with an external developer, sometimes paid) into some kind of client-billed "exploratory phase" or simply "requirement gathering"? Seems like a hard sell. Estimating design feels easier, more manageable.

"I'm always wondering if there isn't a way to convert a rough dev estimate (which involves a lot of back and forth with an external developer, sometimes paid) into some kind of client-billed "exploratory phase" or simply "requirement gathering"? Seems like a hard sell. Estimating design feels easier, more manageable."

That's how Ziptask works (I'm a PM/Developer there). PM gets paid on an hourly retainer for that.