home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!know!mips2!news.bbn.com!noc.near.net!nic.umass.edu!news.mtholyoke.edu!news.byu.edu!eff!sol.ctr.columbia.edu!zaphod.mps.ohio-state.edu!news.acns.nwu.edu!nucsrl!travis
- From: travis@eecs.nwu.edu (Travis Marlatte)
- Newsgroups: comp.software-eng
- Subject: Re: How big is a manmonth
- Message-ID: <1992Nov12.231628.9650@eecs.nwu.edu>
- Date: 12 Nov 92 23:16:28 GMT
- References: <1992Nov11.094243.1171@philips.oz.au> <MARTINC.92Nov11202434@hatteras.cs.unc.edu>
- Organization: Rauland-Borg Corporation, Skokie IL
- Lines: 25
-
- Man-months vary from company to company and from person to person.
- We do initial estimates based on a pure man-month concept and then
- load it with various factors such as planned and unplanned vacations and
- time off, holidays, efficiency, etc.
-
- To assume that an engineer is going to work a full day at 100%
- efficiency is crazy. We expect engineers to statistically spend some portion
- of every day staying current in their field, going to conferences,
- and productively chatting around the coffee pot. By the way, chatting
- about that new wall you're putting in the basement is considered
- productive.
-
- Many people claim that software engineers don't estimate well. I think that
- that is a short sighted view. In most cases the estimates are right on
- target but they don't include other aspects of every engineers day.
-
- When considering estimates from our engineers, we have to be careful. Some
- of them includes different factors in their estimates. Especially as
- an engineer becomes more experienced with the results of his own
- estimates, he will start including many of the weightings that we make
- sure are in the final figure.
- --
- Travis Marlatte
- travis@eecs.nwu.edu
- 708-297-0055
-