Project Management - COS301-SE-2022/Map-out-game-reserves-using-aerial-photographs GitHub Wiki

About

Our team worked in a mix of an egoless and chief programmer structure, with our team lead, Ben, being the main communicator between our team and the lecturers and clients. We all had an equal say in what we wanted from the project and discussed with one another what the next steps were.

The team underwent weekly meetings internally, we would have either weekly or bi-weekly meetings with both the clients and lecturers in order to stay up to date with what we were doing and what we needed to do.


Project Board

The delegation of jobs was represented on GitHub’s Kanban board. The GitHub project board serves as an easy and efficient way to delegate tasks to each member. This project board also served as a source of motivation as we could see how much we had completed and moving the completed tasks to the “done” board was a source of satisfaction which encouraged us to do more and complete more tasks.

The Dylpickles Project Board


Pert Charts

These PERT charts served as time management for the entire group and we were able to keep up to date with where the whole project was. The PERT charts indicate how long each task would take and what should be of highest and lowest priority. It included an indication of the latest point at which we could start each task to ensure that we reached our goal.

The Dylpickles PERT Charts