FUZHUAN: Preparing for Everything

[FUZHUAN]

Which course does this assignment belong to	EE301
Where are the requirements for this assignment?	Teamwork—beta Spring
Team Name	FUZHUAN
The objective of this assignment	Summary of the team FZHUAN's preparing essay in the beta stage.
Other Reference Documents	Method of Construction ( 《构建之法》)

 

---

目录

1. Defining Goals and Task Allocation

1.1 Defining Project Goals

1.2 Task Allocation

2. Developing a Detailed Timeline and Milestones

2.1 Phase Breakdown and Time Planning

2.2 Regular Check-ins and Adjustments

3. Ensuring Technical Readiness and Tool Selection

3.1 Technology Stack

3.2 Development Environment Setup

4. Team Collaboration and Communication

4.1 Team Collaboration Mechanism

4.2 Communication Channels

5. Risk Management and Contingency Planning

5.1 Risk Assessment and Response Strategies

6. User Feedback and Requirements Preparation

6.1 User Research

6.2 User Feedback Channels

7. Preparing for the Sprint Phase

Conclusion

---

1. Defining Goals and Task Allocation

  The first step to success in a project is clearly defining the project's core goals and task allocation. The goal for the FUZHUAN team was to complete the core functionality of the FZZ campus second-hand trading platform in 10 days, followed by testing, optimization, and ultimately improving the user experience. To ensure smooth project progression, we broke down the tasks into actionable sub-tasks and assigned responsibility to specific members, ensuring clear accountability for each phase.

1.1 Defining Project Goals

  The team initially set clear goals for each stage of development. For example:

• Day 1-2: Core Functionality Testing: Ensure the stability of core functionalities, fix bugs found during testing, and ensure the basic functionality is operational.
• Day 3-4: Development of Secondary Features: Develop additional features, such as user management, product categorization, etc., to enhance the platform’s functionality.
• Day 5-6: Overall Testing and Optimization: Conduct global testing and resolve performance bottlenecks, ensuring system stability and smooth performance under various conditions.
• Day 7-8: User Experience Optimization and Feedback: Optimize UI/UX design based on user feedback to enhance user satisfaction.
• Day 9-10: Work Summary and Wrap-up: Summarize the development process, finalize the project documentation, and ensure the platform is ready for handoff.

1.2 Task Allocation

Once the goals were set, the tasks were broken down further and assigned to the appropriate team members. For example:

• Core Functionality Testing: Led by Zhang Yuxin (backend lead) and Luo Yuxin (frontend lead), to ensure smooth integration between the frontend and backend and provide timely feedback on issues found.
• Secondary Feature Development: Handled by Yang Ruoxin, Lin Jiahui, and Yong Yuxin, responsible for specific functional modules and frontend page implementations.
• Overall Testing and Optimization: Led by Sun Xing and Chen Yike to handle backend performance optimization and database adjustments. The frontend team focuses on optimizing page load speed and interactive experience.
• User Experience Optimization and Feedback: Managed by Fang Shuyi and Liu Ningle, who focus on UI adjustments and gathering user feedback to ensure the final version is user-friendly.

2. Developing a Detailed Timeline and Milestones

Progress control is a critical aspect of ensuring timely project delivery. Therefore, we created a detailed timeline at the beginning of the project, defining specific tasks and goals for each phase.

2.1 Phase Breakdown and Time Planning

The development process was divided into several phases, with clear goals for each. For example:

• Day 1-2: Focus on testing and debugging core functionalities, fixing major bugs, and ensuring the platform’s basic functionality is operational.
• Day 3-4: Develop secondary features such as user management and product categorization to enhance the platform’s completeness.
• Day 5-6: Perform overall testing and system optimization to ensure stability and responsiveness.
• Day 7-8: Collect user feedback, and optimize the user experience and interface based on their needs.
• Day 9-10: Summarize the development process, finalize the documentation, and conclude the project.

2.2 Regular Check-ins and Adjustments

