-
-
Save KevDev90/0bb9e3580e77cfc95ac18187237ece66 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 | |
| |
Group Member Names: Kevin Johnson, Dustin Mikusko | |
| |
What feedback did you get on Dog Party today? What was your biggest takeaway? | |
Dustin- Got the entire project completed with some holes. Do the workflow as it's given to you instead of getting ahead of yourself and adding extra things. | |
Kevin- Format my HTML better, get more used to working with js. Do the work they ask of you in the order they ask you and try not to add to much on your own. | |
Goals and Expectations for the Project (You don't know the details of the project yet. But as you go into any project, how do YOU define success?) | |
Stick to the iteration without deviating too much. Get useful practice and knowledge out of the project. To be able to | |
go back and thoroughly explain what we did in the project. | |
Team strengths & collaboration styles (consider discussing your Pairin qualities here): | |
One collaborative strength is that we're both night owls and both have very flexible schedules. We're both | |
pretty self aware of our strengths, and we like to avoid conflicts so we should work well together. | |
How we can use our strengths to overcome obstacles: | |
By being upfront and honest with each other there shouldn't be too many miscommunications that we'll have to overcome. | |
Schedule Expectations (When are we available to work together and individually? What constraints do we have?): | |
We both are very flexible on our schedules, dustin has meetings with his mentor on tues nights. I have my partner at home | |
but she's very accepting of what i'm doing so that shouldn't be too much opf an issue. | |
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?): | |
Text messages, slack. Do some kind of soft retro on monday, weds, friday. Not being afraid to share ideas, keeping open and honest communication | |
as a regular norm. Sharing positive constructive criticism if need be. | |
Abilities & Growth Expectations (Technical strengths and areas for desired improvement): | |
Semantic HTML, less Divs and more meaningful classes. Dustin- has a good grasp on the js they're expecting of us at this point. | |
Kevin- A couple extra hours of studying JS because I didn't make it to that iteration in the dog party project. | |
Workload Expectations (How are we going to make sure we contribute equally?): | |
Switching off driver and navigator roles regularly, keeping open constant communication. | |
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): | |
We're both realizing the importance of Github and using it in the workplace so we're excited to have extra practice using | |
Git in remote situations. Debugging, break the problem in half and see if your problem is on the front or back half of your code. | |
Expectations for giving and receiving feedback: | |
Giving feedback- Approach everything with honesty and be open to criticism. Receiving feedback- Be open minded, not being | |
too critical of receiving possible negative feedback. | |
Project management tools we will use (GitHub Projects and Trello are popular tools): We're going to try to use the Github projects | |
and google calendar to plan and stay on top of our project. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This looks like a solid DTR, nice work here setting expectations!