ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Project NameTogetherlyDate29-Mar to 13-AprProject 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 framework97%Delayed13-Apr-24
4
Authentication system98%Possible Delays13-Apr-24
5
Chore assignment & completion99%Delayed13-Apr-24
6
Reward redemption system93%Delayed13-Apr-24
7
8
9
10
11
12
13
14
15
Tasks CompletedTasks DelayedTasks Planned
16
Write example automated and manual tests for services
Integrate Assignment service into the Chore provider
Design and implement the Person provider
Adding support for redeeming rewards to the Reward provider
Add the ChoreCompletion entity to the ERD
Integrate the ChoreCompletion service into the Chore provider
Set up the authentication back-end
Finish the login page
Integrate the person provider into the parent home page UI
Move changes from demo branch
Finish modifying services to return objects on insert operations
Finish implementing the RewardRedemption service and fix tables
Add icon column to the Reward table
Fix missing column in family_redeemed_reward view
Write tests for the remaining services (waiting on PR review)Review Nathan's PR for service tests (Andrew)
Have the Chore UI get and update assignment status (Andrew)
Integrate reward redemption methods into UI (Andrew)
Finish add/remove child/profile UI (Andrew)
17
18
19
20
21
Team Members -- Billable HoursKey Project Risks and Issues
22
NameRole/TaskHoursTypeRisks or Issue Description
23
Nathan WalkerProject Manager, QA Lead18.7RiskBoth 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.9.5
25
Andrew ThibaudeauUI Designer27.0
26
Ryan HarperDatabase Developer11.0IssueWe 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
Total66.2
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