RancidTomatillos Group Member Names: Colin Koga, John Adams, James Miller
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?):
Iteration 5 would be a good goal to shoot for. We learned all the objectives Before we move on to the next iteration make sure to have the testing, and refactoring in place.
John is strong at planning, and is good at collaboration.
Colin is good at big picture and seeing the overhead, while interjecting ideas. Visionary.
Jim can be support or leader as necessary, communicate a bunch.
Use our ability to communicate and pair programming to ensure that everyone is on the same page.
Our ability to articulate complex ideas simply, will help us help each other. WE FUCKING BAD ASSES
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
8:30 daily standups to discuss the progress being made on the project Down to stay late or leave early depending on the feeling. Slack calls/remote calls if necessary
With the break we plan to have some tentative work days over the break whenever we are available since there are some schedule conflicts with the first weekend and second weekend availability.
Firmly plan to have a recap before the break to detail what we want to work on over it, and then another review/recap day on Sunday to touch base and be ready to hit the ground running when class resumes.
Communication Expectations (How often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
Daily Standup Use slack frequently, and try to focus on paired programming early on in the project Slack cutoff around 8: 30 pm
Break Communications:
Discuss on Friday what day we can plan to all be on so we can remote in and work. Plan to err on the side of over communicating, if we plan to take a particular or need to swap responsibilities just keep all persons apprised.
Group: Everyone wants to get reps on Testing. John is cool to do the CSS/SASS
Try to break up each iteration into each of its individual parts
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
Utilize the PR template. Have the two other members review the PR before pulling in, use feature branches and never work, and use Github Projects.
Work off separate branches, create issues, establish PR using the template
Overall be positive, constructive. If there are any exceptions do so in a kind well thought out manner that lets the person save face. Actionable, Honest, Kind.
Day 1 Agenda:
Create the Channel with all the group members Layouts/Wireframes sketches Group DTR Project management tool (GitHub Projects, Trello, etc.) - be sure this is public so your instructors can view it
Let it marinate, setup the basic repo and github projects, and wireframes.
Additional Notes: