Skip to content

Instantly share code, notes, and snippets.

@trishalanglois
Last active September 3, 2019 21:40
Show Gist options
  • Save trishalanglois/7fef0fccf74b2566762ced84b688d367 to your computer and use it in GitHub Desktop.
Save trishalanglois/7fef0fccf74b2566762ced84b688d367 to your computer and use it in GitHub Desktop.

DTR Memo

Project: Idea Box

Group Member Names: Trond Makonese, Kayla Wood, Trisha Langlois

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

Trond -- to become better at JS (even more!). How to learn new JS and implementation if it. Kayla -- to limit amount that we have to edit our HTML. Trisha -- DRY in JS. Find ways to incorporate parameters instead of rewriting the same functions over and over.

We'll know we're successful if each of us understands the code. The learning is the goal rather than having a a perfect-looking and/or fully-functioning, Phase 4 project. We also want to meet the group's goals for how far we want to get that we set on day 1.

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

We like pair programming but also feels comfortable stepping away and doing stuff on our own. Driver/Navigator is not sustainable to do for every step of the project. When the functionality is complex, or our understanding isn't there, this will be helpful, but we shouldn't solely do it.

Trond - works well in groups and on his own. Prefers listening to music while working. Kayla - works well in quiet or noisy places. Prefers to go home if it's something she can do the work at home. As long as we're doing collaborative work, though, she's cool with staying at school. Trisha - likes to work at school but isn't expecting anyone else to stay too.

Personal Strengths: Trond - easy-going and relaxed. Doesn't like to feel stressed if there's nothing to really be stressed about. We all have the perspective that this is hard and time-consuming, and how we do on this project is not indicative of our self-worth and value. Trisha - organized and deadline-oriented. Can see where we are in the grander scheme of our goals. Kayla - reliable and will be communicative.

How we can use our strengths to overcome obstacles:

In our conversations, we'll incorporate honesty and knowing it's fine and normal to not know how to do something. We're all learning.
Daily check-ins that include wins we've had and obstacles we're experiencing. If other members of the group are able to help, great, but if not, reach out to other resources -- rocks, mentors.

Use Driver/Navigator when appropriate. Don't push code if it doesn't work. Being honest and open when you need help, figuring out if the group can help.

Schedule Expectations (When are we available to work together and individually? What constraints do we have?):

Kayla leaving at 5 on Tuesday, Trisha leaving after class on Thursday. Otherwise, we're all available. For working together, before or after class is fine, knowing that there might be 1-2 nights where we're here late.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):

Daily meetings that include what we're trying to do. Set big goals initially and follow up daily. Writing HTML and stories together so we're all on the same page.

Appreciate direct communication. Don't be passive because it will lead to further being passive from other group members. Slack works well for communication. See each other daily -- daily check ins when we get here - what went well, what did you accomplish, what are next steps?

Give positive feedback to one another throughout the project. Celebrate ourselves and share those wins with one another. Don't be afraid to brag about what you've done and what wins you had!

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

Trond - sees details and can find errors. Wants to get better at JS. Kayla - comfortable with CSS and understands JS concepts relatively quickly and easily. Wants to get better at initial wireframing and setting up HTML the best way. Trisha - classes and ids in HTML and looking for patterns so styling is more straightforward. Wants to get better at DRY JS and semantic HTML.

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

We're going to use GitHub Projects to divde the tasks on the project. We'll be checking in daily to figure out what each person is going to work on.

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

Pay attention to how often we're committing and making sure we're in line with one another. Commit as often as possible. Mark tasks as done in GitHub Projects, which will feed into an overall done section.

Expectations for giving and receiving feedback:

Giving direct feedback about the code (not the person). If there is personal feedback, keeping it kind and doing it in private.

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

GitHub projects.

Day 1 Agenda:

Get project, wireframe together, setting up GitHub projects, make repos and clone it, maybe do HTML today (or tomorrow morning).

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