Align and define branch-strategy

[codeDavidLopez]

Purpose

1. As a developer
2. I want / need branching and merging strategy
3. So that commits and the code are organized

Involved team members

• all developers

Affected artifacs

• planning document
• architecture description
• board
• ...

DoD general criteria

• Feature has been fully implemented
• Feature has been merged into the mainline
• All acceptance criteria were met
• Product owner approved features
• All tests are passing
• Developers agreed to release

[codeDavidLopez]

Estimation: 2

[julianrosenberger]

Create Markdown for documentation

• For each issue we create a branch
• Code gets pair-reviewed and merged, once developer says he finished the task
• In the sprint review we focus on demo

[julianrosenberger]

(rules for commit and push)

[codeDavidLopez]

Strategy written and merged in the base. Real estimation: 1