FUZHUAN: Day 7-8 — SCRUM and PM Report
| 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 | Day 7-8 — SCRUM and PM Report |
| Other Reference Documents | Method of Construction ( 《构建之法》) |
目录
SCRUM Part
| Team Member | Accomplishments | Time Spent | Remaining Tasks | Issues/Problems | Plan for Tomorrow |
|---|---|---|---|---|---|
| Zhang Yuxin | Worked on user experience improvements, addressed UI feedback from users. | 6 hours | Complete user feedback integration. | User feedback had some conflicting results. | Prioritize most frequent user complaints, finalize UX changes. |
| Luo Yuxin | Finished refining UI elements, improved responsiveness based on feedback. | 5 hours | Finalize mobile responsiveness. | UI issues in mobile view under heavy traffic. | Ensure UI works seamlessly under heavy mobile usage. |
| Yang Ruoxin | Improved user flow for product purchase and feedback. | 5 hours | Conduct testing for final product flow. | UI glitches on low-resolution devices. | Test on multiple devices to ensure seamless user experience. |
| Lin Jiahui | Integrated feedback into product and payment flow. | 6 hours | Finalize payment gateway and ensure security. | Payment gateway integration issues with third-party API. | Resolve payment gateway issues and finalize payment process. |
| Sun Xing | Conducted performance optimization for API, fixed remaining load issues. | 5 hours | Finalize API stress testing. | API stress testing not accurate due to slow internet. | Conduct API stress testing in controlled environments. |
| Chen Yike | Worked on further optimization of database queries. | 5 hours | Complete database performance testing. | Large dataset query issues persist. | Optimize large dataset handling in the database. |
PM Report
Expected Tasks Overview
| Task | Estimated Time | Issues Count |
|---|---|---|
| User experience testing and feedback | 16 hours | 4 |
| Final frontend adjustments | 8 hours | 2 |
| Final database and API optimizations | 8 hours | 2 |
Completed Tasks
| Task | Time Spent | Issues Completed |
|---|---|---|
| User experience testing and feedback | 14 hours | 4 |
| Final frontend adjustments | 7 hours | 2 |
| Final database and API optimizations | 6 hours | 2 |
Remaining Tasks
| Task | Remaining Time | Remaining Issues |
|---|---|---|
| User experience testing and feedback | 2 hours | 1 |
| Final frontend adjustments | 1 hour | 1 |
| Final database and API optimizations | 2 hours | 1 |
Burndown Chart

Changes in Task Volume
We found that resolving some of the user feedback issues was more time-consuming than expected. This extended the work related to UI responsiveness and mobile-friendly optimizations. Additionally, payment gateway integration was more complex due to third-party API compatibility issues.
相关推荐
《模式识别与数据挖掘》配套PPT课件
《模式识别与数据挖掘》配套PPT课件
科技成果转化项目进场交易前,评估备案环节需要准备哪些材料?_8.docx
科易网基于AI模型+行业大数据,在技术转移、成果转化、技术经纪、知识产权、产业创新、科技招商等垂直领域的多样化应用场景,推出科技创新领域的AI+工具与数智化解决方案,推动科技创新与产业创新智能化发展。
人工智能通识教育(中职版)课程标准+PPT课件+部分素材+电子活页+在线考核
人工智能通识教育(中职版)课程标准+PPT课件+部分素材+电子活页+在线考核
跨境电商供应链管理(AIGC版)课件+教案+参考答案
跨境电商供应链管理(AIGC版)课件+教案+参考答案
110KV单电源电网三段式电流保护+距离继电保护整定计算说明报告(23页+6000字)
内容概要:本文是一份关于110kV单电源电网继电保护整定计算的综合性技术报告,全文共23页、约6000字,系统阐述了三段式电流保护与距离保护的设计原理及其整定计算方法。报告深入分析了电力系统在短路故障条件下的电流与阻抗特性,详细推导了电流保护Ⅰ、Ⅱ、Ⅲ段的动作范围、整定原则、灵敏度校验及时间配合机制,确保满足继电保护的选择性、速动性、灵敏性和可靠性“四性”要求。同时,针对长距离或重要输电线路,补充介绍了距离保护的阻抗整定计算方法,并可能结合Matlab进行仿真验证与辅助计算,提升整定结果的准确性与工程实用性。; 适合人群:适用于电气工程及其自动化相关专业的高年级本科生、研究生,以及从事电力系统继电保护设计、运行维护的工程技术人员;要求读者具备电力系统分析、短路计算及继电保护的基础理论知识。; 使用场景及目标:①掌握110kV单电源辐射型电网中三段式电流保护的整定流程与实际计算步骤;②理解距离保护的工作原理及其在复杂工况下的应用优势;③完成实际工程项目的保护配置与整定计算任务,或作为课程设计、毕业设计及科研课题的技术参考资料;④结合Matlab工具实现整定计算的程序化处理与动作特性仿真验证。; 阅读建议:建议读者结合《电力系统继电保护原理》等相关教材同步学习,重点研读整定公式的推导过程与典型算例的计算细节,注意区分电流保护与距离保护的适用场景与配置逻辑,有条件时应利用Matlab等工具对保护动作行为进行建模与仿真,以深化对保护协调配合机制的理解。


