Release management
Types of tickets
The type of the ticket determines testing and release flow
User story is the only story that goes through the whole flow of development -> testing -> live. With this story the testers can test a functionality end-to-end. Peer review by the developers is a review of the code.
Refinement story - to investigate an issue
Technical story - to develop the back end of a user story
Bug - to resolve an issue detected by testers
Definition of Ready
You can start working on a user story when
the user story is clearly defined - it adds value for the end user and it is discussed in sprint planning meeting so that everybody understands the requirements;
the technical issues are cleared out - if there are technical issues created a linked technical story that has to be resolved first;
the story is estimated - indicate the level of complexity of a story and the percieved risks and uncertainties.
Example of a not complex story - 2 story points: https://binnenland.atlassian.net/browse/CLBV-134
Example of a more complex story - 8 story points: https://binnenland.atlassian.net/browse/CLBV-351
A ticket is finished in 1 sprint. If you estimate that the ticket can't be finished in 1 sprint, it should be split. A sprint should not be overplanned, but also not be underplanned. It should be realistically planned.
Definition of Done
A user story is done when
the required functionality is developed;
the ticket has been reviewed by peers;
the functionality is deployed to DEV and has been tested;
the functionality is deployed to QA and has been tested.
TEST - QA - PROD
There are 3 environments:
TEST - current development state - used by developers and testers. When a user story is developed, it will be released immediately to TEST. The testers will test it and give feedback. If there are bugs the developers will take it up.
QA - current PROD + new functionalities plannend in a release - used by developers testers. When a release is planned in the release board, those stories will be deployed on QA. The testers will test the release and give feedback. If there are bugs the developers will take it up.
PROD - current live functionalities - uses by end users. When is a release is approved on QA, it will be deployed to PROD. User will be informed of the changes.
Last updated
