# Project Workflow Template

## General Agreements

* Internal Communications Channel: Teams? Slack?
* Method: Kanban or something else
* Working days: when, where and how - both individual and with team. The total contribution for every team member should be 19hrs per week and tracebale via issue tracker
* Team meetings: when, where and how?
* Stand-ups: when, where and how?
* Retrospectives: When and how?
* Sprints: when and how? 

## Roles and Responsibilities

* Who is responsible for what

## Project Milestones

* A list of features and when they should be delivered


## Project Agreements

### Creating an issue

Everyone updates the project issue board with the tasks he/she is doing.

When you create an issue, please add:
*  General description why we are doing this
*  What needs to be done (AC - acceptance criteria)

### Issue creation during team meetings
1. Team meeting --> Issue discussed and added to Gitlab (only title) --> Issue description added (Project lead) --> Issue is added to Backlog

2. Team meeting --> Issue discussed and added to Gitlab (only title) --> Issue description added (Project lead) --> Issue needs refinement --> Team meeting

## Code review
*  After creating PR, share it in Slack to make other developers aware
*  Code review is optional but highly recommended (especially if you have a lot of changes)