Created
June 26, 2017 20:25
-
-
Save ciarabujanos/8f296829e2ec8f233b4b29517b8acb44 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| DTR Memo | |
| Project: HeadCount 2.0 | |
| Group Member Names: | |
| Ciara Bujanos | |
| Travis Gregory | |
| Project Expectations: | |
| Ciara: Get react fundamentals down pat and get more comfortable with api calls using fetch, passing data with props. Better grasp of which | |
| components should be state vs stateless. | |
| Travis: Solidify knowledge of react/api calls and testing. | |
| Goals and expectations: | |
| Get through phase 3 by wednesday and done with proj by thursday evening if possible! | |
| Use waffle to keep organized | |
| Team strengths: | |
| Ciara: Strength in HTML & CSS, breaking down problems into smaller parts, communication, js fundamentals. | |
| Travis: Communication, collaboration, flexibility in scheduling, problem solving. React and JS. | |
| How to overcome obstacles: | |
| Spend 30-60 mins researching/troubleshooting the issue, after 60 mins ask partner or other resource for help - pair if needed | |
| Schedule Expectations (When are we available to work together and individually?): | |
| Work during work time until 7-8ish latest. Open availability. | |
| Communication Expectations (How and often will we communicate? How do we keep lines of communication open?): | |
| Slack DMs, Constant communication while in-person. Timely responses (within 15 mins) using digital communication. | |
| Workload Expectations (What features do we each want to work on?): | |
| We will share the responsibility for all major features. Smaller details of some features can be worked on by just one of us. | |
| Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests): | |
| alternate github accounts for pushes to the master branch. each feature of the app will be worked on in its own branch and merged into master upon completion. | |
| implement waffle with features and small bugs - if working separately in branch then push up branch and merge adjust waffle board. | |
| Expectations for giving and receiving feedback: | |
| Giving feedback in person before it's a bigger issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment