ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Project NameTogetherlyDate15-Mar to 21-MarProject ManagerNathan Walker
2
Project Summary (including redirection)Key TasksProgress*StatusFinish
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 & completion96%Delayed25-Mar-24
5
Family system (chore overview, person UI)58%Delayed25-Mar-24
6
Reward store (read-only)96%Delayed25-Mar-24
7
Chore repetition system0%Future Task06-Apr-24
8
Family system (person BL, editing)15%On Track30-Mar-24
9
Rewards editing0%Future Task01-Apr-24
10
Chore completion & approval system0%Future Task12-Apr-24
11
Reward redemption system39%On Track08-Apr-24
12
Authentication system32%On Track09-Apr-24
13
Webapp deployment0%Future Task11-Apr-24
14
Testing framework60%Possible Delays25-Mar-24
15
Tasks CompletedTasks DelayedTasks Planned
16
Review PRs for Chore edit UI and Reward model
Finish docs for proxy providers, example for family ID
Create the Reward provider
Update Reward and RewardRedemption entities
Plan approach and design entities for chore repetition (completed during team meeting)
Refine and finish the ChoreAssignment model
Research Supabase authentication
Update database tables to match updated entities
Implement the ChoreAssignment service
Create additional database views as needed		Create RewardRedemption model (waiting for PR review).
Set up unit tests and mocking examples (still working on service tests, waiting for partial PR review)
Integrate ChoreAssignment service into the Chore provider (did not get to it)
Create the Reward UI and integrate with providers (waiting for PR review)
Finish Chore overview screen/list (still waiting for more providers and services)
Plan Person-related aspects of Provider layer (was blocked until recently, will take simpler approach)
Add UI support for chore completion (waiting for provider support)
Implement the Reward service (mostly done, but needs some changes and a PR review)
Write tests for existing services (still waiting on testing framework)		Update team deliverables (Nathan)
Review RewardRedemption model PR (Nathan)
Review unit testing PR (Nathan)
Review Reward UI PR (Nathan)
Review Reward service PR (Nathan)
Figure out a way to create a constraint in Postgres (Nathan, Ryan)

Update Chore and Reward models/services to support new family ID fields (Kylie, Ryan)
Integrate Assignment service into the Chore provider (Kylie)
Submit separate PRs for unit testing, RewardRedemption model (Kylie)
Implement the Person provider (Kylie)
Figure out how to write unit tests for the service layer (Kylie, Ryan)
Add ChoreCompletion entity to ERD, update Chore and Person entities (Kylie)
Create ChoreCompletion model (Kylie)

Finish Chore overview list (Andrew)
Add UI support for chore completion (Andrew)
Create stubbed methods for Person provider (Andrew)
Finish family/person overview list (Andrew)
Add UI support for adding/removing children (Andrew)
Start setting up authentication backend in Supabase (Andrew)

Update services to return resulting object on insert (Ryan)
Finish up the Reward service (Ryan)
Create the RewardRedemption service (Ryan)
Create ChoreCompletion table (Ryan)
17
18
19
20
21
Team Members -- Billable HoursKey Project Risks and Issues
22
NameRole/TaskHoursTypeRisks or Issue Description
23
Nathan WalkerProject Manager, QA Lead5.8RiskBoth 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.
24
Kylie CallawayChief Architect, Library & Config. Manager, Front-end Business Logic Dev.6.0
25
Andrew ThibaudeauUI Designer14.0
26
Ryan HarperDatabase Developer5.1RiskOur 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.
27
28
29
Issue
30
31
32
Total30.9
33
34
*These progress percentages represent the most recent values as of the time this status report was prepared (3/23).
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