ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Project NameTogetherlyDate16-Feb to 22-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 diagram40%On Track11-Mar-24
4
Page routing system0%Delayed29-Feb-24
5
App logo50%Delayed29-Feb-24
6
Child home - UI90%Possible Delays29-Feb-24
7
Child home - Business logic50%Possible Delays29-Feb-24
8
Child home - Database50%Possible Delays29-Feb-24
9
Parent home (UI, business logic, and DB)5%Future Task12-Mar-24
10
Rewards page (UI, BL, and DB)0%Future Task20-Mar-24
11
Chore approval (UI, BL, and DB)0%Future Task04-Apr-24
12
Logic/registration page (UI, BL, and DB)0%Future Task08-Apr-24
13
Settings page (UI and BL)0%Future Task10-Apr-24
14
Tasks CompletedTasks DelayedTasks Planned
15
Set up provider system
Update project wiki with Asana project, Gantt chart, PERT chart
AssignedTo, and Person entities
Create set of profile pictures
Stub out methods for Chore service
UI mockups of chore editing dialogues, chore overview list		Entity relationship diagram (will be created incrementally)
Set up page routing system (did not get to it this week)
Navigation bar (will be developed as pages are added)
Design more possible logos (did not get to it this week)
Design and implement Chore provider (Kylie/Andrew)
Further refine Chore entity design (Kylie)
Create/update Chore and Person models (Kylie)
Create/update Chore and Person tables (Ryan)
Create ChoreAssignment/AssignedTo table (Ryan)
Research implementations of repeating tasks (Kylie)
Start work on entities and models for Reward, etc. (Kylie)
Set up page routing system (Andrew)
Design more possible logos (Andrew)
Integrate Chore provider into the Chore UI (Andrew)
Implement Chore service (Andrew)
Find/create a Git cheatsheet for the team (Nathan)
Figure out high-level entities to include in arch/design docs (Nathan/Kylie)
Create and post team architecture and design documents (Nathan)
16
17
18
19
20
Team Members -- Billable HoursKey Project Risks and Issues
21
NameRole/TaskHoursTypeRisks or Issue Description
22
Nathan WalkerProject Manager, QA Lead14.8RiskFlutter 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.7.7
24
Andrew ThibaudeauUI Designer12.0
25
Ryan HarperDatabase Developer6.0RiskSupabase is based on Postgres, which a new SQL dialect for our database developer.
26
27
28
29
30
31
Total40.5
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