RomCom-DTR.MD

DTR: Define the Relationship

Project: RomCom

Group Member Names:

• Matt Umland
• Nikki Petersen

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

• Finish each iteration with level 3 or above.
• Work towards understanding.
• Assure rubic levels 1-3 are complete for each iteration before moving on to the next.
• Rubric level 4 and any extension are bonus and will be completed only if time allows.

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

• Use timers and/or scheduling to provide time boxes for check ins before escalating with mentors, etc.
• An hour long daily morning meeting to discuss the days plans, goals and roadblocks. This includes some pair programming and plan the days paired programming activities.
• Divy up workload using trello for individual time.
• Be available for check ins periodically throughout the day.

How we can use our strengths to overcome obstacles:

• We face similar obstacles and can use each other for accountability to reach our goal of understanding over accomplishment.
• We have organizational experience and tools to help us stay on track.
• We good :)

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

• 6:00 am MST/8:00 am EST is a regular check in time and can be expanded if we need more time before class.
• A regular post class check in will allow us to schedule additional time in the evening, as needed.
• Mornings are better than evenings.
• No thursday evenings.

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

• See above for regular meeting times.
• Start meetings with a quick feelings check.
• Slack will be used for primary communication. Trello for organization. Tuple for paired programming. Zoom only when necessary.
• Be open with challenges. Be respectful when conflict arise.
• Listen to feedback. Say thank you for it. Use when it appropriate.

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

• Abilities - Comfortable with unknown topics and researching new approaches.
• Growth - Work on using proper terms of art.

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

• See goals and expectations.

Workflow Expectations:

• Use Turing Git Flow.
• When we get stuck - Take a breath, slow down, go line by line.
• Rubber duck.

Pomodoro Break Schedule:

• Pomodoros as needed based on tasks currently being worked on.

Expectations for giving and receiving feedback:

• See Communication Expectations.

Additional Remote Considerations:

• We good :)

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

• Trello

Day 1 Agenda:

• Create a trello board with all of the iterations planned out.
• Clone repo, share repo, independant review in preparation for collaboration during morning meeting.