The first STEP is to clearly identify what are the goals of the organization. Function Point Analysis can be used for several purposes: estimation of software projects, unit of contracts measurement, support for quality and productivity control, benchmarking and metrics program.

Each approach has its specific peculiarities; however there are aspects common to all them, highlighted below:

1. Gain the support of the organization’s direction. Keep in MIND that the results of the use of Function Point Analysis in the organization are not always immediate and that the success of its use will depend on the dedication and use of human and financial resources, as well as any program that focuses on processes improvement.
2. Take advantage of existing opportunities in the organization that may have some common goals. Examples of these initiatives are: ISO, Six Sigma, CMM, PMI, Balanced Scorecard. Taking these initiatives and knowing how to relate (and show to sponsors) Function Point Analysis may contribute to some of the organization´s goals, and will make it easier to accept.
3. EMPOWER yourself. Knowing the correct technique is essential. It’s amazing the number of cases that Function Point Analysis has being applied incorrectly, and that, invariably ends in failure. The official reference of the technique is the IFPUG — CPM (Counting Practices Manual). Interesting actions in this regard can be:
   
   Hire a closed class for the whole team involved, so you can adjust the load or summary of the course with the objectives of the process and the reality of the organization. In this case, FATTO USUALLY holds a service package with one week duration: two days to teach the course Training Function Point Analysis; and three days for consulting the beginning of the process and mentoring on the application of the technique in organization’s practical cases.
   
   Sign up key people that are involved in the process in open Function Point classes. FATTO regularly teaches open courses in several cities in Brazil. See our course schedule for more information.
   
   
4. Set modest initial goals. Start with a pilot project in a simple system. Evaluate the results, make adjustments, review the objectives and move on.
5. Be aware of technique limitations. There are domains where Function Point Analysis is is restricted. For example, in systems optimization, the technique is not suitable for measuring parts with high algorithmic complexity.
6. In doubt, make an analogy with the square meter. In general, it is sufficient to solve the issue.
7. Seek help if necessary. An outside consultant can avoid unnecessary troubles, hasting the process, bringing experience and helping to correct the directions.
8. Do not compare apples with oranges. Comparisons should only be made between projects that have similarities (development process, technology platform, business AREA, etc).

The first step is to clearly identify what are the goals of the organization. Function Point Analysis can be used for several purposes: estimation of software projects, unit of contracts measurement, support for quality and productivity control, benchmarking and metrics program.

Each approach has its specific peculiarities; however there are aspects common to all them, highlighted below: