ConQuest is a sports management and nutrition tracking web application I developed with 7 other university students for a software engineering course. Here each of us acted as full-stack developer. Responsible for all layers of the tech stack, from design to implementation.

We worked in an Agile Scrum environment, before each sprint we would groom our backlog, discuss user stories with the PO (the course coordinator), and perform tasking. During the sprints we would have bi-weekly standups where we would discuss what we did in between standups, what we were currently working on, what we would be working on, as well as any current/future improvements, those present at these standups would consist of the developers (I and my team), our Scrum Master (a final year software engineering student), and possibly the PO and/or a member of the teaching team acting as a CTO or some other position for the fictional company we were working for.

During the sprints we would perform pair programming, choosing to co-locate in a computer lab enabled us to work more efficiently as a team, learn from others, and allow any impediments or frustrations to be quickly communicated.

At the end of each sprint, we would have a sprint review, demo, and retrospective. In the Sprint Review, the different teams in the course would test each other's applications, marking each user story against their respective assessment criteria to check if they fulfilled it during the sprint, here I got experience in manual testing features, and writing about how to reproduce an error. The Sprint Demo is where my team and I would showcase the new features of our application, as well as answer any questions the audience (the students in the course, the teaching team), had about the future of our application. In the Retrospective, we would generally discuss what worked during the sprint, what we should start doing, and what we should stop doing, although the specifics depend on the technique we were using.

In terms of technology, we developed ConQuest using Spring (the Java framework), MariaDB, and Bootstrap, and in terms of languages Java, Javascript, SQL, and HTML. Here acted as a full stack developer, on an average day I would pick up a task (possibly with another teammate), and refine what the task wants (e.g. what assessment criteria must this task meet? Is this task encompassing too much?), and then begin implementing it, working on the frontend using HTML, Javascript, and styling with Bootstrap, developing controller endpoints using Sprinboot, and Java, and saving objects to the database / performing queries using JPA, and SQL.