black_thursday_dtr

Guiding Questions to Define The Relationship:
What are your learning goals for this project?
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’s gone well or poorly in your previous projects?
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?

Any additional questions that you would like to add:
















Template for DTR Memo:
DTR Memo
Project: Black Thursday
Group Member Names: Nicholas Jacques, Sergey Lukyanenko
Project Expectations: What does each group member hope to get out of this project? Goals and expectations:
Finish Module 1 Strong
Get all 3s on the assessment
 Application is well tested but does not balance isolation and integration tests, using only the data necessary to test the functionality
Application implements iterations 0, 1, 2, 3, and either 4	
Schedule Expectations: When are we available to work together and individually?
Work in person 90 %
100% committed
Start 8am to discuss the plan for a day
8-9pm to work till, later if needed
Saturday 10am - 4pm
Sunday 10am - 4pm
Communication Expectations: How and often will we communicate? How do we keep lines of communication open?
Check-in every morning
Nicholas 207-239-0379 , Sergey Lukyanenko 646-251-6149
Texting, slack
Abilities Expectations: Technical strengths and areas for desired improvement:
Sergey Strengths: building big picture, good in TDD,
Sergey Weaknesses: typos
Nick Strengths: fast typer, small methods, compartmentalization, TDD
Nick Weaknesses: hashes

Workload Expectations: What features do we each want to work on?
Do iteration 0 together 100%
Workflow Expectations: Git workflow/Tools/Code Review/Reviewing Pull Requests: 
Never merge your own pull request
Set up waffle account today
Expectations for giving and receiving feedback:
Don’t be shy
Agenda to discuss project launch:

Ideas:
 
Tools: 

Additional Notes: