What went well

• Refactoring/repurposing was done efficiently and split among different people (free-for-all: whoever was free to create issue and work on that part)
• Forking workflow done smoothly
• Communication and helping each other. Every team member was consistently contactable and put in effort to help each others' individual problems (bugs etc.)
• No major bugs that require long debugging hours

What didn't go well

• Merging was messy - many merge conflicts to resolve
• Some minor hiccups during testing and adjusting minor behaviour differences between AB3's Find feature and Bamboo's Find feature
• Documentation bugs in HTML generated not evident in our IDE
• Planning of tasks was not done comprehensively. We did not foresee that the task of refactoring the AB3 code would cover a lot of the functions we wanted to implement.
• Documentation was not done efficiently and incrementally; was left to the last minute where the bulk of the documentation was rushed.

Plan for future

• Think about the order of PRs to reduce the amount of merge conflicts needed
• Each member should be assigned tasks that are closely related to minimize the amount of merge conflicts, if more people were to work on the same component.
• Split PRs into smaller increments (e.g. instead of a whole feature)
• Proper scheduling of rounds of documentation to check and update accordingly (one round of documentation in the planning stages of each version, and one round closer to the release date)