Skip to content

Instantly share code, notes, and snippets.

@Garrett-Iannuzzi
Last active February 3, 2020 21:25
Show Gist options
  • Save Garrett-Iannuzzi/d6ad01b3a31a19f417eb1dc0be3b33ec to your computer and use it in GitHub Desktop.
Save Garrett-Iannuzzi/d6ad01b3a31a19f417eb1dc0be3b33ec to your computer and use it in GitHub Desktop.
Palette Picker

Group Member Names: John Adams and Garret Iannuzzi

Project: Palette Picker

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?):

  • Finsih all requirnments
  • Learn BE testing
  • Further understanding of complete CRUD endpoints
  • Use two repos
  • Positive git workflow

Both want to collaborate and work together at the beginning and then split up work further into the project once more comfortable with direction and work. Over communicate, and have constant communication. How we can use our strengths to overcome obstacles: Use each instance as a learning situation and be kind, honest and actionable.

Schedule Expectations (When are we available to work together and individually? What constraints do we have?):

Flexible about needing to work on own material vs project. Work at least 4 nights after school from now to project due date. Friday night is night off. Come in to Turing one day on weekend to work on project - Sunday.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):

Daily check-ins - either 8:30AM or during lunch for reviewing PR and daily plan do not expect respone after 9pm use slack to constantly be in communication while remote working paired work together Abilities & Growth Expectations (Technical strengths and areas for desired improvement): We mostly want to collaborate on everything together.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):

Communicate progress and create PR for production quality code (no console logs, commented out code, etc.) use PR format we used in Mod 2/3. Stay up-to-date with GH Projects. Use SCSS for styling tool. Don't merge own PR. Expectations for giving and receiving feedback: Up front and honest. Don't be afraid to tell, and don't be afraid to be told. Actionable, honest, kind. Take each moment as a learning opportunity.

Project management tools we will use (GitHub projects or Trello are popular tools): GitHub Projects

Day 1 Agenda: DTR Memo - Project Mgmt Board - Wireframe endpoints - Make the Repo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment