A group project by Zack Nemeroff & Phil Delong & Jordan Holtkamp & Ryan Novak
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?):
- We wish to gain a better understanding for Python, Flask, and React Native.
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
- One of our teams strengths is our ability to effectively communicate with one another regarding issues and work styles. We feel our collaboration style is working together to explain unfamiliar concepts, otherwise divide and conquer.
How we can use our strengths to overcome obstacles:
- We intend to pair using driver/navigator. We will have a strong focus on communication throughout this project.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
- We can be reached via Slack during class time. We are all flexible with our schedules and will communicate daily when we plan to work together.
Communication Expectations (How and often will we communicate? How do we keep the lines of communication open? How will we make decisions as a team?):
- We will communicate on a daily basis performing retros and discussing our plan for that day. We will tentatively meet during work time everyday.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
- We wish to gain a better understanding of unfamiliar languages and platforms. We intend to regularly update our project board and make sure we are utilizing the INVEST principle and agile practices.
Workload Expectations (What features do we each want to work on?):
- We will focus on learning the new techs each group (FE & BE) are exploring and explain to the other end how things are working to the best of our abilities.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
- We will effectively use GitHub Project Board, Testing Suites for FE & BE, reaching out to our PMs.
- We will make sure to thoroughly comment on each and every PR when applicable.
Expectations for giving and receiving feedback:
- We intend to be honest and polite when we address feedback to one another. Knowing that just because I disagree, doesn't mean I think I'm right and you're wrong. We will use the "compliment sandwich" technique as much as possible. Open, direct, and kind. Address problems sooner than later.
Project management tools we will use (GitHub projects or Trello are popular tools):
- We will use GitHub Project Board.
the struggle is REAL
- It is important to recognize when problems become larger or more complex than anticipated
- Recognizing when we are avoiding difficult or less desirable tasks to complete
- Make sure we take to time check in regularly on current progress
- Not meeting deadlines or using time productively / getting partner help
- We will let our PM know if we believe we are significantly behind at any time