DTR - Night Writer - Nate G. / Joel L.

dtr_night_writer_nate_joel.md

Defining The Relationship

Project: Night Writer (A Journey into Braile Encryption)

Group Member Names:

• Nate Giesing & Joel Lindow

Project Expectations: What does each group member hope to get out of this project?

• Nate

  • To be able to know how to translate one language into another language using code.
  • To gain a stronger understanding of how to build the skeleton of the code before getting deep in the programing.

• Joel:

  • To become stronger in the Ruby language
  • To gain a better understanding of FILE IO

Goals and expectations:

• 20 minutes of "exercises" every day we work together for more than 2 hours
• Good testing
• Clean Conventional Code

Team strengths:

• Desire for good commmunication
• Willing to take time to stop "chasing the finish line" and focus on "areas of growth"

How to overcome obstacles:

• Not be afraid to tell eachother to slow down.
• Timebox discussions and "just try to code" sometimes when we feel stuck
• Never get stuck for more than 20 minutes without asking for help or advice.
• Let fresh eyes look at the project daily at some point

Schedule Expectations (When are we available to work together and individually?):

• Friday Morning 9:00 - 9:45am - Skeleton/PsuedoCode
• Friday After School
• Saturday 8:00am - 12:00pm
• Monday After School
• Tuesday - No After School - Possibly Remote
• Wednesday - After School

Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):

• Slack - Touch base on all updates.

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

• Driver/Navigation share of the load.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests):

Expectations for giving and receiving feedback:

• Talk before it becomes an issue.
• Respect personal time.

Agenda to discuss project launch:

Ideas:

Tools:

Additional Notes: