Created
April 13, 2021 02:25
-
-
Save Andrey-1992/2e8c07a270e2276a0d4995fc40f1e5f1 to your computer and use it in GitHub Desktop.
DTR - Intention-Timer (Group Project)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Project: Intention Timer | |
Group Member Names: Andrey, Lauren, and Jani | |
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?): | |
Andrey - goal is to understand the workflow, how to start from zero | |
Lauren - super cool app! | |
Jani - Data Model and DOM Interaction, global variables, etc. | |
We want to achieve good time management, and not killing each other - enjoy coding together! | |
Team strengths & collaboration styles (consider discussing your Pairin qualities here): | |
We’re all cool calm and collected. Lauren and Andrey are logical and methodical. Jani is organized and has “blaze”. Andrey is open minded, and shows empathy to include others. | |
How we can use our strengths to overcome obstacles: | |
We’ll be cool during obstacles, and Lauren and Andrey’s logical skills will benefit us doing research. | |
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): | |
Lauren is in eastern time. 2+ hours ahead of Andrey, and 1+ hour ahead of Jani. | |
Lauren typically works no later than 10PM eastern (7pm for Jani, 8pm Andrey). | |
Jani is up at 6am (9am for Lauren, 7am for Andrey) | |
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?): | |
Daily check-ins on each other’s sanity and work pace - so we know when to take breaks or fill each other in later. | |
Make the most of our scheduled project time during class. | |
Tuesday 4/13 1-4 PM MST | |
Wednesday 4/14 2-4PM MST | |
Thursday 4/15 1-4 PM MST | |
Friday 4/16 2-4 PM MST | |
Monday 4/19 1-4 PM MST | |
All other times are TBD, through the weekend. | |
Jani - has dinner with the fam every night. | |
Andrey - weekly check ins with his mentor. (Friday 3-3:30 full) | |
Lauren - Wednesday evening’s mentor meeting 5PM MST. | |
Abilities & Growth Expectations (Technical strengths and areas for desired improvement): | |
Andrey - pretty good at vocab, learn more about CSS, and organizing HTML | |
Lauren - pretty solid at JS, want to learn more about local storage, improve CSS skills | |
Jani - refactoring and syntax, git flow - also want to learn local storage and functions | |
Workload Expectations (What features do we each want to work on?): | |
We all want experience with working on local storage. | |
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): | |
Pull Request Template used for each pull | |
Frequent branches for each change/feature | |
Detailed ReadMe | |
Pomodoro Break Schedule: | |
Take a break if one of the 3 of us is feeling like a zombie. | |
At least once an hour - use chrome extension timer | |
Expectations for giving and receiving feedback: | |
Be kind with your words, be actionable and specific. | |
Additional Remote Considerations: | |
Zoom - remote control | |
Project management tools we will use (GitHub projects or Trello are popular tools): | |
Regularly referencing the project spec - https://frontend.turing.io/projects/module-1/intention-timer-group.html | |
Chrome Extension, highlight what we’ve completed on the project spec. | |
Day 1 Agenda: | |
Setup Repo | |
Additional Notes: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment