#DTR: Define the Relationship
- 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?
- 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:
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?):
Passing data through react components. Grasp of the react lifecycle.
Communication, compartmentalization. Occasional pairing.
Just keeping communication lines open.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
Freeflowing, occasional schedule constraints.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
Touch base in the morning, quick stand-up, debreif. Slack channel for off-hours communication.
Similar to learning goals, reps testing react. Practice in independent learning.
Whenever.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
Pull request templates, github projects. Branches per concern.
Open, communicative.
Github projects.
Wireframe, set up project board.
None.
Slow to start indicates a lingering problem, too focused on one specific misunderstanding or bug. Overlearning a certain point.
Procrastination of a certain point, constant rebuilds of unfunctional/dead code.