Cop Watch DTR

# DTR: Define the Relationship

One teammate should copy and paste the *raw* markdown into a gist of your own.

### Guiding Questions to Define The Relationship:

* What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
* How do you communicate best? How do you appreciate receiving communication from others?
* How would you describe your work style?
* What are each of our strengths? How can our strengths complement each other?
* What’s gone well or poorly in your previous projects?
* How will we set direction and make decisions as a team?
* 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? Where do you feel you could use improvement in your technical skills? How can our team help support you in improving these skills?
* 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: 2001 Mod 4 Cross Poll Final

Group Member Names: Olivia Webster, Karl Nielsen, David Pernitz, David Tran, Ben Fox

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? YES, you can still fully answer this question without knowing exactly what you're going to build.):
Dave P: Learning a new technology or Framework, hitting base MVP, learn, have a good experience, put something out there that's useful
Ben: Feeling like he gets Python. Making something useful and have a good user experience. 
David T: Wants to see a more seamless interaction between FE and BE, functional and presentable enough that it can go to code fair and maybe demo comp. 
Olivia: Get a good understanding of hooks and react native if we use it. Well tested front end. Maintain good communication the entire project.
Karl: a project we end up proud of, good user experience, maybe get into demo comp, getting familiar with react native and building for mobile


Team strengths & collaboration styles (consider discussing your Pairin qualities here):
Dave P: collab: pairing early on and a mix. if stuck sometimes needs space. strength: flexible and happy to put in the work 
Ben: collab: pairing for getting on the same page and then divide and conquer strengths: meticulous, detail oriented.
David T: collab: pair on whatever needs to get paired on, fine with D and C strengths: enjoys explaining things, detail oriented, good at problem solving
Olivia: collab: mix of pairing and D&C strengths: patient, flexible
Karl: collab: when new tech likes to pair. likes pairing with equal driving and navigating. also happy to split things up. strengths: flexible
and takes feedback well, pivots easily, attention to detail, pom master, clear communication

How we can use our strengths to overcome obstacles:
we're all pretty flexible and open to assist. Daily regular communication. Regular whole group meetings. 

What do you need to look out for, in terms of strengths/working styles coming into conflict?
Making sure BE and FE communicate regularly and explain to each other what's going on. 
Be open to ideas, provide learning sources in resources thread. 
 

Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
Dave P: mornings for PD, prefers project work be afternoons and evenings, hour or so for dinner, not too late, but also flexible
depending on what needs to be done. 
Ben: daily done by 9pm, likes to take one day a week preferably sunday. group calendar. 
David T: pretty flexible, not uncommon to be up late, maybe sunday off
Olivia: I like to be done by 9 or 10 but if it's an emergency i can stay up late, i like to take a lunch and dinner, half day on weekends
Karl: Tuesdays in the evening will need a couple hours. gone 1st friday afternoon-sunday morning, open to work by 9pm. 


What is the one hour/day that each teammate has on their calendar for personal study/practice time?
morning before class.
None of us want to get too bogged down in the project so that we can do networking. 
generally keep lunches open. 


Expectations for giving and receiving feedback:

Dave P: honest, direct, but kind, assume positive intent
Ben: assume positive intent, be kind and honest. assume no one is trying to screw up and not care, be honest about issues.
David T: give it to him straight. but be nice
Olivia: direct but kind, actionable. Regular communication. 
Karl: clear, actionable, kind