ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Project NameTogetherlyDate23-Feb to 29-FebProject ManagerNathan Walker
2
Project Summary (including redirection)Key TasksProgressStatusFinish
3
Togetherly is an app that will allow parents to assign chores to one or more kids and will allow kids to earn rewards for completing their assigned chores.Entity relationship diagram85%On Track11-Mar-24
4
Child home - Database and services70%Delayed04-Mar-24
5
Child home - Business logic80%Delayed04-Mar-24
6
Child home - UI90%Delayed04-Mar-24
7
Parent home - Entities and models50%On Track06-Mar-24
8
Parent home - Database and services20%On Track12-Mar-24
9
Parent home - Business logic and UI10%On Track12-Mar-24
10
Rewards system0%Future Task20-Mar-24
11
Chore approval system0%Future Task04-Apr-24
12
Logic/registration system0%Future Task08-Apr-24
13
Settings and notifications system0%Future Task10-Apr-24
14
Tasks CompletedTasks DelayedTasks Planned
15
Set up page routing system
Design app logo
Design Chore entity
Create/update Chore and Person tables
Design Reward entity
Find/create Git cheat-sheet for the team
Figure out high-level entities to include in architecture and design documents
Create and post team architecture and design documents		Design and implement Chore provider (almost done, awaiting refinement and PR review)
Create/update Chore and Person models (almost done, awaiting refinement and PR review)
Create ChoreAssignment table (not critical for demo 1, didn't have time this week)
Research implementations of repeating tasks (some research done, but no conclusion reached yet)
Create Reward model (not critical for demo 1, work started)
Integrate Chore provider into the Chore UI (Chore provider not yet ready)
Implement Chore service (Chore model not yet ready)
Post test plan document (Nathan)
Sort out model and Chore provider details (Nathan and Kylie)
Look into how to manage dependencies between providers (Nathan)
Integrate finished Chore provider into the Chore UI (Andrew)
Finish Chore detail dialogue (Andrew)
Add fake chore data to the database for the upcoming demo (Ryan)
Finish implementing Chore service using finalized models (Ryan)

Experiment with different implementations of repeating tasks (Kylie)
Research unit testing and mocking practices for Dart (Kylie)
Design and implement Person service (Ryan)
Figure out needs for Person-related state management (Andrew)
Design and implement Person-related providers (Andrew and Kylie)
Create ChoreAssignment model (Kylie)
Create ChoreAssignment table and service (Ryan)
Update providers to use ChoreAssignment service (Andrew)
Add chore completion, editing, and overview to the UI (Andrew)
Create Reward table and start designing Reward service (Ryan)
16
17
18
19
20
Team Members -- Billable HoursKey Project Risks and Issues
21
NameRole/TaskHoursTypeRisks or Issue Description
22
Nathan WalkerProject Manager, QA Lead8.0RiskFlutter is an unfamiliar technology to two of our team members, so there will be at least an initial learning curve in the development process.
23
Kylie CallawayChief Architect, Library & Config. Manager, Front-end Business Logic Dev.5.0
24
Andrew ThibaudeauUI Designer8.5
25
Ryan HarperDatabase Developer5.8RiskSupabase is based on Postgres, which a new SQL dialect for our database developer.
26
27
28
IssueWe are unsure how to manage state dependencies between different providers, something which is critical to our app's functionality.
29
30
31
Total27.3
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100