What are the key strengths of each person on the team?
- Julian- Debugging and complex coding concepts
- Ian- Design, following directions
- Mathieu- Code and code architecture.
- Joe- Debugging, wrangling tired teammates.
How can you best utilize these strengths in the execution of your project?
- Julian- Work on logic-heavy components, data handling and manipulating. But volunteered to do front end.
- Ian- Server setup and maintenence. Design driven assistance
- Mathieu- Flexible, but no design work. (but still can do it; though)
- Joe- Team lead, debugger, front ender
In which professional competencies do you each want to develop greater strength?
- Julian- Bravery (and also design)
- Ian- Confidence, Competence, Condiments
- Mathieu- Creativity
- Joe- Communication, planning and execution
Knowing that every person in your team needs to understand all aspects of the project, how do you plan to approach the day-to-day work?
- pair programming and standups
NOTE: Undoing, Redoing, Replacing, or otherwise steamrolling the project as an individual is considered to be unacceptable. Account for the inevitable divergence of ideas, execution tasks, and assignments of duties here.
What will be your group’s process to resolve conflict, when it arises?
- Speak calmly and openly. Be kind. Attempt to resolve issue indiviually, then through discussion with entire group, THEN raise to higher authority.
What will your team do if one person is taking over the project and not letting the other members contribute?
- See above.
How will you approach each other and the challenges of the project knowing that it is impossible for all members to be at the exact same place in understanding and skill level?
- If you need help ask for it. Employ the fifteen minute rule.
How will you raise concerns to members who are not adequately contributing?
- See above.
How and when will you escalate the conflict if your resolution attempts are unsuccessful?
- See above.
What hours will you be available to communicate?
- 08:00 to 18:00
What platform will you use to communicate (ie. Slack, phone …)?
- Slack
How often will you take breaks?
- As needed
What is your plan if you start to fall behind?
- Extend working hours.
How will you communicate after hours and on the weekend?
- Slack, but no expectation for reply.
What is your strategy for ensuring everyone’s voice is heard?
- Daily stand-up meetings
How will you ensure that you are creating a safe environment where everyone feels comfortable speaking up?
- Ensure participation in daily standups, encourage asking for help.
Work Plan
How you will identify tasks, assign tasks, know when they are complete, and manage work in general?
- Extensive pre-planning phase, whiteboarding, etc. github Projects
What project management tool will be used?
- github Projects
What components of your project will live on GitHub?
- any non-api components
How will you share the repository with your teammates?
- github Organization
What is your Git flow?
- locked down main, each person has own branch, merges need at least one review
Reminder as you work on and practice your presentations:
Expressions of gratitude should be heartfelt. When not presenting, team members should make strong eye contact with the “audience” / camera. Be positive, no matter how tired or burned out you may feel … “Your smiles can be heard over the phone”