There are standard FP tools available in the market today, but one of the finest ways to work with Project estimation is to build your own tool set that can be customized to your organizational requirements and gives you a great deal of flexibility. I am going to use an excel worksheet to do the FPA analysis as showcased on this website. There have been customization made to the standard FPA principles in order to include workflow management and improve accuracy using progressive estimation techniques which will be discussed shortly.
Let us begin by creating a sheet for including all project related details and a summary of calculations in the FP sheet.
Here we enter the internal project related details; ID, Name, associated Work Order, Language(s) used,Client, Tentative Start date and End date of this project. The second part showcases the project summary, which is taken from the FP calculation sheet. The details shown here are the calculated FPs in the project which comprises of the total FP count, the Reuse FP count, and the Process FP count, and the total man hours for the project. Process FP is used to include workflows which we will describe shortly. As the estimation provided uses multiplicity factor instead of static ranges of high/medium/low, it has a greater deal of accuracy so it is possible to compute both estimated man hours and total cost of the project.
The next section is the Licensing, which is issued to all who support the project, licensing helps to support the project and it is requested that all commercial projects may purchase a copy when possible.
The next sheet is the Project Use Case/User Story/Scenario list which we will refer to for each data and transaction functions by means of a reference ID. There may also be references to Non-Functional tasks which is indicated by Has FP column.
There are four columns which consists of Reference ID, Description, UFP and Reuse FP. All the individual use cases or user stories are listed here. You are required to provide a unique ID and description of the use case. Once you provide all the data and transaction functions in the use case/user story the Unadjusted FP count and Reuse FP count will be visible here to help you understand the workload in each UC/US.