Skip to content

Instantly share code, notes, and snippets.

@benjamin-firth

benjamin-firth/rancid-tomatillo-dtr.md

Last active December 16, 2019 23:33
Show Gist options
  • Save benjamin-firth/f255e3c0e664869894f3db705214c0da to your computer and use it in GitHub Desktop.
Save benjamin-firth/f255e3c0e664869894f3db705214c0da to your computer and use it in GitHub Desktop.
Download ZIP
DTR for Rancid Tomatillos Mod 3 Group Project
Raw
rancid-tomatillo-dtr.md

Project: Rancid Tomatillos / Hate It N' Rate It

Group Member Names: Consuelo, Roger, and Ben

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

  • Consuelo: Getting better at Redux and testing.
  • Ben: Getting better at testing, learning Redux, and improving styling.
  • Roger: “Git gud with redux.”

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

  • Consuelo: Good experiences with divide and conquer.
  • Ben: I have more experience with divide and conquer, but like pair programming. Get together during key parts of project.

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

  • Consuelo: In person or through Slack.
  • Ben: In person or Slack, feel free to text but no guarantees.
  • Roger: I communicate best by just being straight forward and direct.

How would you describe your work style?

  • Consuelo: Divide and conquer.
  • Ben: I am very dedicated to project specs and working through each one.
  • Roger: My work style is adaptable.

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

  • Consuelo: Background knowledge from repeating, css, communication, stick to assigned iterations.
  • Ben: Organization, decent with fetching.

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

  • Consuelo: Well: Remotely, communication. Not so well: Communication, especially over the weekends with PRs.
  • Ben: Well: Communication. As long as team members stick to assigned tasks everything should get finished.

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

  • Consuelo: Talking, keeping communication open. If problems arise that aren't being solved, contact project manager.
  • Ben: Talking, referring back to project spec, and our individual learning goals as a motivator.

How will we overcome obstacles?

  • Consuelo: Work together.
  • Ben: If have issues that we can't solve individually, working together to figure them out might help.

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

  • Consuelo: Space, largely remote, but maybe at Turing when not.
  • Ben: I can't work in coffee shops. Turing works best when not remote.

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

  • Consuelo: Leave this Friday the 20th after school. Holidays.
  • Ben: I leave Saturday the 21st. Back the 29th. Happy to work a bit over the Holidays. Make a schedule for everyone so that we don't end up behind after.
  • Roger: Have to leave by 5:30.

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

  • Consuelo: Tell people.
  • Ben: Tell people, probably more passively than I think.

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

  • Consuelo: GitHub Projects
  • Ben: GitHub Projects

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

  • Consuelo: Get together.
  • Ben: Get together.

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

  • Consuelo: No errors, passing tests, complete functionality for what we have.
  • Ben: Improving on my learning goals, no errors.

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

  • Consuelo: Keeping to your issues.
  • Ben: I'll give hi-fives.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment