Group Member Names: Paul and Eric
Project Expectations: What does each group member hope to get out of this project?
Paul - Hoping to get a better understanding of array prototypes and object oriented programming. Especially using the word keyword 'this'.
Eric - Everything Paul said above as well as ever more frequent commits on github. Exposure to new technologies.
Goals and expectations:
Goals
- Want to understand/articulate every aspect of every line of code. Strive for a smooth working relationship between partners. Have a functional working project. Revisit and improve css and html implementation.
Team strengths:
Strengths - Writing single use functions. Building functional html structure. Diligence. Hard work. Not giving up. Growth mindset. Simple DOM manipulation.
How to overcome obstacles:
- Take lots of breaks
- Talk through obstacles
- Psuedo code/wireframe before building
- Front load work
Schedule Expectations (When are we available to work together and individually?):
- Work time during school, after school, and on the weekends.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):
- Talk everyday, work together, respects each others break time. I statements.
Abilities Expectations (Technical strengths and areas for desired improvement):
- Reference above.
Workload Expectations (What features do we each want to work on?):
- Will work together on all aspects of project unless otherwise comfortable.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests):
- In person, multiple commits, 1 branch for each function in project scope/story.
Expectations for giving and receiving feedback:
- If we have a disagreement for more than 10 minutes then take a break to evaluate personal opinion before we decide to move forward.
Agenda to discuss project launch:
- Follow project schedule assigned.
Ideas:
Tools:
Additional Notes: