Sprint Summary Essay

FZU Meteorological Bureau —— Alpha Sprint_Sprint Summary Essay

Catelog

I. Project Progress
1. Expected Plan
Day 1 (12.12)
Day 2 (12.13)
Day3-Day4 (12.14-12.15)
Day5-Day6 (12.16-12.17)
Day7-Day8 (12.18-12.19)
Day9-Day10 (12.20-12.21)
2. Actual Progress
II. Teamwork
1. Group Division & Workload Distribution in the Alpha Phase
2. Teamwork and Collaboration
3. Gains and Insights of Each Member
III. Outlook for the Next Stage
1. Future Plans
2. Next Sprint Plan

I. Project Progress

1. Expected Plan

Day 1 (12.12)

• Project manager(Chen Ye)：
  Clarify the overall project goals and milestones at each stage, and formulate a detailed project implementation schedule. Organize and hold a project kick-off meeting to synchronize the project background, core values and acceptance standards to all members; Complete task dismantling and division of labor deployment according to the functions of each group; Write and output the first draft of the project blog to synchronize the project launch progress.
• UI Design Group(Zhang Shimin)：
  Align the detailed requirements of the product prototype with the product and technical team, including page layout logic, interaction flow, core function entrance location, etc.; Start the design of the core interface, and give priority to the visual style definition of frequently accessed pages such as the platform homepage and personal center.
• Front-end development group(Wang Jiarui, Li Yifei)：
  Build a development environment that meets the requirements of the project technology stack, complete basic work such as dependency package installation and code repository initialization. Build the basic framework of the project’s core pages and determine the reuse scheme of routing rules and global components.
• Backend development group(Sun Chenen, Chen Xueting, Zhang Zhikai,Liu Zhongbo )：
  Design the database table structure based on the project requirements document, clarify field types, associations and indexing rules; Build a back-end development and testing environment and configure servers.
• Database group（Li Yuxin, Lin Qixuan ）：
  database table structure design, data dictionary maintenance; Database index optimization, master-slave replication architecture, and data backup strategy formulation
• Test group(Chen Hongyu, Lin Juntian)：
  Formulate the whole process of the project test process specification, and clarify the execution nodes of unit testing, integration testing, and system testing. Write test case documentation that covers forward and reverse testing scenarios for core functional modules.

Day 2 (12.13)

• Project manager(Chen Ye)：
  Track the implementation progress of each module task, collect resource gaps and technical difficulties encountered by each group, and coordinate internal and external resources to solve problems in a timely manner. Organize short daily stand-up meetings to synchronize progress and expose risks.
• UI Design Group(Zhang Shimin)：
  Output a high-fidelity design draft of the full core page, including page element size, color specification, font level, interactive effect annotation, etc., and submit it for review.
• Front-end development group(Wang Jiarui, Li Yifei)：
  Complete the basic layout development of the platform homepage to realize page skeleton construction and static resource rendering. According to the principle of functional responsibilities and reusability, complete the splitting of front-end components, such as navigation bar components, card components, search components, etc.
• Backend development group(Sun Chenen, Chen Xueting, Zhang Zhikai,Liu Zhongbo)：
  Complete the development of basic interfaces for user authentication modules, covering core interfaces such as user registration, login, token verification, and password reset, to ensure the smoothness of the user authentication process.
• Test group(Chen Hongyu, Lin Juntian):
  Refine test scenarios and supplement test cases for boundary conditions and abnormal processes, such as limiting the number of password errors when users log in, null value submission handling, and other scenarios. Prioritize test cases to provide a basis for subsequent test execution.

Day3-Day4 (12.14-12.15)

• Front-end development group(Wang Jiarui, Li Yifei, Zhang Shimin)：
  Focus on intelligent interaction and core business display, develop air quality data display components, and support data visualization (such as line charts, bar charts); Multiple rounds of iterative optimization are carried out for the interface effects and interaction logic of the air quality display component to improve the user experience.
• Backend development group(Sun Chenen, Chen Xueting, Zhang Zhikai,Liu Zhongbo)：
  Complete the docking of third-party air quality APIs to realize data pulling, cleaning, and formatting. Develop personalized recommendation interfaces to output customized air quality suggestions and related service recommendations based on user browsing history and regional information.

Day5-Day6 (12.16-12.17)

• Some front and rear end joint debugging：
  Organize the front-end and back-end teams to carry out joint debugging work, focusing on completing the docking of core pages such as the homepage, air quality query page, and personal center with the back-end interface to ensure that the data transmission is normal and the page rendering is correct. Solve the problems of interface parameters mismatch and data format inconsistency that occur during the joint commissioning process.
• All members：
  Centralized optimization is carried out for the problems of unreasonable interface layout, unsmooth interactive experience, and unbeautiful visual effects in the project, including button style, page color matching, pop-up window position, loading animation and other details. Collect feedback from internal trials and make quick iterations.

Day7-Day8 (12.18-12.19)

• Front-end development group(Wang Jiarui, Li Yifei, Zhang Shimin)：
  The design details of the front-end interface and the smoothness of page jumps are specially optimized to solve problems such as page lag, jump delay, and slow loading. Optimize the adaptation effect of mobile terminals to ensure a consistent access experience across multiple terminals.
• Test group(Chen Hongyu, Lin Juntian)：
  Build an independent test environment to complete the deployment and configuration of project code to ensure the consistency between the test environment and the production environment. Configure environment variables to achieve normal connection between front-end and back-end services.
• All members：
  According to the code specifications formulated by the project, supplement and improve the comment content of the full code, including interface document comments, function comments, complex logic comments, etc.; Organize the interface description documents, and clarify the interface address, request method, parameter description, return format, and other information.

Day9-Day10 (12.20-12.21)

• All members：
  Internal alpha version acceptance. Organize the internal acceptance meeting of the project and conduct a comprehensive review of the alpha version according to the acceptance standards. Record the problems found during the acceptance process and form a rectification list.
• Test group(Chen Hongyu, Lin Juntian)：
  Continuous software testing. Test tool selection and automated test start-up: Combine the project technology stack and testing requirements to select appropriate automated test tools; Build an automated testing framework, write automated test scripts for core functions, and gradually promote automated test execution.
• Preparation of project materials：
  Organize project achievement materials and produce project report PPT, covering project background, goals, implementation process, core achievements, items to be optimized, etc. Write a project summary report.
• Submit the final Alpha Sprint outcome package：
  Summarize all deliverables such as project code, test reports, design drafts, interface documents, and report PPTs, and file them according to the requirements and submit them formally.

2. Actual Progress

1. The weather api displays the video

In the previous article on Alpha Sprint 2, we mentioned that due to unknown reasons, the weather API interface call to obtain data and not display it on the frontend. We are excited to complete the fixing and development of this module at the end of the Alpha Sprint phase.

• First of all, I would like to show you the API interface development documentation for Zephyr Weather

Zephyr weather development documentation

2. The current situation of the project is displayed

1. User interface design and implementation

• [Task Detail 1, such as implementing the navigation layout of each functional module on the homepage (homepage, system announcement, volunteer activities, volunteer wheel communication, personal center, leaderboard)]
  

• [Task Details 2, System Announcement]
  

• [Task Detail 3, Volunteer Activities]
  

• [Task Details 4, Volunteer Forum]
  

• [Task Detail 5, Personal Center]
  

• [Task Details 6, Leaderboard]

2. User interface design and implementation

• [Task Detail 1, Announcement Management]
  

• [Task Detail 2, Volunteer Forum Management]
  

• [Task Detail 3, Personal Center]
  

• [Task Detail 4, User Management]
  

II. Teamwork

1. Group Division & Workload Distribution in the Alpha Phase

2. Teamwork and Collaboration

• Collaboration between front-end and back-end teams was highly effective, with joint problem-solving meetings addressing many integration challenges.

• Each member’s unique strengths were fully utilized, and this diversity fostered mutual respect and reliance. Constructive feedback and brainstorming further enhanced problem-solving capabilities.

• Cross-departmental coordination played a pivotal role in breaking down silos, as shared project management tools streamlined task tracking and resource allocation.

• Mutual accountability was embedded in our workflow; each team member took ownership of their responsibilities, and proactive support was offered whenever a colleague faced obstacles.

• Celebrating small wins together strengthened team cohesion, reinforcing the belief that collective achievements are more impactful than individual ones.

• Adaptive collaboration strategies, tailored to the evolving needs of the project, ensured that we remained agile and responsive to unexpected changes.

3. Gains and Insights of Each Member

• 1. Project manager(Chen Ye)
     As a project manager in the alpha stage, I have a better understanding of “dynamic project management”. Compared to the previous fixed plan, this time I learned to flexibly adjust tasks according to the actual schedule: for example, when the development of front-end components is delayed, coordinate the back-end to advance the preparation of interface debugging first, avoiding team idleness.
• 2. Front-end development（Wang Jiarui）
     As a developer responsible for front-end routing and privilege control, the alpha phase gave me a deeper understanding of Vue’s route guarding and privilege blocking logic. Previously, it was limited to “implementing functions”, but now it has learned to design more flexible permission rules based on business scenarios - such as menu visibility to distinguish between different user roles, which not only ensures security but also takes into account user experience.
• 3. Front-end development（Li Yifei）
     This time, I was responsible for the scaffolding construction of the Vue project, and my biggest gain was the improvement of “engineering thinking”. At first, it was just a simple initialization project, but later it was discovered that it was necessary to consider dependency version compatibility, environment variable differentiation, and code specification constraints, which directly affected the smoothness of subsequent development.
