We would have daily team meetings outlining what we had done the day before, what progress we aim to make that day and go over any issues. This ensured that everyone was held to account and encouraged team discussion when it came to solving problems.
Constant Channel of communication
Despite COVID and us not being able to meet in person, it was important to have as many other clear communication channels as possible.
Other than these daily meetings, we also stayed up to date with each other via platforms such as Teams and Whatsapp.
Using Tools for Managing Tasks
During our meetings, we would assign tasks as well as deadlines based on when we expect to complete them. We would manage and keep track of these tasks by using Trello.
Weekly Feedback from Client
We would have regular weekly meetings with our client where we could report our findings for the week and get their feedback. This was important to ensure that our vision and the client’s vision were closely aligned.
Our project from the very beginning was shrouded with a lot of uncertainties, so we followed an agile methodology in project development which included short development cycles to fit our project needs.
Regular Peer Code Reviews
When it came to codebase management, we utilised new branches for each new feature or fix. To merge changes with our stable master branch, we required pull requests to be reviewed and approved by the other two members of the team.
Short Reports before decisions
Each time we would reach a crossroad, such as deciding which chatbot platform we are going to use or how we are going to implement the API, we would create a short report outlining all the research we have done.
Within this report, we would weigh up all our options, estimate how long implementation could take and either go forward or reject the decision via group consensus.
These reports can be found attached to relevant Trello cards as well as our development blogs when we were doing research.
We created road maps that would outline all the tasks we expected to get done during each and every week leading up to our delivery date.
The roadmap was designed to be heavy with the number of tasks early on but reduced as the weeks went by.
This allowed us to have a clear idea of what we want to get done each week but also give leeway and mitigate issues caused by unexpected problems.