Forum: Ruby on Rails RE: OT -- billing and estimating, good resources?

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Chris B. (Guest)
on 2006-04-27 21:54
(Received via mailing list)
Giles,

I would try and avoid this if possible.  The main reason is that in
order to estimate the milestone, you need to specify it.  Which means
that the client and you need to fully document what is going to be
delivered.  Many times, as you develop, the client and you will need
further clarification on the application which will almost always change
the initial specification.  My experience has been that this translates
to more work than you initially estimated.

I would recommend that you estimate the total number of hours and let
your client know that it is just an estimate.  Depending on the client's
changes, that could go up or down. Also, try to work in short iterations
instead of long milestones. This "agile process" is best because you
don't need to specify the application up front.  You specify small bits
of functionality in very small iterations (like week or less) and that
way the application can evolve as more is understood.



Chris
This topic is locked and can not be replied to.