Jeremy Neo

After splitting the team up, I felt a lot better in terms of the team coordination. We are able to communicate well as we are always actively online. Before this, the communication was really bad especially when there is an emergency, no one shows up, at least the one who is responsible for the task. Even though we have better communication, we still overestimated the tasks that we can do for this release as we completely underestimated the workload of other module's CAs which took us lots of time to complete them. Overall, I still think that we are doing a lot better in terms of efficiency and progress of our work.

Dennis Willie

The work coordination of the team after the team split have gone so much better. Before the team split, I had to think twice about delegating tasks. Sometimes I delegated tasks just because I had to delegate, not because I think the person has the sufficient ability, and this was largely because of the pressure to make the appearance that the whole team is working even though it's only 3 members who are actively working on the project. However, on my side, I have to admit that I overestimated the time I was going to have in this release and it can be reflected by me creating the task for the navigation chatbot and putting it inside the release. Because of the amount of tasks that I have to do, for example, user testing because now there's no user tester on the team after the team split, I have to spend more time outside my role rather than what I want to do, and that's in the name of making the whole project better. I also spent a lot of time helping to create the search page (initially, this was not my task, however I had to jump in since the components that are used was my components and a help from me is needed). I ended up creating most of the search page. Because of this, I had so limited time to do anything else. As a team lead, I should've taken into account the tasks that I may have to jump into in order to help the team move.