• 4. Front-end development（Zhang Shimin）
     As the front-end responsible for page components and styles, the alpha phase gave me a new perspective on design restoration and user experience. Previously, it only pursued “looking like a design draft”, but now it will actively consider the details of the interaction, and these small optimizations make the interface easier to use.
• 5. Backend development (Sun Chenen）
     Responsible for the construction of the Spring Boot multi-module architecture, my biggest gain is the idea of “modular design”. At the beginning, all the code was stacked in one module, and later the core business module, tool module, and common dependency module were split, which not only reduced the code coupling, but also facilitated the independent iteration of subsequent functions.
• 6. Back-end development（Chen Xueting）
     When doing user login authentication and permission menu management, I have a more practical understanding of “system security”. The permission menu should be dynamically bound to the user role, so that low-privilege users can not see the high-privilege functions, and the menu loading efficiency of different roles must be ensured.
• 7. Back-end development（Zhang Zhikai）
     Responsible for business CRUD and unit testing, my biggest gain is the improvement of “code quality awareness”. Previously, writing code only pursued functional implementation, but now it actively writes unit tests to cover the core logic, which makes it less likely to “change one place” in subsequent iterations.
• 8. Back-end development（Liu Zhongbo）
     This time, I was responsible for Redis caching, file services, and thread pool optimization, and I had a more specific practice of “system performance optimization”. When uploading and downloading files, I learned to use fragmented upload and breakpoint resumption to improve the transfer experience of large files, and also reduce the risk of service crashes.
• 9. Test（Chen Hongyu）
     As a functional tester, I will now actively design boundary scenarios - such as password length exceeding the limit when logging in, null submission, and wrong parameter types in interface requests, which allows many hidden bugs to be discovered before launch.
• 10. Test（Lin Juntian）
      Responsible for performance testing and user acceptance, my biggest gain is “looking at the system from the user’s perspective”. This made me realize that testing is not only about functionality, but also about ensuring that the system is easy to use and performs reliably.
• 11. database（Li Yuxin）
      My biggest gain from database table structure design and data dictionary maintenance is the rationality of data modeling. At first, it only considered the storage requirements of fields, but later learned to design foreign keys and split tables reasonably according to business associations, which not only avoided data redundancy, but also improved query efficiency.
• 12. database（Lin Qixuan）
      Responsible for database index optimization and master-slave replication, I have a deeper practice of “data layer stability”. When formulating a data backup strategy, I learned to use a combination of regular full backup + incremental backup to ensure data security.

III. Outlook for the Next Stage

1. Future Plans

1.1 Core objectives

• Complete feature iterations and issue fixes in the beta sprint stage to ensure that core product scenarios (air quality query, volunteer activity participation, and community interaction) are stable and available.
• Collect effective feedback through beta testing to optimize product experience and performance to meet the quality standards of official delivery;
• Complete the deployment, acceptance and delivery of the final version of the product, and output a full set of deliverables that meet the requirements.

1.2 Mission-critical

• Phase 1: Beta sprint execution
  Core actions: bug fixes, function optimizations, test feedback, version iterations;
  Outputs: Beta system, bug fix list, public beta feedback report.
• Phase 2: Beta feedback closed-loop and functional improvement
  Feedback processing: Sort out the beta public beta feedback by category, prioritize fixing high-priority (P0/P1) issues (such as functional failures, data anomalies, and interaction lags), and selectively optimize low-priority issues after evaluation
• Phase 3: Performance and safety final check
  Performance optimization: Addresses performance issues exposed during the beta phase (such as slow interface response and page loading lag).
• Phase 4: Delivery Preparation and Acceptance
  Deliverables: Packing the final version of the system code (front-end + back-end), database scripts, test reports (functionality/performance/security)
  Data preparation: Import the official environmental initial data (latest air quality data, official volunteer activity information, default role permissions)
• Phase 5: Formal delivery and go-live support
  Delivery Finishing: Hand over the full set of deliverables to ensure normal use by users.

2. Next Sprint Plan

2.1 Sprint to the goal

• Functional level: Fixed P0/P1 bugs left over from the alpha stage (such as abnormal login and data query failure), and completed 2 core function optimizations (real-time air quality warning, volunteer activity duration certification) to ensure that there are no fatal problems in core scenarios.
• Test level: Complete 3 rounds of internal testing + 1 round of small-scale public testing (50-100 target users)
• Performance: The response time of the core interface is ≤ 500ms, and the loading time of the page above the fold is ≤1.5s, with no obvious lag.
• Delivery level: Deploy the beta test environment and output bug fix lists, test reports, and first drafts of interface documentation.

2.2 Team division of labor and task arrangement

2.3 Deliverables

• Features: Normally accessible beta system (with alpha legacy bug fixes, 2 core feature optimizations);
• Documentation: Beta test report, bug fix list, user beta feedback report;
• Environment: The deployed beta test environment (with public network access).