User Story Overview
A User Story is the smallest unit of work in an Agile framework. It’s an informal, general explanation of a software feature written from the perspective of the end-user or customer. Hence, a User Story can be called an end goal and not a feature.
In Copado, a User Story is also used as a container object to develop, commit, promote, and deploy development work (Meta Data, Apex code, etc). It also helps to link and track additional functionalities like Use Cases, Test Runs, and Quality Gates to it.
Features of a Good User Story
A good User Story is governed by INVEST:
- Independent: User stories should be self-contained, independent of other user stories.
- Negotiable: You should be able to make changes to a user story and rewrite it until it is implemented in a time box.
- Valuable: Each user story should deliver a business value to the user.
- Estimable: You should be able to estimate and determine the size/effort of a user story.
- Small: User stories should be small enough to fit in a time box.
- Testable: User stories need to provide information that is necessary for testing, i.e. to make the development of tests possible.