Template for DTR Memo Project: FitLit Refactor Group Project
Group Member Names: Leigh Larson, Steph Norton, Linus Leas
Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
For Leigh, she would like to get more familiar with tools like SASS and webpack, and writing accessible code. Additionally she would like to gain more experience in terms of working with real world projects. As for Steph, she would like to improve her refactoring skills, and getting familiarized with the new tools as well. Linus's goals are similar in that he would like a deeper understanding in the new technologies being implemented as well as having more experience with general project developement practices.
Leigh is a leader and a hard worker to a fault. Technically, she is good with CSS and HTML and is apt at aquiring and learning new skill sets. Steph is a strong collaborator and team player. She's interested in sharing ideas and giving people space to show new ideas. Linus is an agreeable team player that prefers the group to have a unified goal. Technical strengths are control flow.
Schedule Expectations (When are we available to work together and individually? What constraints do we have? Make sure to discuss the remote questions above in regards to this section):
Steph might plan for about a day off for her birthday but is flexible outside of that as long as there's a balance between the project and other Turing tasks. Leigh would like to get an hour or two of PD in but is otherwise ok with working whenever. Linus is similarly flexible with time but would like at least one day off during the week for mental health upkeep. As a group we would utilize all project work time during school hours with a hard cutoff at nights at about 9pm depending on the status of the project. Additionally, for these longer days, we'll also plan for longer breaks for dinner/errands/additional studying. A 40 on 7 off pom schedule will be utilized
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team? How will we communicate about our emotional and mental well-being with each other?):
We'll communicate mostly through slack and propose bigger decisions while we're talking live to discuss them, any decisions that may affect the project or others work will at least be communicated via slack and not executed unless someone's replied to it. We will communicate our well-being with each other with honesty and empathy and understand that this is a stressful project.
Similar to goals, Linus would like to be more aquainted with project management and tech aquisition. Steph would like to improve her familiarity with the project board on github and everything else. Leigh's agrees with the aforementioned.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
We will utilize github projects and VS Codes Liveshare extension and using Tuple. As far as support goes, we would access our Mentor and Rock resources for times that we are especially stuck. Our cohort would also be a good resource as well when we are especially stuck
We should expect that everyone in the group has the best intention and in turn react with empathy and understanding of how our group members are doing. Feedback is always constructive and not accusatory.
Github Projects
Turn in DTR and project board as deliverables