Liliana
Nice post! Functions point analysis is part of the techniques used in agile project management to measure the size of an application system based on the functional view of the system. Functions point analysis is a measurement technique introduced by IBM in 70’s to estimate the software development effort which is independent of the technology, development methodology, computer language, and the team’s capability to develop the software. The size of an application system is determined by counting the number of inputs, outputs, queries, internal files, and external files in the system and adjusting that total for the functional complexity of the system. Function point analysis focus on measuring software produced in terms of functionality delivered to the end user, rather than in terms of development deliverables, which have no direct bearing on the end user. Function point use five elements to estimates the size of a software project : Internal Logical Files (ILF), External Interface Files (EIF), External Inputs (EI), External Outputs (EO) and external Enquiries (EQ). Function point calculations begin with counting the five elements. Each function point element is assigned a complexity level (Low, Average, High) based on its associated file number. The associated file numbers are described as Data Element Type (DET), File Type Referenced (FTR) and Record Element Types (RET). Calculation: Step 1: To calculate Total Count (TC) Factor i.e. addition of all individual multiplication of respective weight factors and amount of parameter. Step 2: Calculate Function Point (FP) by using given formula. FP = TC *[0.65+0.01*∑ (Xi)] , where Xi = Addition of all given Processing factors. Step 3: Calculate Productivity, documentation, cost per function of the software application (Uzzafer, 2016).
Warm Regards,
Liiana
Reference
Uzzafer, M. (2016). Principle Component Analysis of Function Point Elements. Retrieve from http://article.nadiapub.com/IJAST/vol91/4.pdf
Laury
- Although using story points, function points, or estimated hours are different methods of estimating workloads, their basic utility is the same… optimizing efficiency. Another thing to keep in mind is that the use of one method does not preclude the use of another method (Estimacy, 2019). In other words, you can combine elements of more than one method to estimate the workload of a project.
The Estimancy article makes a few good points to keep in mind (2019):
- Function Points are considered standard units and can be replicated. In your post you noted the formulas used to calculate workload by this method. This us commonly performed by either an automated system or a subject matter expert.
- Story Points. In contrast to Function Points, Story Points are not standard units. When this method is used, team members will estimate their workloads by how they perceive the complexity of the tasks involved. This requires a great deal of collaboration between the team.
- Estimated hours. This method differs from both of the methods mentioned above in that it utilizes the number of hours to estimate the workload. A great point was made in the Merrill article (2021). If the team estimates a specific task will take 100 man-hours to complete, you do not want to schedule it to be completed in a 40 man-hour block.
References
Estimancy. (2019, Dec 9). Story Points vs. Function Points. Retrieved from Estimancy: https://www.estimancy.com/en/2018/09/25/story-points-vs-function-points/
Merrill, C. (2021, Mar 8). How Agile Estimation Techniques Help Workload Management. Retrieved from Zibtek: https://www.zibtek.com/blog/how-agile-estimation-techniques-help-workload-management/
Reply
