In FPA estimation technique, how to estimate daemon process / invisible / internal process?
You may come across requirements like workflow management, generate complex primary key / Id, batch processes etc. How to estimate these functions in FPA estimation technique?
Answers (2)
Naren P.
Business Intelligence, Business Analytics. CBIP, PMP.
Best Answers in: Planning (1), Career Management (1), Enterprise Software (1), Software Development (1)
You can not estimate it unless you are able to qualify/quantify what's the benefit to user and which functions does this daemon process deliver/address. In fact you should not include such invisible process(es) as part of your FP estimates- FP estimation should be driven from user standpoint and not from Development team's standpoint. What if another developer proposes alternate way to daemon process? Your FP estimates should be insensitive to technical solution. If you are estimating for a daemon process, I guess you are at design stage; in such case I recommend you not to use FP estimates. You can do better estimates as you know design and technology(I am assuming you know technology platform in this case).
All the best
As Naren says, if the daemon process involves value added functionality from the user’s point of view, you can count it using FPA. If the added value in not “visible”, the effort to develop these processes could be already considered on the “platform factor”.
Regards
