-
What are each of our learning goals for this project? What drives us in this project?
-
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
- A combination of the two is ideal to have a good balance of efficient progress; as well as, problem solving
-
How do you communicate best? How do you appreciate receiving communication from others?
-
How would you describe your work style?
-
What are each of our strengths? How can our strengths complement each other?
-
What’s gone well or poorly in your previous projects?
-
How will we set direction and make decisions as a team?
-
How will we overcome obstacles?
-
What do you need (resources, environment, communication) to do your best work?
-
What scheduling restraints do you have? What are your scheduling preferences?
-
What is your style for giving feedback? Does anything ever hold you back from giving feedback?
-
What do you identify as being your biggest strength(s) technically, as they relate to this project? Where do you feel you could use improvement in your technical skills, as they relate to this project? How can our team help support you in improving these skills?
-
What tools do you want to use to manage the project?
-
How do you want the group to solve problems when members run into issues with features of the project?
-
How do you know if a project is successful? How can we achieve that as a group?
-
How will we recognize each other's successes and celebrate them?
Any additional questions that you would like to add:
Project: SWAPI BOX
Group Member Names: Chris Basham, Victor Abraham
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?): - LEARNING GOALS? - Grow React, Jest, Enzyme, and React Router fundamentals. - Effectively make modular, scalable code base.
- WHAT DRIVES US?
- Making a project that we would feel good about placing in a resume/portfolio
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
- Both paired programming and divide-and-conquer approches will be utilized to have a good balance of efficient progress; as well as, problem solving.
How we can use our strengths to overcome obstacles:
- We are both grinders, so even though we don't have exceptional experience with the tech stack, we can acheive goals through perseverance. We have also worked together in the past on a group project, so we will leverage that knowledge/experience on this project. We also utilized a remote work approach on the last project, which we will lean on here.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?): Remote work, flexibility with zoom call Pair programming Open for all with communications Chris is expecting a child soon, so he may be absent and remote work could be even more necessary
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?): Slack Preloading communications clearly defined what is everyone working on Put the effort into doing what you said you were going to do Communicate all the important technical difficulties you may run into
Workload Expectations (What features do we each want to work on?):
- We plan to break-up the work load in a way that both members get to interact with everything.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
- We will use the GIT workflow we used in the past where conflicts are resolved on the local machine prior to pushing to branches on GitHub. Messages will be sent on slack when a PR is submitted. We will be sure to avoid working the same file at the same time.
Expectations for giving and receiving feedback:
- Feedback will be actionable, and objective. Both members are open to honest feedback at anytime.
Project management tools we will use (GitHub projects or Trello are popular tools):
- Trello Day 1 Agenda:
- Build Trello
- Wireframe