Project:
Group Member Names:
Project Expectations: What does each group member hope to get out of this project?
Goals and expectations:
Team strengths:
How to overcome obstacles:
Schedule Expectations (When are we available to work together and individually?):
Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):
Abilities 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):
Expectations for giving and receiving feedback:
Agenda to discuss project launch:
Ideas:
Tools:
Additional Notes:
Group Member Names: Haley Jacobs & Todd Ayres
Project Expectations: What does each group member hope to get out of this project? Honing Javascript knowledge and also utilizing a few jQuery shortcomings. Progressing from Linked List
Goals and expectations: A supportive and positive communal working environment; And again, steady progression of knowledge
Team strengths: A shared desire to prove our knowledge despite insecurities. Can-do attitude
How to overcome obstacles: Communication and time management
Schedule Expectations (When are we available to work together and individually?): After school and at Gavin's weekend study group; individual pairings as needed with available resources
Communication Expectations (How and often will we communicate? How do we keep lines of communication open?): Daily, before, during and after classtime; in addition we have exchanged numbers to keep communication more fluid
Abilities Expectations (Technical strengths and areas for desired improvement): jQuery is still a bit of an enigma in comparison to Javascript, so I would love to more fully be able to embrace any understanding in these areas
Workload Expectations (What features do we each want to work on?): 50/50; Challenge ourselves where needed.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests): Following the logical timeline of the project as outlined in the project spec. Even commits etc.
Expectations for giving and receiving feedback: Positive and useful, not degrading.
Agenda to discuss project launch: Saturday, Gavin's apartment study group; get project to the finished level of previous project before embarking on new features and project challenges.
Ideas: Focus on what we can implement with confidence and not get caught up on the aspects we cannot fully complete.
Tools: Pairings, communication, designated working times
Additional Notes:
Group Member Names: Haley & Kylee
Project Expectations: What does each group member hope to get out of this project? Goals and expectations: Kylee : I would like to complete the project fully Haley: Build strength with array prototypes
Team strengths: Kylee: Time blocking, and Responsive and pseudo coding Hayley: Time blocking, Empathetic, Typing
Abilities Expectations (Technical strengths and areas for desired improvement) & How to overcome obstacles: Kylee : Drive, reps for JS and jQ , being more direct Hayley: Communicating directly, array prototypes
Schedule Expectations (When are we available to work together and individually?): Friday 1-3pm Sat 9-5pm (optional remote pair 630-8) Sun: (optional remote pairing) Monday-Wednesday 2-4 work time
Communication Expectations (How and how often will we communicate? How do we keep lines of communication open?):
Slack Video call/Sharescreen DM/ Group messages
Workload Expectations (What features do we each want to work on?): Do together Driver Nav Remote conference call
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests): Follow git workflow chart Pseudo coding
Expectations for giving and receiving feedback: Direct but gentle, honesty.
Agenda to discuss project launch: Work through Code fair Finish html -Friday Finish Css - Sat Use work time to complete JS
Ideas:
Not at the moment
Tools: Sublime. Turing Lessons. Noted
Additional Notes:
Go TEAM!