At the start of each phase, we held regular team meetings to check progress, assess results, and identify issues. This allowed us to ensure the project was on track and make necessary adjustments. If any phase was delayed or encountered problems, we would promptly adjust resources and task priorities to prevent the overall project from being affected.

3. Ensuring Technical Readiness and Tool Selection

The correct selection of technical architecture and tools directly impacts the project’s progress and quality. Thus, we thoroughly evaluated the technology stack and prepared the team with suitable development tools before starting the project.

3.1 Technology Stack

For the FZZ project, we chose Java for backend development, Vue.js for frontend frameworks, and MySQL for the database. This combination of technologies ensured efficiency and scalability. Additionally, we incorporated Git for version control, Jira for project management, and Jenkins for continuous integration and automated testing. These tools helped the team maintain a high level of efficiency throughout the development process.

3.2 Development Environment Setup

We provided all team members with comprehensive environment setup guides and necessary technical training to ensure smooth usage of the selected tools, minimizing the chance of technical issues during development.

4. Team Collaboration and Communication

Efficient team collaboration and communication are crucial for project success. At the start of the project, we clarified roles and responsibilities within the team, and set up regular meetings to ensure smooth communication between all groups.

4.1 Team Collaboration Mechanism

We established a reporting mechanism where every team member provided daily progress updates and highlighted any issues they faced. This ensured quick responses to challenges and allowed for adjustments when necessary. During the core functionality testing phase (Day 1-2), backend and frontend developers worked closely to provide timely feedback and resolve any integration issues.

4.2 Communication Channels

We used Slack as the team communication tool to ensure quick information flow. Additionally, we used Trello for task tracking and Jira for bug tracking, ensuring all team members could easily track the progress of the project and tasks.

5. Risk Management and Contingency Planning

All projects face unforeseen risks, such as requirement changes, technical challenges, or personnel changes. Therefore, it was essential to have a risk management plan and predefined strategies to handle potential risks.

5.1 Risk Assessment and Response Strategies

At the beginning of the project, we conducted a detailed risk assessment and developed response strategies for potential issues. For example:

• If technical bottlenecks occurred, the team would hold technical discussion meetings to brainstorm solutions.
• If requirements changed during development, the requirements analysis team would update documentation and communicate with the development team to ensure the project direction remained clear.
• If a specific feature fell behind schedule, the project manager would adjust task priorities and resource allocation to ensure the project timeline was maintained.

6. User Feedback and Requirements Preparation

To ensure each feature aligned with user needs, we conducted thorough user research early in the project and set up a feedback mechanism.

6.1 User Research

Through surveys and user interviews, we gathered information on user expectations for a campus second-hand trading platform. These insights helped us plan and design the features more effectively and avoid disconnecting from user needs during development.

6.2 User Feedback Channels

During the User Experience Optimization and Feedback phase (Day 7-8), we paid special attention to user feedback, creating multiple channels (e.g., surveys, online feedback systems) to ensure every comment was addressed and translated into actionable development tasks.

7. Preparing for the Sprint Phase

The sprint phase is typically the final stage of the development cycle, where the team must complete the remaining development, testing, and optimization tasks within a limited time. To ensure smooth progression during the sprint, we prepared thoroughly in earlier phases:

• Code Quality Control: Ensuring all features passed unit tests, code reviews, and continuous integration checks.
• Enhanced Team Collaboration: Ensuring every team member clearly understood their tasks and was ready to address potential risks.
• Timely Feedback and Adjustments: Adjusting the development plan and priorities based on feedback and testing results to ensure sprint goals were met on time.

---

Conclusion

Through clear goal planning, reasonable task allocation, thorough technical preparation, and effective team collaboration, the FUZHUAN team was able to adequately prepare for the sprint phase. By carefully planning and working together closely, we were able to move the project forward smoothly and lay a strong foundation for the timely delivery of the project. Ultimately, the team's efficiency and preparedness ensured the platform was delivered on time and met user needs.