Template for DTR Memo Group Member Names: Heather Faerber and Scott Ertmer
What feedback did you get on Dog Party today? What was your biggest takeaway? Heather- feedback: some minor syntax tweaks. Biggest takeaway: Get help sooner, get more comfortable with css layout. Scott- feedback: ditto with syntax and some formatting tweaks. Biggest takeaway: No time to waste. Front-load the work as much as possible. MVP: minimum viable product.
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?) Heather & Scott's definition of success: Recognize when we've met the MVP and stop tweaking and then we move onto the next iteration. Iteration by iteration progress. Being able to confidently explain the code = success. Progress > perfection.
Team strengths & collaboration styles (consider discussing your Pairin qualities here): Heather is objective/analytical which she thinks could be an obstacle, becasue she wants it to be black and white, when really there are many ways to accomplish a task. Scott is intuitive/conceptual and finding patterns could be helpful. Our teams strengths are: putting the relationship first, self care. Both empathatic. We both commit to dealing with issues directly.
How we can use our strengths to overcome obstacles: By being direct when issues arrive, valuing our relationship. When either of us feel anxious, we can give support without it feeling like telling the other what to do or how to feel.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?): Both morning people. Both flexible when it comes to getting it done. Prefer sundays for deep dives over saturdays, but still flexible. Hard Stop at least by 9pm.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?): In person preferred. Slack preferred, phone call if you really need an important issue resolved. How we make decisions as a team? Literally asking "Are you good with this decision?" before moving on. No coding until we can both articulate. OK to take time to solidify the concept. Stay in communication about commits.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement): Heather: Glow = Github, matching comp and style guides. Growth = Css layout and flexbox. Scott: Glow = Semantic HTML, matching style guides. Grow = Javascript and dom/scope concepts.
Workload Expectations (How are we going to make sure we contribute equally?): check in with git commit #'s, Driver/navigator mostly. Stick to poms to help us stay on track for specific tasks (+ or 1 10), and check in with commits.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): Check back in on this as workflow gets better defined. Trello for managment. Rubber Ducking, Self awareness regarding when to break.
Expectations for giving and receiving feedback: Direct Feedback with supportive language and HELLA HIGH FIVES!
Project management tools we will use (GitHub Projects and Trello are popular tools): Trello.
I appreciate how thorough you were here, nice job!