The implementation part is pretty straightforward and its complexity depends on the actual tickets. As a summary the following is required for each 'New Feature', 'Improvement' and 'Bug' ticket:
- Create a new branch from 'master' using the ICT JIRA interaction with BitBucket
- Move the workflow from 'Accepted' to 'In Progress'
- Do the actual implementation
- Coding, manual developer tests
- Automatic Phase A tests
- Commits should try to include the ticket number for IRM integration purposes later on
- Move the status to 'Implemented'
- Create Pull Requests back to master
- Assign ticket to irm ('Integration and Release Management') user
This is not a rigid rule as there may be exceptions, for instance in the case of tickets highly dependent of each other where one branch may be used for both of them.
Other kind of tickets may be tackled in different ways:
- For instance a 'Task' ticket may or may not require actual commits to Bitbucket server, but they do not have testing associated.
- 'Sub-features' may require to be all part of the main 'Feature' branch, in order for their implementations to be available to each other.
- Etc.
From time to time, but also at the end of the implementation phase, the Integration of all the delivery branches needs to be done.