ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Project NameTogetherlyDate22-Mar to 28-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.Testing framework19%Delayed10-Apr-24
4
Authentication system35%On Track13-Apr-24
5
Family system (back-end, BL)67%Delayed03-Apr-24
6
Chore assignment & completion40%Delayed13-Apr-24
7
Family overview (people/chores, parent home page)80%Delayed11-Apr-24
8
Reward redemption system60%On Track10-Apr-24
9
10
11
12
13
14
15
Tasks CompletedTasks DelayedTasks Planned
16
Update team deliverables
Review RewardRedemption model, Reward service, Reward UI, and unit testing PRs
Figure out a way to create a constraint in Postgres
Update Chore and Reward services to support new family ID fields
Submit separate PRs for unit testing, RewardRedemption model
Start setting up authentication backend in Supabase
Finish up the Reward service		Integrate Assignment service into the Chore provider (in progress)
Implement the Person provider (stubs were not yet written)
Figure out how to write unit tests for the service layer (ran into complications)
Add ChoreCompletion entity to ERD, update Chore and Person entities (did not get to it)
Create ChoreCompletion model (did not get to it)
Finish Chore overview list (waiting on provider layer)
Add UI support for chore completion (fake behavior was in place for demo, now waiting on provider layer)
Create stubbed methods for Person provider (Andrew had limited hours this week)
Finish family/person overview list (waiting on provider layer)
Add UI support for adding/removing children (Andrew had limited hours this week)
Update services to return resulting object on insert (ran into challenges with Supabase API, but should be ready soon)
Create the RewardRedemption service (mostly finished, but ran into ambiguity in ERD)
Create ChoreCompletion table (waiting on ERD update)		Update tasks (Nathan)
Write example automated and manual tests for services (Nathan)
Integrate Assignment service into the Chore provider (Nathan)
Review PRs (Nathan)

Respond to PR feedback (Kylie)
Meet with Nathan early in the week to discuss mocking in unit tests (Kylie)
Implement the Person provider (Kylie)
Start adding support for redeeming rewards to the Reward provider (Kylie)
Add the ChoreCompletion entity to the ERD (Kylie)

Create stubbed methods for the Person provider (Andrew)
Continue setting up the authentication back-end (Andrew)
Continue working on the login page (Andrew)
Integrate the person provider into the parent home page UI (Andrew)
Move changes from demo branch (Andrew)

Finish modifying services to return objects on insert operations (Ryan)
Finish implementing the RewardRedemption service and fix tables (Ryan)
Once example tests have been written for services: Write tests for the remaining services (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.9RiskBoth 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.4.0
25
Andrew ThibaudeauUI Designer3.0
26
Ryan HarperDatabase Developer3.7IssueWe have so far put off unit testing due to our lack of knowledge on how to accomplish it with the language and framework we are using. We need to change this soon if we hope to meaningfully follow the automated testing portion of our QA plan.
27
28
29
Issue
30
31
32
Total16.6
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