Skip to content

Instantly share code, notes, and snippets.

@AurumValian
Last active May 26, 2020 18:50
Show Gist options
  • Save AurumValian/054e31270ba1014224ba23cf046c4fff to your computer and use it in GitHub Desktop.
Save AurumValian/054e31270ba1014224ba23cf046c4fff to your computer and use it in GitHub Desktop.

Template for DTR Memo

Project:

Intention Timer

Group Member Names:

Leigh, Estelle, Ben

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?):

Our team plans to complete iteration 3 by the deadline, with roughly equal commits and PRs and a professional README. We want to acquire a deeper understanding of clean code.

Team strengths & collaboration styles (consider discussing your Pairin qualities here):

Leigh: Hard worker and endurance worker, values professionalism, good leader

Ben: Quick learner and guide, good at collaborating and explaining concepts, focused on learning

Estelle: Detail-oriented, able to find the syntax struggle, hard worker

We all have a direct collaboration style, with a blend of driver-navigator and divide-and-conquer strategies.

How we can use our strengths to overcome obstacles:

We'll name problems on the spot, moving forward after gaining clarity on the step we're working on.

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):

From 6:45 to 8:30, we're blocking out time so each of us can have time to themselves.

Tuesday at 5-5:40: Ben's mentor chat

Wednesday from 4-5: Leigh's mentor chat

Wednesday from 5-6:30: Estelle's mentor chat

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?):

Fairly constant communication, through Slack. Transparency about problems coming up, with communication ahead of time. Making decisions as a team means taking everyone's input.

Abilities & Growth Expectations (Technical strengths and areas for desired improvement):

Ben: Good fundamental Javascript, need to work on professionalism and granular commits as well as CSS skills

Leigh: All-around, jack-of-all-trades, wants to keep improving across the board

Estelle: General understanding of all 3 languages, would like to improve and deepen functionality and understanding

Workload Expectations (What features do we each want to work on?):

We all should work on each part. Rough outline for D&C: work and rotate.

Mainly D&C for iteration 0 and 1, transitioning to Driver-Nav.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):

Commits within JS should be a code block (single-function). Refactor commits. HTML and CSS: section commits. Push when completing a bullet-point, not just for iteration blocks.

Pomodoro Break Schedule:

50 minutes on, 10 minutes off.

Expectations for giving and receiving feedback:

Transparency and clarity. Credit where credit's due, specifically in Readme. Coaching and appreciative feedback throughout project.

Additional Remote Considerations:

Overcommunicate.

Project management tools we will use (GitHub projects or Trello are popular tools):

Github projects.

Day 1 Agenda:

-Setup GitHub repo and invite collaborators. -DTR. -Slack channel. -GitHub projects page. -Setup README and HTML skeleton.

Additional Notes:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment