Software Project Estimation: Part 1

Sign in to leave a comment.

• FM

  Former member14y agoPosted Jan 4, 2012, 1:17 PM

  Hello dear My name is madina.i am interested in having a relationship with you and being your friend.i'm romantic and young Girl,you can send an email to my email address ([email protected]) so that I can send you more details about my self Including my picture.
• A

  ahmed15y agoPosted May 13, 2011, 12:28 AM

  Schedule in calendar months = 3.0 * (man-months) 1/3 The parameter 3.0 is variable, used depending on the situation which works best for the organisation. ????
  • 

    Nipun Tomar15y agoeditedPosted May 13, 2011, 3:10 AMEdited May 13, 2011, 3:12 AM

    A rule of thumb is that you can compute the schedule from the size estimate by: schedule in months = 3.0 * (man-months)1/3 where Man Months is defined as Man Months = (Project Work Effort (Hours)) / (Hours per Month) If you’ve estimated that it will take 65 man-months to build the project, then the optimal schedule is 12 months (3.0 * 65^1/3). That in turn implies an optimal team size of 65 man-months divided by the 12-month schedules—5 or 6 team members. This equation is the reason that the estimation ranges are broader for efforts than they are for schedules. Bigger projects take longer, but they also have bigger teams; and the bigger team size means that effort increases disproportionately faster than schedule. The schedule ranges assume that you will add or remove team members as you learn more about the scope of the project. If you hold the team size constant, the schedule ranges will be just as large as the effort ranges. Optimum Staffing Size is given by the following formula. The origin of this formula is currently unknown, but it goes like this: Optimum Staffing Size = Square Root of Man Months