Comment Re:Experience, solid requirements (Score 1) 227
I love this post, it actually reflects the problem from a project management perspective.
If you do not have detailed requirements, estimating becomes an estimate-of-an-estimate!
If you cannot break down the task, you really don't know what you're doing - irrespective of level of personal experience.
If you are going to use a RAD methodology that speaks to rapid prototyping, you still need detailed requirements to get something started.
THE REAL problem a wise customer should recognize, and a deliberate methodology will likely raise, is WHAT'S the REAL TIME to GATHER REQUIREMENTS going to be? Development time becomes a more precise estimate based upon requirements definition time.
If you do not have detailed requirements, estimating becomes an estimate-of-an-estimate!
If you cannot break down the task, you really don't know what you're doing - irrespective of level of personal experience.
If you are going to use a RAD methodology that speaks to rapid prototyping, you still need detailed requirements to get something started.
THE REAL problem a wise customer should recognize, and a deliberate methodology will likely raise, is WHAT'S the REAL TIME to GATHER REQUIREMENTS going to be? Development time becomes a more precise estimate based upon requirements definition time.
