ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Project NameTogetherlyDate08-Mar to 14-MarProject 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%Possible Delays20-Mar-24
4
Chore assignment & completion45%Delayed21-Mar-24
5
Family system (read-only)65%Possible Delays21-Mar-24
6
Reward store (read-only)25%Possible Delays22-Mar-24
7
Family editing0%Future Task26-Mar-24
8
Rewards editing0%Future Task01-Apr-24
9
Chore approval system0%Future Task10-Apr-24
10
Reward redemption system3%On Track08-Apr-24
11
Authentication system0%Future Task08-Apr-24
12
Notifications0%Future Task11-Apr-24
13
Webapp deployment0%Future Task28-Mar-24
14
Tasks CompletedTasks DelayedTasks Planned
15
Review Person service PR
Discuss "isRedeemed" field of the Reward entity
Research unit testing and mocking practices for Dart
Finalize Reward model
Create views in the database to augment certain tables with a family ID column
Finish Chore edit UI		Document team approach to proxy providers, set up example for family ID (Close to finished as of 14-Mar)
Figure out how to integrate ChoreAssignment into the Provider layer (Did not get to this week)
Experiment with different implementations of repeating tasks (Still working on this)
Plan Person-related aspects of Provider layer (More details to be sorted out)
Design the ChoreApprovalRequest entity and model (Delayed until we have a plan for chore repetition)
Finish Chore overview UI (Waiting on more work to be finished with services and providers)
Add UI support for marking chores as complete (Waiting on ChoreAssignment integration into the provider layer)
Create ChoreAssignment model and service (In progress, but feedback and refinement is needed)
Create Reward service (Waiting on Reward model)
Create ChoreApprovalRequest table and service (Delayed until we have a plan for chore repetition)		Review PRs for Chore edit UI and Reward model (Nathan)
Finish docs for proxy providers, example for family ID (Nathan)
Create the Reward provider (Nathan)

Update Reward and RewardRedemption entities (Kylie)
Create RewardRedemption model (Kylie)
Plan approach and design entities for chore repetition (Kylie)
Set up unit tests and mocking examples (Kylie)
Refine and finish the ChoreAssignment model (Kylie)
Integrate ChoreAssignment service into the Chore provider (Kylie)

Create the Reward UI and integrate with providers (Andrew)
Research Supabase authentication (Andrew)
Finish Chore overview screen/list (Andrew)
Plan Person-related aspects of Provider layer (Andrew, Kylie)
Add UI support for chore completion (Andrew)

Update database tables to match updated entities (Ryan)
Implement the ChoreAssignment and Reward services (Ryan)
Create additional database views as needed (Ryan)
Write tests for existing services (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 Lead6.1RiskBoth Flutter and Supabase are unfamiliar technologies to most of our team, 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 Designer6.5
25
Ryan HarperDatabase Developer5.2RiskOur current time estimates do not allow enough time for thorough QA. If we do not adjust our schedule and drop features soon, we risk being late and/or ending up with a low-quality product. Those adjustments will depend on Kylie's unit testing findings.
26
27
28
Issue
29
30
31
Total22.8
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