Project Management

How can we track the progress of the current project, understand each member’s tasks, and reasonably advance the development process?

In this case, we can consider using a Scrum Board. This tool clearly and intuitively displays all the tasks in the project and the current work status of each team member, improving work transparency and team collaboration efficiency.A typical Scrum Board includes the following vertical columns:

· Backlog: Lists all the tasks that need to be completed. · Todo: Lists the tasks that are about to be started. · Doing: Lists the tasks that are currently being worked on. · Review: Lists the tasks that need to be reviewed by other team members. · Done: Lists the completed tasks.

We can write down the tasks that need to be completed during development on sticky notes and place them in the Backlog column. Based on priority, the most urgent tasks can be moved to the Todo column. Tasks that are being worked on should be placed in the Doing column. Once a task is completed, it can be moved to the Review column, and team members will review it. After approval, the task can be moved to the Done column.

To distinguish each person’s tasks, we can label each sticky note with a name or use specific stickers. Additionally, we can allocate a row for each member in the board, listing their tasks in the corresponding row.

When multiple members are working on the same project or file, conflicts can arise. In such cases, Git can be used for version control. Git is a distributed version control system that tracks all changes made by team members and allows us to revert to any previous version of the project. It helps us with backups and recovery, and through branch management, it assists in handling file conflicts.

Each member can work on their own project branch, and after completing their work, they sync their changes to the main branch. If two members modify the same file, the later commit will trigger a conflict warning when syncing with the main branch. At this point, the later submitter can manually resolve the conflict based on the conflict details provided in the file, preventing data loss when multiple people are editing the same content simultaneously.