Overview

As part of the project requirement, we used an adapted Scrum methodology. The process was applied throughout the project lifecycle to efficiently manage tasks, track progress and deliver value incrementally.

Task Management

The team's strategy was to split the workload by focusing on implementing one microservice at a time per member. The selection process done by the team was to prioritize the development of key functionalities essential for social media platform. However, at a later time, we decided to divide the team into front-end and back-end to optimize efficiency on developing the project.

To monitor progress on each task, a weekly meeting was held at the end of each week via Discord. During these meetings, team members discussed the status of tasks and addressed any concerns or challenges related to their respective assignments.

Additionally, the team utilized Trello to categorize tasks in an organizational way, further details on how it was implemented will be discussed in later section. The Trello board was often referenced during the weekly meetings to provide a comprehensive overview of task statuses and prioritize work for the next upcoming sprint.

Requirements Planning

The features and functionalities needed for each microservice were defined more in-depth on a shared document during the initial phase of the project's first sprint. Each member has specified the needs and assigned their own tasks. Below is a screenshot of the requirements planning for the project:

Scrum/Kanban Boards - Trello

The use of Trello allowed team members to visualize the status of tasks and track their progress throughout the sprint.

Trello board were organized into four main lists: "Backlog," "Sprint Backlog," "In Progress," and "Completed For Each Deliverable."

• Backlog: contains the overall features and functionalities of the project that were planned for future sprints or releases.
• Sprint Backlog: includes tasks that were selected for the current sprint.
• In Progress: tracks the current tasks that were actively being worked on by team members.
• Completed: contains tasks that have been finished on each sprint and were ready for review.

Furthermore, labels were added to each Trello card to indicate which relevant microservice it belongs to and the task category (front-end, backend, testing, deployment).

Each team member was assigned to tasks based on their responsibilities, ensuring clarity and understanding on who will be working with what task. This labeling system enhanced visibility and organization within the Trello board, facilitating smoother task management and coordination among team members.

Project Timeline

The brief overview of timeline for the project is as follows: