Is functional point analysis used for evaluations?

Question

In one of the discussions among colleagues, I heard that the analysis of functional points is not used today, because it can go wrong, for various reasons.

Therefore, WBS (breakdown structure) is commonly used.

It's true?

Answer 1

Function points and WBS are two different but related elements. Functional points are a unit of measurement that can be used to determine complexity and labor effort, WBS (work breakdown structure) is an approach for determining project sub-blocks (problems). So, when you start a project with a given area and a lot of expectations, you use WBS to determine project sub-blocks (to the extent that is useful to you), as soon as you have clearly defined units, you can determine the effort by assigning functional points to everyone and multiplying the speed (the number of function points per day that can be delivered, as an example).

Here are some useful links:

• Function Points via Wikipedia
• Software size during requirements analysis
• WBS via Wikipedia
• step by step wbs

Answer 2

I just took the introductory course of the project management program, and we did not even look at the “functional point analysis” (I'm not sure what it is), but we spent a lot of time on WBS. All of the following processes are NGN.

Answer 3

I can only talk about what I saw. I saw how IBM uses feature points in Mexico to determine product size and pay subcontractors.

Yours faithfully...

Answer 4

In the early nineties, I again began to analyze functional points, but it never appeared again as soon as I actually entered the workforce.

Answer 5

Function points are out of fashion, but they work very well. I urge you to look further at the work of Caper Jones, who has published several amazing books that help measure and confidence in software projects.

Answer 6

FPA is not a measure of effort. FPA is used to determine the "functional size" of software requirements expressed in "functional points" (fp), so it can be one of many input variables for a more complex effort estimation model (such as COCOMO).

Do not allow "ratings" for "planning." WBS is a planning technique that requires detailed knowledge of what and how to create / develop. On the contrary, an estimate is a forecast of expected effort / cost based on limited evidence.

So it's not about “one-or-the-other”, but “when-what”.