Skip to content

Instantly share code, notes, and snippets.

@edwindelbosque
Created August 19, 2019 20:39
Show Gist options
  • Save edwindelbosque/dc8d22859da37d732b556180333bc962 to your computer and use it in GitHub Desktop.
Save edwindelbosque/dc8d22859da37d732b556180333bc962 to your computer and use it in GitHub Desktop.
DTR FitLit (Edwin & Vanessa)

DTR: Define the Relationship

Vanessa & Edwin

Guiding Questions to Define The Relationship:

What are each of our learning goals for this project? What drives us in this project?

  • Learn the files talk to each other.
  • Getting to be better at handling array.prototypes and methods.
  • Learn to manipulate data more efficiently.
  • Learn to design the UI/UX of a working application.
  • Be more efficient when writing a robust TDD.

What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?

  • a hybrid of both, begin with mostly pair programming, and maybe start to branch out a bit more later on.

How do you communicate best? How do you appreciate receiving communication from others?

  • Just open communication, honesty, consistency.
  • Difficult conversations if necessary.

How would you describe your work style?

  • Work at Turing most of the time.
  • Maybe work some weekends at Turing, or bar, etc.
  • Edwin works best for long period of time (to get in the zone).
  • Quiet, lyric-less music, calm environment
  • Nothing broken goes on master branch.

What are each of our strengths? How can our strengths complement each other?

  • Edwin is good with CSS.
  • Vanessa is good with looking at the big picture.

What’s gone well or poorly in your previous projects?

bad

  • Passive aggressiveness.
  • Getting left behind.
  • Not sticking to DTR, or plans. good
  • Planning aspect is VERY helpful. a roadmap.
  • When working together we can find solutions faster.

How will we set direction and make decisions as a team?

  • Have a conversation about the goals for the day.
  • Wrap up conversation at the end to celebrate wins (and struggles)
  • Talk about plans for the next day / expectations.

How will we overcome obstacles?

  • Communication is important.
  • Best intent.
  • A good balance when reaching for help, not too soon, not too late.
  • Working together to have another pair of eyes.

What do you need (resources, environment, communication) to do your best work?

  • Don't throw each other down the bus.
  • Calm environment (Turing, etc.)
  • Understand each other, be empathetic.

What scheduling restraints do you have? What are your scheduling preferences?

Vanesaa: Meetings with Jun on Thursday 08/22 4pm, Monday 08/26 4pm. Edwin: No limitations.

No working over lunch. No paired working in the mornings.

What is your style for giving feedback? Does anything ever hold you back from giving feedback?

  • Confront if uncomfortable, but always with best intentions.
  • SPEAK UP.

What do you identify as being your biggest strength(s) technically, as they relate to this project? Where do you feel you could use improvement in your technical skills, as they relate to this project? How can our team help support you in improving these skills?

Strengths: Vanessa: refactoring. Edwin: debugging.

  • Get better at not getting overwhelmed with projects.
  • Getting better at JavaScript.
  • TDD and object/data manipulation.

What tools do you want to use to manage the project?

  • GitHub Project.
  • Design Tool like InVision or Figma for UI.
  • VSCode.

How do you want the group to solve problems when members run into issues with features of the project?

  • Communicate them.
  • Address pros and cons.
  • Have a suggestions to make it better.

How do you know if a project is successful? How can we achieve that as a group?

  • If we are proud.
  • If teamwork works.
  • If we get to make every iteration as clean and flawless.mp3 as possible.
  • If I want to show it to other people.

How will we recognize each other's successes and celebrate them?

  • Drinking
  • High-fives
  • Show gratitude & appreciation for what we have accomplished in every step of the process.
  • Focus on achievements and learnings after struggling. Don't focus on the bad stuff.
  • Positive self-talk.

Template for DTR Memo

Project: FitLit.

Group Member Names: Vanessa Randall & Edwin Del Bosque

Day 1 Agenda: Plan and wireframe. Walk though iteration one, set up all the files, set the repo, set gitHub Project.

Additional Notes: Functionality is the priority, at least in the beginning.

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