TonyR-KeelianaM DTR

uiding Questions to Define The Relationship:
====

* **What are your learning goals for this project? What drives us in this project?**
  - Perfect JavaScript. Utilize jQuery. Learn activate .class
* **What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?**
  - Diver/Navigator with divide and conqure. Meetup to merge progress.
* **How do you communicate best? How do you appreciate receiving communication from others?**
  - Slack. Open communication. 
* **How would you describe your work style?**
  - Perfer independant but open to to collab.
* **What are your strengths? How can our strengths complement each other?**
  - Keeliana: Good at coming up with ideas. | Tony: Self motivation.
* **What’s gone well or poorly in your previous projects?**
  - No planning. Lack of communication.
* **How will we set direction and make decisions as a team?**
  - Break down the project into messurable goals. Then assign those goals when we divide and conquer.
* **How will we overcome obstacles?**
  - When driver/nav it will be easy to overcome. When divide and conqure a mix self-research for 30min and then slack call partner for help.
* **What do you need (resources, environment, communication) to do your best work?**
  - Pairing resource with mentors. Low distraction enviorment. Good communication.
* **What scheduling restraints do you have? What are your scheduling preferences?**
  - No restraints besides public transport during weekdays.
* **What is your style for giving feedback? Does anything ever hold you back from giving feedback?**
  - Direct respectful honest communication. No.
* **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?**
  - Keeliana: HTML/CSS learning JS and jQuery. | Tony: Well rounded but need to learn jQuery.
* **What tools do you want to use to manage the project?**
  - Slack. Notes checklist.
* **How do you want the group to solve problems when members run into issues with features of the project?**
Group research or self research with Pairing.
* **How do you know if a project is successful? How can we achieve that as a group?**
  - Presenting a functional end product and learning from the experience.
* **How will we recognize each other's successes and celebrate them?**
  - Overcoming new challenges or obsticles and learning new methods of programing.

Any additional questions that you would like to add:






### Template for DTR Memo

Project: 
Linked List

Group Member Names: 
Keeliana & Tony

**Project Expectations: What does each group member hope to get out of this project?** 
 - Getting better at JavaScript and learning jQuery. Also learning how to pair program successfully.
 
**Goals and expectations:**
- Get through Phase 3 expectations and hopefully Phase 4 completion.
	
**Team strengths:**
- Keeliana: HTML/CSS learning JS and jQuery
- Tony: Well rounded but need to learn jQuery

**How to overcome obstacles:**
- Group research or self research with Pairing.

**Schedule Expectations (When are we available to work together and individually?):**
- Weekdays: 4pm-7pm
- Weekend: 9am-Open

**Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):**
- Very open with use of Slack

**Abilities Expectations (Technical strengths and areas for desired improvement):**
- Keelina:
* HTML: Advance Beginner to Proficient
* CSS: Advance Beginner to Proficient
* JavaScript: Novice to Advanced Beginner
* jQuery: Beinner

- Tony:
* HTML: Proficient
* CSS: Proficient
* JavaScript: Proficient
* jQuery: Beinner

**Workload Expectations (What features do we each want to work on?):** 
- Even workload with features. Possible JavaScript balance more towards Tony if needed.

**Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests):** 
- Git Pull requests will be done in person together. We'll scheduel pairing with MOD2/3 at least twice before turn-in.

**Expectations for giving and receiving feedback:**
- Super open communication and feedback.