FocusFlow β Sprint Plan

[FOCUS_2025_SE]

目录

• Project Overview
• Introduction
• Part 1: Assumptions, Goals, and Sprint Plan
• Part 2: Design, Implementation, Testing, and Release
• Blog Planning and Sprint Schedule
• Specific Requirements for Sprint Essay Blogs
• Conclusion

Project Overview

Course	2501_MU_SE_FZU
Assignment Requirement	Sixth Assignment - Beta Sprint
Team Name	Focus_2025
Goal of this assignment	Clarify Code Standards, Sprint Tasks, and Plans for the team Beta Sprint
Other references	IEEE Std 830-1998, GB/T 8567-2006

Introduction

Following our Alpha retrospective, we enter the Beta sprint (Dec 28, 2025 - Jan 6, 2026) with clarity and purpose. This blog outlines our detailed plan to address previous shortcomings and deliver meaningful improvements to FocusFlow. We answer the core questions related to our assumptions, goals, plans, and our approach to design, implementation, testing, and release.

Part 1: Assumptions, Goals, and Sprint Plan

A. Core Assumptions:

1. Improving specific, high-friction user interactions will disproportionately increase overall user satisfaction.
2. Implementing basic engineering processes (Git flow, code review) will reduce bugs and improve development speed in the latter half of the sprint.
3. Proactively writing and scheduling blogs will provide better project visibility and reduce last-minute stress.

B. Sprint Goal:
To successfully complete a 7-working-day Beta sprint, delivering a polished FocusFlow v1.1 that demonstrably improves usability, interface, and code quality over the Alpha version.

C. Detailed Plan & Improvements for the Next Phase:

Area for Improvement	Alpha Phase Issue	Beta Phase Action Plan
1. Team Division of Labor	Vague roles, bottlenecks.	Define clear roles: Frontend Lead (UI/Animations), Backend/Logic Lead (APIs/State), QA/Process Lead (Testing/Git). Tasks from the backlog are assigned to roles upfront.
2. Tool & Process	Chaotic Git, no testing.	Enforce Git Feature Branch Workflow: All changes via PRs with code review. Introduce a testing protocol: A mandatory manual smoke test checklist for each PR.
3. Blog & Time Planning	Last-minute, low-quality blogs.	Create a publishing schedule (see below) and assign a blog owner for each post. Blogs are drafted incrementally alongside development.
4. New Features & Polish	Clunky UX, unengaging UI.	Implement 5 priority features (F1-F5) derived from user pain points and polish goals.

Part 2: Design, Implementation, Testing, and Release

A. Features to be Improved/Added (Design & Implementation):

1. F1: Streamlined Password Reset: Redesign flow to use phone number only, with a confirmation step and a 10-second delay button for security.
2. F2: Animated Homepage: Implement gradient background and typewriter text animations for a dynamic welcome.
3. F3: Visual Task Management: Transform task lists into card components with expand/collapse for completed items.
4. F4: Focus Mode Guard: Add a persistent warning modal for any interaction during an active timer.
5. F5: Personalization: Correctly display the logged-in user's first name in the app header.

B. Testing Strategy:

• Code Review: Mandatory for all pull requests.
• Manual Smoke Testing: A defined checklist (login, create task, start timer, test new password reset) executed before merging any PR affecting core flows.
• User Testing: We will conduct a structured session with 3-5 external users in the middle of the sprint. Findings will be documented in a dedicated User Usage Survey Report blog.

C. Release Plan:

• The final deliverable will be a standalone APK file and a web demo link, ensuring we are not dependent on app store review cycles for our deadline.
• All source code, final builds, and documentation will be tagged in our GitHub repository by the final deadline (January 6, 2026, 23:59).

Blog Planning and Sprint Schedule

Date	Primary Development Focus	Blog Publication (Not on the same day per team)
Dec 28-29	Sprint Planning, F1 (Password Reset) backend	1. Alpha Phase Retrospective (Dec 28/29)
Dec 30	F1 Frontend, F5 (User Name)	2. Preparing for Everything (Dec 29/30)
Dec 31	F2 (Homepage Animations)	3. Beta Sprint Essay 1 (Focus: F1)
Jan 1	F3 (Task Cards)	4. Beta Sprint Essay 2 (Focus: F2)
Jan 2	F4 (Focus Guard), Integration	5. Beta Sprint Essay 3 (Focus: F3) & 6. Code Standards
Jan 3	Testing, Polish, User Testing Session	7. Beta Sprint Essay 4 (Focus: F4/F5)
Jan 4	Fixes from feedback, Final Integration	8. User Usage Survey Report
Jan 5	Final Build, Documentation, Defense PPT	9. Beta Sprint Essay 5 (Sprint Wrap-up)
Jan 6	Final Checks & Submission	10. Beta Sprint Summary Essay & Top-of-line Collection

Specific Requirements for Sprint Essay Blogs

Each of our 5 beta sprint essays will strictly contain:

1. Scrum Section: A table for each member detailing: Yesterday's achievement (task, time spent), Problems, Today's plan. We will include code commit links/screenshots for dev work and test result screenshots for QA work. A unique, daily scrum meeting photo will be attached.
2. PM Report: A summary of total project tasks (# of issues), completed work, and remaining work. We will include a Burn-Up Chart, a chart showing task volume changes (for discovered work), and the latest running screenshots/gifs of the featured module.

Conclusion

We are entering the Beta sprint not just with a list of features, but with a battle-tested plan to improve how we work. By combining targeted feature development with strengthened engineering practices, we aim to deliver a superior product and a more professional team performance.