FitLit - DTR.md

DTR: Define the Relationship

Project Name: FitLit

Partners: Emily Lalonde and Alyssa Lundgren

Guiding Questions to Define The Relationship:

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

• Manipulating data
• Improve array prototypes
• Git workflow
• Design skill chops
• Testing before implementation
• Score between 2 and 3 on all

Today- layout project, layout design, vision for both desktop and mobile

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

• Enjoy pair programming
• Next three days crucial
• Plan to take 4th off and get back to work on Friday

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

• Slack
• Class
• Pairing

How would you describe your work style?

• Breaks every 45 minutes
• Collaborative
• Mostly paired programming (driver/navigator)

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

• Organized
• Try not to get ahead in the project
• Know when to take a break and walk away and come back fresh later

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

• DTRs
• Paired
• Collaboration

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

• Discussing, collaboration

How will we overcome obstacles?

• Ask for help

What do you need (resources, environment, communication) to do your best work? What scheduling restraints do you have? What are your scheduling preferences? What is your style for giving feedback? Does anything ever hold you back from giving feedback? 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? What tools do you want to use to manage the project? How do you want the group to solve problems when members run into issues with features of the project? How do you know if a project is successful? How can we achieve that as a group? How will we recognize each other's successes and celebrate them? Any additional questions that you would like to add:

Template for DTR Memo Project:

Group Member Names:

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

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

How we can use our strengths to overcome obstacles:

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

• Stay a bit later this week
• Thursday off, Meetup Friday and Saturday, Sunday as an option

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

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

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

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

• Branches
• Pull requests by the other

Expectations for giving and receiving feedback:

Project management tools we will use:

Day 1 Agenda:

• wireframe
• setup project on git
• big picture understanding of the data and files

Additional Notes: