DB Up & Down
Each ticket should have a Up & Down script if any database changes are required
New Jira should be empty and use the Scrum template for workflow. Customers to add new tickets and move any ticket still open for work from Redmine.
TODO: Create Jira accounts for everyone (FO + Marketers + EHI people) - Micke
TODO: Talk with Mattias about any Jira costs. - Jonas
TODO: Setup new Jira for WebRes Services - Micke
IMPORTANT! We need to restrict the permissions to create tickets. If everybody can create and edit tickets, Jira will become a mess quite soon.
We need to train our customers in Jira.
We need to decide on the boards columns (the steps for a ticket).
There should be a Master branch, which is always ‘good to go’
Release branch merges into master every 2 to 3 weeks
Make small feature branches if required for large tech tickets. Deleted after depolyment.
No need to tag for each deploy for release, just push to RC. (Tagging available as before for larger tickets if rollback is required)
One release iteration for both Content and Tech.
Working with Requirements
The whole team joins a iteration planning (Sprint planning).
Planning is commitment driven; That is the (working) team decided what will fit in the upcoming iteration (Sprint).
30 Minutes estimation & design meeting every week. If nothing to estimate/break down, no meeting needed.
Always turn back tickets that have questions or are unclear. We only estimate if we are sure what is required.
Once a ticket is estimated any changes to the requirement will undo the estimate and a new estimate will have to be made.
Once a ticket is locked in a iteration (Sprint) no changes to the requirement is allowed.