User stories are a concise description of the user’s needs for a software product, from the user’s point of view, widely used by agile software development methodologies. User stories are a simplified format for documenting customer requirements without having to create formalized requirement documents and without performing the administrative tasks related to maintaining them. The intention of the user story is to respond quickly to rapidly changing real-world requirements.

In this context, the Function Point Analysis approach can be applied to the Scrum framework, like any other agile methodology, as presented in IFPUG FSSC White Paper “Applying Function Point Analysis to Scrum Agile Software Development Projects”. Many FP analysts face the challenge of applying the FPA Elementary Process Identification Rules to user stories, which is no different than counting more detailed functional user requirements (FUR) in more comprehensive, traditional requirements documentation developed for software development methodologies such as waterfall. In either case, the level of decomposition of FUR may be too high, as in the case of Epics and Features not decomposed into user stories, to enable the correct identification of EPs. Epics and Features require a greater level of detail for the user’s functional requirements. In some cases, the level of decomposition in the user story may be too granular, resulting in an over counting of EPs. This typically occurs when there are multiple steps or stories required to complete a function. Either case arises because there is insufficient detail to determine the appropriate EPs from the user perspective.

Pre-recorded events are available exclusively to IFPUG members. You must be logged in before having access to view recordings or presentation slides.

Login as a member to access or join as a member here: https://ifpug.memberclicks.net/membership-form