Project estimation metrics?

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Ray Stevens

    #1

    Project estimation metrics?

    I've been asked to come up with a formula for estimating C# projects. Does
    anyone know of a good source for this? (website, book, etc.)


  • Peter Rilling

    #2
    Re: Project estimation metrics?

    Although I know of no such resources, I can tell you that there is no single
    formula for estimating time. From my experience, it takes experience to now
    what a project entails.

    I have seen attempts at estimation for project that rely on the number of
    forms or the number of tables in the database. I have found these not to be
    very accurate because there are many factors that must be taken into
    account.

    1) How experienced the devs are that are working on the project and are
    there any new technologies that must be learned.
    2) Will there be an architecture or just use the quick-and-dirty features
    of VS.NET.
    3) Will it be ASP.NET, console, webservice, etc.
    4) The complexity of the database.
    5) The complexity of the forms or pages.
    6) (and many others that I cannot think of off the top of my head)

    Maybe you can clarify your phrase "formal for estimating".

    "Ray Stevens" <nfr@nospam.com > wrote in message
    news:OayF5S1KGH A.1312@TK2MSFTN GP09.phx.gbl...[color=blue]
    > I've been asked to come up with a formula for estimating C# projects. Does
    > anyone know of a good source for this? (website, book, etc.)
    >[/color]


    Comment

    • Michael Nemtsev

      #3
      Re: Project estimation metrics?

      Hello Ray,

      I recommend to read about COCOMO and PSP/TST
      These methods based on "proxy bases estimates"
      Small description:
      - use UseCase to assess amount of work for each module in lines of code
      (LOC) and general solution (proxy)
      - for each module forecast the deadline bases on PERT Estimation (read
      - get PERT productivity factor LOC/hr

      It's just a glance on estimating project. Being a certificated PSP engineer
      I recommend to read about PSP. I found it strongly usefull for those who
      are concerned about his own productivity and quality of code. For me it gave
      an outstanding result

      RS> I've been asked to come up with a formula for estimating C#
      RS> projects. Does anyone know of a good source for this? (website,
      RS> book, etc.)
      RS>
      ---
      WBR,
      Michael Nemtsev :: blog: http://spaces.msn.com/laflour

      "At times one remains faithful to a cause only because its opponents do not
      cease to be insipid." (c) Friedrich Nietzsche


      Comment

      • Ray Stevens

        #4
        Re: Project estimation metrics?

        This looks encouraging. Did you mean PSP/TSP?

        "Michael Nemtsev" <nemtsev@msn.co m> wrote in message
        news:9cc1c86378 8888c7f98d86317 65c@msnews.micr osoft.com...[color=blue]
        > Hello Ray,
        >
        > I recommend to read about COCOMO and PSP/TST
        > These methods based on "proxy bases estimates"
        > Small description:
        > - use UseCase to assess amount of work for each module in lines of code
        > (LOC) and general solution (proxy)
        > - for each module forecast the deadline bases on PERT Estimation (read -
        > get PERT productivity factor LOC/hr
        >
        > It's just a glance on estimating project. Being a certificated PSP
        > engineer I recommend to read about PSP. I found it strongly usefull for
        > those who are concerned about his own productivity and quality of code.
        > For me it gave an outstanding result
        >
        > RS> I've been asked to come up with a formula for estimating C#
        > RS> projects. Does anyone know of a good source for this? (website,
        > RS> book, etc.)
        > RS> ---
        > WBR,
        > Michael Nemtsev :: blog: http://spaces.msn.com/laflour
        >
        > "At times one remains faithful to a cause only because its opponents do
        > not cease to be insipid." (c) Friedrich Nietzsche
        >
        >[/color]


        Comment

        • Michael Nemtsev

          #5
          Re: Project estimation metrics?

          Hello Ray,

          Sure

          RS> This looks encouraging. Did you mean PSP/TSP?
          RS>[color=blue][color=green]
          >> Hello Ray,
          >>
          >> I recommend to read about COCOMO and PSP/TST
          >> These methods based on "proxy bases estimates"
          >> Small description:
          >> - use UseCase to assess amount of work for each module in lines of
          >> code
          >> (LOC) and general solution (proxy)
          >> - for each module forecast the deadline bases on PERT Estimation
          >> (read -
          >> get PERT productivity factor LOC/hr
          >> It's just a glance on estimating project. Being a certificated PSP
          >> engineer I recommend to read about PSP. I found it strongly usefull
          >> for those who are concerned about his own productivity and quality of
          >> code. For me it gave an outstanding result
          >>
          >> RS> I've been asked to come up with a formula for estimating C#
          >> RS> projects. Does anyone know of a good source for this? (website,
          >> RS> book, etc.)[/color][/color]

          ---
          WBR,
          Michael Nemtsev :: blog: http://spaces.msn.com/laflour

          "At times one remains faithful to a cause only because its opponents do not
          cease to be insipid." (c) Friedrich Nietzsche


          Comment

          • Randy A. Ynchausti

            #6
            Re: Project estimation metrics?

            Ray,
            [color=blue]
            > I've been asked to come up with a formula for estimating C# projects. Does
            > anyone know of a good source for this? (website, book, etc.)[/color]

            The Personal Software Process (PSP) by Watt S. Humphrey is the current best
            of bread technology for your problem.

            Regards,

            Randy


            Comment

            Working...