In Agile Software development, the execution level requirement or functionality is terms as user story. A user story can be of one or more sentences. The requirement (details contents) in the user story needs to be sufficient enough so that
- A developer can start and finish his development
- A tester and test the developed code to check if it is meeting the required functionality
- Product owner/ BA / Stake holder can verify the desired functionality to accept the story completion.
Each story has be to fulfill a requirement with a very specific goal or benefit, it’s always advisable to break any store to smaller stories, if it has more than one goal.
Requirement of a story has to be of a complete functionality, means upon completion of development, testing and acceptance, the code should be deploy-able, or park for future release. In other word the each user story should be potentially ship-able.
Size of a user story is measured in story points (Refer our section Estimation Techniques), to provide a business value or complexity.