User Requirement is a set of scenario that is a considered as building block for product development. Development in general based on requirement. Most requirement are presented in a different format to let development team understand about the feature to be developed and delivered.
The user requirements are first formed in the form of Feature. Feature is nothing a particular part of a product and mainly represent has big scope of a product feature. The Feature further decomposed into several types of elements
- PBI – Product Backlogged Item / Story
- TUS– Technical User Story
PBI – Product Backlogged Item
Product Backlogged Item – considered as one peaces of a Feature which has a target scope. Therefore the PBI derived from the Feature, and has a list of Scenario functional as well as technical requirements. This work item is considered to be as development brick since it is adding some functionality to the product that is under developmetn.
Product Development team start working on the PBI after Grooming the user requirement to be developed. In the Sprint Grooming, the following main activities will be conducted. Each development team members play a great role about each functionality which is going to be added. Therefofe the following are the responsibility of the team members
- PS – Product Specialist – Present the PBI and explain the user requirement
- UI/UX – Already present the prepared requirement and user journey in the for.m of Mockup.
- Developers – address different point considering what it is available now ignorer to determine how to approach the current requirement and develop as well. This could help them to address all the technical requirement and estimate the effort (how many days or hours) needs.
- Testers – Engaged themselves to understand better about the new business requirement and ask for any clarity.
Note :-
- Any Member of the development team should raise or propose any improvement or clarity about the business requirement.
- Any Latest discussion and confirmed change should be included as part of the development
TUS – Technical User Story
This is a requirement to be developed or address before the user requirements. Most of the case the TUS are considered as backbone of the user requirement. Because the user requirement is development considering that all the Technical aspected is already in placed. Therefore TUS will be groomed in the same manner as PBI but mostly among developers only.
Some of the activities that Developers are doing in the TUS
- Perform Analysis first what the current implementation and behavior of the module that they are trying to add the new bsuiness requirement
- Present the result of the analysis to the team to share the knowledge and get feedback
- After a team discuss and confirmation, it will have a defined scope that could make the TUS to be estimated and prioritize.