Last active
December 9, 2020 01:56
-
-
Save stevecalla/f26126a673d32a5c3d89cf4131dd3487 to your computer and use it in GitHub Desktop.
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
Template for DTR Memo | |
Project: Mod1 Paired Project - Rom Com | |
Group Member Names: Matt McVey & Steve Calla | |
Goals and Expectations for the Project (What does each group member hope to get out of this project? | |
- Deeper understanding and learning of javascript. | |
- Solid team dynamics and collaborations. | |
- Score at least a 3 or better for each rubric requirement. | |
- Well balanced contributions from each team member. | |
What do we want to achieve as a team? How will we know that we're successful?): | |
- Hit that 3 or above score with us both understanding the code 100% fully. | |
- Be on time with full submission. | |
- Hold each other accountable in an honest and straightforward manner to get to the finish line. | |
Team strengths & collaboration styles (consider discussing your Pairin qualities here): | |
- Steve's stength is to be sure that group has equal contribution. | |
- Matt's strength is to keep us on track and moving forward and energized to get the job done. | |
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): | |
- At least 2 hours a night between 6-8 with potential of morning sessions before class and project work time allocated by turing as whatevers needed on the weekened. | |
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?): | |
- Constant communication while being respectful and responsive. | |
Abilities & Growth Expectations (Technical strengths and areas for desired improvement): | |
- Steve would like to use this as a way to understand objects, functions and their realationship between them. | |
- Matt would like to solidify my current understanding and hopefully push a bit further. | |
Workload Expectations (What features do we each want to work on?): | |
- Work as a true pair when working through the project so we both get a full understanding of each piece. | |
- Allow for flexibility as we progress through the project. | |
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): | |
- Again, we'll try to pair on most efforts until learning more about our strengths, preferences or other priorities. | |
- Again, we'll be flexible to adjust as possible and necessary to achieve the task at hand. | |
Pomodoro Break Schedule: | |
- Agree to break about every 30 - 45 minutes. | |
Expectations for giving and receiving feedback: | |
- Be open and honest. But be kind, emphathatic, immediate and brief. Agree to move forward. | |
Additional Remote Considerations: | |
- Be respectful of dogs, kids, family needs that may or may not come up. | |
Project management tools we will use (GitHub projects or Trello are popular tools): | |
- Start with a shared google sheet to outline tasks, owner, deadline and other shared information. | |
Day 1 Agenda: | |
- 4:15 to 5: Initial originization and introduction. Complete git clone and other initial tasks. | |
- 6:00p to 8p: Complete Day 1 requirements. | |
- 6:00p to 8p: Plan remainder of work. | |
- 6:00p to 8p: Possibly begin project. | |
- 6:00p to 8p: Decide if there are any pre-Day 1 assignment. | |
Additional Notes: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment