• DB Up & Down

  • Jira

  • Git

  • Release Cycle

  • Working with Requirements

  • Each ticket should have a Up & Down script if any database changes are required

  • Tutorials, Screencasts

  • 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.

  • 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

  • 2 weeks

  • One release iteration for both Content and Tech.

  • 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.

  • up-12345.sql
    down-12345.sql

  • 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.

  • 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)

{"cards":[{"_id":"37f18ee906519b39ee000028","treeId":"37f18c7e06519b39ee000023","seq":1,"position":0.5,"parentId":null,"content":"DB Up & Down"},{"_id":"37f195f85e07d804c600000c","treeId":"37f18c7e06519b39ee000023","seq":1,"position":1,"parentId":"37f18ee906519b39ee000028","content":"Each ticket should have a Up & Down script if any database changes are required"},{"_id":"37f197985e07d804c600000d","treeId":"37f18c7e06519b39ee000023","seq":1,"position":1,"parentId":"37f195f85e07d804c600000c","content":"up-12345.sql\ndown-12345.sql"},{"_id":"37f18da006519b39ee000026","treeId":"37f18c7e06519b39ee000023","seq":1,"position":1.5,"parentId":null,"content":"Jira"},{"_id":"37f1916b06519b39ee00002b","treeId":"37f18c7e06519b39ee000023","seq":1,"position":1,"parentId":"37f18da006519b39ee000026","content":"Tutorials, Screencasts"},{"_id":"37fe52195332bf73e1000012","treeId":"37f18c7e06519b39ee000023","seq":1,"position":3,"parentId":"37f18da006519b39ee000026","content":"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."},{"_id":"37fe54765332bf73e1000013","treeId":"37f18c7e06519b39ee000023","seq":1,"position":0.5,"parentId":"37fe52195332bf73e1000012","content":"TODO: Create Jira accounts for everyone (FO + Marketers + EHI people) - Micke"},{"_id":"37fe56935332bf73e1000014","treeId":"37f18c7e06519b39ee000023","seq":1,"position":0.75,"parentId":"37fe52195332bf73e1000012","content":"TODO: Talk with Mattias about any Jira costs. - Jonas"},{"_id":"37fe4f945332bf73e1000011","treeId":"37f18c7e06519b39ee000023","seq":1,"position":0.875,"parentId":"37fe52195332bf73e1000012","content":"TODO: Setup new Jira for WebRes Services - Micke"},{"_id":"37fefee50d8e02c21900001e","treeId":"37f18c7e06519b39ee000023","seq":1,"position":2,"parentId":"37fe52195332bf73e1000012","content":"IMPORTANT! We need to restrict the permissions to create tickets. If everybody can create and edit tickets, Jira will become a mess quite soon. "},{"_id":"37fe583e5332bf73e1000015","treeId":"37f18c7e06519b39ee000023","seq":1,"position":6,"parentId":"37f18da006519b39ee000026","content":"We need to train our customers in Jira."},{"_id":"37fe59025332bf73e1000016","treeId":"37f18c7e06519b39ee000023","seq":1,"position":7,"parentId":"37f18da006519b39ee000026","content":"We need to decide on the boards columns (the steps for a ticket). "},{"_id":"37f18e7006519b39ee000027","treeId":"37f18c7e06519b39ee000023","seq":1,"position":2,"parentId":null,"content":"Git"},{"_id":"37f198a75e07d804c600000e","treeId":"37f18c7e06519b39ee000023","seq":1,"position":1,"parentId":"37f18e7006519b39ee000027","content":"There should be a Master branch, which is always 'good to go'"},{"_id":"37f19a385e07d804c600000f","treeId":"37f18c7e06519b39ee000023","seq":1,"position":2,"parentId":"37f18e7006519b39ee000027","content":"Release branch merges into master every 2 to 3 weeks"},{"_id":"37f19b675e07d804c6000010","treeId":"37f18c7e06519b39ee000023","seq":1,"position":1,"parentId":"37f19a385e07d804c600000f","content":"Make small feature branches if required for large tech tickets. Deleted after depolyment."},{"_id":"37f19cf75e07d804c6000011","treeId":"37f18c7e06519b39ee000023","seq":1,"position":2,"parentId":"37f19a385e07d804c600000f","content":"No need to tag for each deploy for release, just push to RC. (Tagging available as before for larger tickets if rollback is required)"},{"_id":"37f190b806519b39ee000029","treeId":"37f18c7e06519b39ee000023","seq":1,"position":3,"parentId":null,"content":"Release Cycle"},{"_id":"37f190f806519b39ee00002a","treeId":"37f18c7e06519b39ee000023","seq":1,"position":1,"parentId":"37f190b806519b39ee000029","content":"2 weeks"},{"_id":"37fe61ab5332bf73e1000019","treeId":"37f18c7e06519b39ee000023","seq":1,"position":2,"parentId":"37f190b806519b39ee000029","content":"One release iteration for both Content and Tech. "},{"_id":"37fe64c95332bf73e100001a","treeId":"37f18c7e06519b39ee000023","seq":1,"position":4,"parentId":null,"content":"Working with Requirements"},{"_id":"37fe66505332bf73e100001d","treeId":"37f18c7e06519b39ee000023","seq":1,"position":1,"parentId":"37fe64c95332bf73e100001a","content":"The whole team joins a iteration planning (Sprint planning)."},{"_id":"37fe75235332bf73e1000022","treeId":"37f18c7e06519b39ee000023","seq":1,"position":1.5,"parentId":"37fe64c95332bf73e100001a","content":"Planning is commitment driven; That is the (working) team decided what will fit in the upcoming iteration (Sprint)."},{"_id":"37fe68665332bf73e100001e","treeId":"37f18c7e06519b39ee000023","seq":1,"position":2,"parentId":"37fe64c95332bf73e100001a","content":"30 Minutes estimation & design meeting every week. If nothing to estimate/break down, no meeting needed.\n"},{"_id":"37fe6a205332bf73e100001f","treeId":"37f18c7e06519b39ee000023","seq":1,"position":3,"parentId":"37fe64c95332bf73e100001a","content":"Always turn back tickets that have questions or are unclear. We only estimate if we are sure what is required."},{"_id":"37fe6bda5332bf73e1000020","treeId":"37f18c7e06519b39ee000023","seq":1,"position":4,"parentId":"37fe64c95332bf73e100001a","content":"Once a ticket is estimated any changes to the requirement will undo the estimate and a new estimate will have to be made."},{"_id":"37fe72bd5332bf73e1000021","treeId":"37f18c7e06519b39ee000023","seq":1,"position":5,"parentId":"37fe64c95332bf73e100001a","content":"Once a ticket is locked in a iteration (Sprint) no changes to the requirement is allowed."}],"tree":{"_id":"37f18c7e06519b39ee000023","name":"Services 2014","publicUrl":"services-2014"}}