mid sprint1 status - blucas6/BudgetBuddy GitHub Wiki
Mid-Sprint 1 Status
Date: 10/08/2024
Major Project Feature Summary:
Feature | Status | Completion Percentage |
---|---|---|
Transaction Handling (Functionality) | :yellow_circle: | 50% |
Database Setup | :yellow_circle: | 60% |
Home Screen UI/UX Design | :yellow_circle: | 40% |
Current Project Status: AMBER
The team is making steady progress, but the database integration is taking longer than anticipated, and the transaction handling functionality is not fully complete. The UI/UX design is on track but still needs further development.
Team Goals for the Upcoming Week:
- Finalize transaction handling (Ben).
- Complete database schema integration (Deep, Jash).
- Finish the home screen UI/UX design, including navigation and layout (Kriza, Shi).
Individual Team Member Status:
-
Ben (Functionality):
- Worked on basic transaction handling.
Next week: Finish implementing the add and view transactions features.
- Worked on basic transaction handling.
-
Deep (Database):
- Worked on the initial database schema design.
Next week: Finalize database schema and start integration.
- Worked on the initial database schema design.
-
Jash (Database):
- Assisted with database schema design and integration planning.
Next week: Help finalize schema and work on database integration with the app.
- Assisted with database schema design and integration planning.
-
Kriza (UI/UX):
- Worked on the home screen layout and 50/30/20 budget chart design.
Next week: Finish the home screen layout and integrate navigation.
- Worked on the home screen layout and 50/30/20 budget chart design.
-
Shi (UI/UX):
- Assisted with home screen design and initial navigation setup.
Next week: Help finalize the UI and test navigation.
- Assisted with home screen design and initial navigation setup.
Team Activities:
- Team Meeting (10/02/2024): All team members attended to review progress.
- UI/UX Pair Programming (10/05/2024): Kriza and Shi worked on the home screen design.
Team Project Decisions:
- Adjusted the database schema to accommodate additional transaction types.
- Decided to move collaborative profile functionality to Sprint 2.
Other Comments:
The delay in database integration might require additional time, but we expect to catch up by the end of the sprint.