Hello All, especially y''all with a shingle out, I would like to hear your advice, patterns, and approaches to estimating your Rails projects? I need to provide an item-specific hours estimate for 2 upcoming projects. I want to hear about pitfalls, gotchas, who-da-thunks, and also points that say "this really IS a better way". Thanks for your feedback! Peter J. Fitzgibbons Applications Manager Lakewood Homes - "The American Dream Builder"(r) Peter.Fitzgibbons-STCS76aLmhk1y/cD6r8xzl6hYfS7NtTn@public.gmane.org (847) 884-8800 _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
Hi, I''ve always found the only way to estimate the time needed for a project is to do so from experience. Without that, you''re probably going to be off the mark. I''d suggest you estimate it as if you were building it in whatever language/framework you''re already accustomed to (and experienced in) and then if it takes less time in Rails you can either add more features or provide the client with a discount. You can then take what you learn from that and better estimate next time around. Ben On 7/30/05, Peter Fitzgibbons <Peter.Fitzgibbons-p2lxMnUesd41y/cD6r8xzl6hYfS7NtTn@public.gmane.org> wrote:> > > Hello All, especially y''all with a shingle out, > > I would like to hear your advice, patterns, and approaches to estimating > your Rails projects? I need to provide an item-specific hours estimate for > 2 upcoming projects. > > I want to hear about pitfalls, gotchas, who-da-thunks, and also points that > say "this really IS a better way". > > Thanks for your feedback! > > Peter J. Fitzgibbons > Applications Manager > Lakewood Homes - "The American Dream Builder"(r) > Peter.Fitzgibbons-STCS76aLmhk1y/cD6r8xzl6hYfS7NtTn@public.gmane.org > (847) 884-8800 > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails > > >-- Ben Myles RailsAppHosting (www.railsapphosting.com)
I''d suggest this route, but if you haven''t used Ruby, Rails, FCGI, etc, before, add MORE time to your estimate. Ignore the Rails hype -- you''re using tools with which you''re unfamiliar, right? If so, treat your estimate accordingly. Any "extra" time you find can be used to optimize SQL usage for your particular RDBMS, auditing and strengthening security, and doing mini pen-tests on your system. On Jul 30, 2005, at 8:46 AM, Ben Myles wrote:> Hi, > > I''ve always found the only way to estimate the time needed for a > project is to do so from experience. Without that, you''re probably > going to be off the mark. > > I''d suggest you estimate it as if you were building it in whatever > language/framework you''re already accustomed to (and experienced in) > and then if it takes less time in Rails you can either add more > features or provide the client with a discount. You can then take what > you learn from that and better estimate next time around. > > Ben > > On 7/30/05, Peter Fitzgibbons <Peter.Fitzgibbons-p2lxMnUesd41y/cD6r8xzl6hYfS7NtTn@public.gmane.org> > wrote: > >> >> >> Hello All, especially y''all with a shingle out, >> >> I would like to hear your advice, patterns, and approaches to >> estimating >> your Rails projects? I need to provide an item-specific hours >> estimate for >> 2 upcoming projects. >> >> I want to hear about pitfalls, gotchas, who-da-thunks, and also >> points that >> say "this really IS a better way". >> >> Thanks for your feedback! >> >> Peter J. Fitzgibbons >> Applications Manager >> Lakewood Homes - "The American Dream Builder"(r) >> Peter.Fitzgibbons-STCS76aLmhk1y/cD6r8xzl6hYfS7NtTn@public.gmane.org >> (847) 884-8800 >> >> _______________________________________________ >> Rails mailing list >> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org >> http://lists.rubyonrails.org/mailman/listinfo/rails >> >> >> >> > > > -- > > Ben Myles > RailsAppHosting > (www.railsapphosting.com) > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
I''d suggest to fix price not time. Everything else is too hard unless you have a lot of experience with the tools. On 7/30/05, Peter Fitzgibbons <Peter.Fitzgibbons-p2lxMnUesd41y/cD6r8xzl6hYfS7NtTn@public.gmane.org> wrote:> > > Hello All, especially y''all with a shingle out, > > I would like to hear your advice, patterns, and approaches to estimating > your Rails projects? I need to provide an item-specific hours estimate for > 2 upcoming projects. > > I want to hear about pitfalls, gotchas, who-da-thunks, and also points that > say "this really IS a better way". > > Thanks for your feedback! > > Peter J. Fitzgibbons > Applications Manager > Lakewood Homes - "The American Dream Builder"(r) > Peter.Fitzgibbons-STCS76aLmhk1y/cD6r8xzl6hYfS7NtTn@public.gmane.org > (847) 884-8800 > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails > > >-- Tobi http://www.snowdevil.ca - Snowboards that don''t suck http://typo.leetsoft.com - Open source weblog engine http://blog.leetsoft.com - Technical weblog