Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
- Work with Async JavaScript, React, Jest, Enzyme, React Router, fetch API, es6 synax, strong UI/UX, modular architecture, lifecycle methods, PropTypes and promises.
- Good mixture of both paired programming and individual programming. Start the project together and then begin working on seperate components and tests.
- Committed and positive and encouraging
- Talk it out.
- Async testing not taught until next week - so we will do this next week
- Good strong communication
- Establishing schedule/timelines/checkpoints/goals
- Breaking things down into managable chunks and figure out challenges early
- Don't struggle for too long
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
- Friday night expectations (made Wednesday night), assign weekend homework, leave async testing for the end (next week).
- After school/during work time is best
- Early morning check-in before school
- Setup meeting rooms
- Close to final product by the end of Monday (ideally only some async testing and README to go by the end of the day Monday)
- Friday 11pm - Sunday 5pm Greg out of state for a wedding - team to split up work prior to the start of the weekend for individual coding
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
- Face to face, slack, maybe some slack video this weekend
- Both of us getting as much out of: async JavaScript, React, Jest, Enzyme, React Router, fetch API, es6 synax, strong UI/UX, modular architecture, lifecycle methods, PropTypes and promises.
- Begin meetings with review, attempt to split work up and work individually for 1/2 hour or so
- Evenly split the work
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
- Good mixture of both paired programming and individual programming. Start the project together and then begin working on seperate components and tests.
- Atomic commits
- Utilize issues for functionality not
- Always work on a branch
- Never merge our own pull requests
- Deal with merge conflicts locally before pushing
- Daily checkins (except Saturday)
- GitHub projects
- Early and often
- Kind and specific
- GitHub projects
Day 1 Agenda:
- DTR
- Wireframe
- GitHub projects
- Setup repository
- mkdir file structure (app, planets, people, vehicles, scrolling)
- Ideate components and methods
- Submit to Travis/Robbie