- 'stop planning my wedding during projects'
- 'stop giving up so quickly BUT ask for help sooner'
- 'assign yourself to issues & check that someone else is not already assigned on to a task'
- 'think about branch naming conventions' - We concluded to have one branch per issue and delete it once merged. Make the branch names descriptive.
- 'use issues more, create one before every task bigger than 5 minutes'
- 'everyone going through code together to see changes' (so you get familiar with code you didn't write)
- 'give chance to learn new things by giving the task to the people who will find it most difficult/rewarding'
- 'asking colleagues for expertise - communication'
- 'making Cleo happy' (she feels that we had a great project and she learn a lot, good teamwork)
- 'continue to not make changes overnight'
- 'explaining well to each other'
- 'realistic decisions given time' (good time management at the beginning of the project)
- 'proper pair programming and not veering off for ages'
- 'explain the process you went through on the issues if it was troublesome, so we can learn/reference in the future'
- 'stopping every so often to explain our code to each other'