| Task |
Description |
| Independent |
The User Story shall be NOT depend on other user Stories be implemented before the actual User Story. |
| Negotiable |
The User Story is open for discussion before and during the Sprint Planning. Only in rare cases will a User Story be negotiated after the definition of ‘Done* has been agreed. |
| Valuable |
The implementation of the User Story shall create some kind of business value for the organisation. Value can be directly in use or because it enables value for other User Stories.
Example: A User Story for creating a database do not give value in itself for the business, but it give value for all other User Stories related to using the data base for storing data or retrieving data to e.g. reports. |
| Estimable |
The User Story shall be sufficient specific and detailed to allow the Scrum Team to estimate the effort required to implement
the User Story.
There shall be no or only little confusion about what is needed to make the implementation ‘Done’. |
| Small |
The User Story shall possible to implement during a Sprint. When the Development Team estimate the effort to implement the User Story the final value shall not exceed what can be accomplished during the Sprint. |
| Testable |
The User Story shall be verifiable (testable). The Development Team and Product Owner (or the representative of the Product Owner) shall be able to agree to objective criteria for when the User Story is ‘Done’.
The criteria can vary from User Story to User Story and be influenced by regulatory requirements. |