Definition of User Story
The specifications are often a big cause of failure in projects. Bad specifications could lead to misunderstandings about the final product, wrong functionalities, and not required features.
The objective of “User stories” is to respond quickly and with less cost to modifications of requirements (new user needs for example).
With agile methodologies, the US is written to share the vision of developers/testers/project leaders instead of continually reviewing during the redaction phases.
We find this sharing also in the V cycle through the very formal notion of requirements reviews after this one is drafted (less + but very motionless process – no live modification).
The ” user stories ” describe the features that will be useful. The ” user stories ” consist of three aspects ( principle of 3C) : …