Created
October 29, 2017 00:37
-
-
Save cbdallavalle/77a247a6e93cb5234f9a7f188ac5b279 to your computer and use it in GitHub Desktop.
Edgar & Casey DTR
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
Project: Linked List | |
Group Member Names: Edgar and Casey | |
Project Expectations: What does each group member hope to get out of this project? | |
-Edgar: solidify jQuery, learn responsiveness | |
-Casey: be introduced to jQuery, work on CSS, learn responsiveness | |
Goals and expectations: | |
-Finish phase 3 | |
-Split the work in half | |
-Over weekend finish phase 1 | |
Team strengths: | |
-Know each other’s strengths finders | |
-Edgar: good at commanding and finding individual’s strengths | |
-Casey: can learn quickly | |
-Casey and Edgar: can take charge when the need arises | |
How to overcome obstacles: | |
-We have different strengths so identify them when obstacles come up | |
-Capitalize on the urge to get things done quickly | |
-Come to each other with problems | |
Schedule Expectations (When are we available to work together and individually?): | |
-Figure out screen hero | |
-Work in the mornings and during the day | |
-Friday Casey will start learning about jQuery, Saturday we are meeting at 7:30am for several hours, Sunday all day coding session at 7:30am. | |
Communication Expectations (How and often will we communicate? How do we keep lines of communication open?): | |
-Daily 2-5 times | |
-When struggling with a problem, set up a 30min timer to work on the issues. When the time runs out, reach out to partner. | |
-Pairing together with mod2. Monday & Tuesday lunch pairs established. | |
Abilities Expectations (Technical strengths and areas for desired improvement): | |
-Edgar: jQuery | |
-Casey: Vanilla Javascript | |
Workload Expectations (What features do we each want to work on?): | |
-Workload around 50/50 | |
-We are a little unsure of how the project will naturally be split up. Since this is our first time doing a pairing project, we are going to revisit this once we have a wider understanding of our project. | |
-We did a lot of driving/navigating the first day, and it was slow-going. Next time, lets split up specific tasks that are connected for more kinetic workflow (stay in CSS together, or javascript, etc.) | |
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests): | |
-Use GitHub to share work, we tried and will ask for help | |
-Letting each other know when we have completed steps | |
Expectations for giving and receiving feedback: | |
-Try to do through Git, slack as default | |
-Positive and constructive criticism | |
-How to address a problem with code: | |
-Complimentary comment | |
-Address the problem with honesty and in a constructive tone | |
-Add ideas on how to fix the issue | |
-Motivational comment | |
Agenda to discuss project launch: | |
-We planned a quick agenda in the schedule category | |
-We are planning get together times as we go | |
Ideas: | |
-Have each other’s backs | |
-Group pairing | |
-Check ins 2 times a day | |
Tools: | |
-Javascript & jQuery book, pairings, cross-pairings, mentors and staff | |
Additional Notes: | |
-Have fun and DANCE! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment