Last active
May 12, 2020 23:27
-
-
Save jordy1611/bc62c84f0efe03eb9d74c41dfe354f14 to your computer and use it in GitHub Desktop.
This file contains 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
DTR: Define the Relationship | |
Project: RomCom | |
Group Member Names: Jordy Shryock & Leigh Larson | |
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?): | |
Confidence with javascript so that projects seem less daunting initially. Create and nurture positive working relationship with partner. Give each other opportunities to grow. Demonstrate javascript development, professionalism and teamwork. | |
Team strengths & collaboration styles (consider discussing your Pairin qualities here): | |
Emphasis on psuedo code and planning prevents mistakes and saves time. Both able to self teach and learn on the fly. Abilitiy to analyze goals of project to create effecient project outline. | |
How we can use our strengths to overcome obstacles: | |
Ability to self teach brings multiple perspectives to overcoming each obstacle. Psuedo code and planning reduces likelihood of mistakes down the road and keeps project organized. | |
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): | |
Wed & Thurs: After 6:00pm. Friday: Start anytime after class. Saturday & Sunday: Plan a couple hours ahead of time to sit down. | |
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?): | |
Constantly use slack. We'll be using driver/navigator so communication will constantly while working. If you need a break, take a break (no questions asked). Plan hourly breaks. | |
Abilities & Growth Expectations (Technical strengths and areas for desired improvement): | |
Want to work on relationship skills and creating a growth environment for others. Improve organization and convention styles. Improve ability to work on technical tasks with others without taking over the room and allow others opportunity to work. | |
Workload Expectations (What features do we each want to work on?): | |
Split driving as evenly as possible. Give each partner and opportunity to tackle problem and step back to analyze problem. | |
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): | |
Pull request everytime to master branch. Pull request for each step solved. Non puller approves pull request. Take time to leave at least 1 comment on each pull request. | |
Get project passing and functioning initially then return to sections to DRY and impliment SRP. | |
Pomodoro Break Schedule: | |
60 minutes w/ 10 minute break, if skipped or deep into project ~90 minutes. Whenever comes naturally. | |
Expectations for giving and receiving feedback: | |
Bluntness is appreciated, while staying polite. Speak up but also give someone the opportunity to learn. | |
Additional Remote Considerations: | |
Project management tools we will use (GitHub projects or Trello are popular tools): | |
GitHub projects | |
Slack | |
Atom text editor | |
MDN | |
Module 1 Lesson Plans | |
Day 1 Agenda: | |
Overall project setup | |
DTR | |
Strategy | |
README Day 1 | |
PR | |
Additional Notes: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment