What are the key strengths of each person on the team?
- Donna : Team Player, adaptability, collaboration
- Hayden :Utilization of prior experience inside of project management to allow for a proper flow and progression of the project and utilization of a team flow method that has set goals, deadlines, and approval of the work done for each day.
- Kao : Analytical thinking, problem-solving, attention to detail, and business acumen.
- Kenya : team player, open to communication, love learning
- Reece : Collaboration, listening, critical thinking, supportive attitude, grit
- Tricia : adaptability, attention to detail, collaboration
How can you best utilize these strengths in the execution of your project?
- Donna : To help the team tackle problems together and help to the overall success of the project
- Hayden : Project Management and team organization
- Kao : Leverage critical thinking, finding solutions, and meticulousness to ensure project success.
- Kenya : to work with the team in the best way possible
- Reece : be supportive of everyone on the team when we hit walls throughout the project.
- Tricia : communicating well to team members, working together to tackle features, and being able to pivot with the challenges we may face.
In which professional competencies do you each want to develop greater strength?
- Donna : Want to get better at backend logic.
- Hayden : Commination, Team resolution, and leadership
- Kao : Effective communication with teammates and improve public speaking
- Kenya : sequel, mongo
- Reece : want to develop my technical jargon to match with the material we will be using
- Tricia : ambiguity and confidence in myself, to trust my gut
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?
- Daily meetings will help in guiding who is going to be doing what portions of the project. This coupled with the project board through GitHub will help maintain our workflow and who is in charge of what for each day as we pair program.
What will be your group’s process to resolve conflict, when it arises?
- Approach the conflict respectfully with psychological safety in mind. Figure out where the root of the problem or concern is coming from and figure out a plan to resolve it.
What will your team do if one person is taking over the project and not letting the other members contribute?
- Come together as a team and inform that individual how their actions are affecting the team as whole. Try to come up with a better way to break up the work into sections to prevent someone from hijacking the entire project.
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?
- Utilize each other's strengths in different areas of coding. We all are on different levels in different areas and helping one another in those weaker areas is what will increase our learning across the board and help us navigate through all the different challenges.
How will you raise concerns to members who are not adequately contributing?
- Set realistic expectations for each other on how we will contribute and at a reasonable pace. We are developers, but we are still learning a lot of things we will be working with. So keeping that in mind with how we model who is doing what, will help prevent this.
How and when will you escalate the conflict if your resolution attempts are unsuccessful?
- Since we are on such a short time period to accomplish our project, if something has not been able to resolved within a 24 hour period, we will reach out to our instructor, Ryan Gallaway, for assistance in navigating through the problem.
What hours will you be available to communicate?
- Given we are on varying time zones with some of us actually into the next day due to this, we will be trying to stay within our normal core hours that everyone has already worked out in their lives to be available.
What platforms will you use to communicate (ie. Slack, phone …)?
- We will primarily be using Slack for group communication, we have created our own group chat.
How often will you take breaks?
- We plan to stay in line with our class breaks.
What is your plan if you start to fall behind?
- If we begin to fall behind, we will look at what is pulling the project behind our deadline and come together to either address the problem together or adjust what our MVP is going to be.
How will you communicate after hours and on the weekend?
- We will respect each other's established work times that we agreed to upon the project start.
What is your strategy for ensuring everyone’s voice is heard?
- Daily meetings and pair programming rotations as features are completed.
How will you ensure that you are creating a safe environment where everyone feels comfortable speaking up?
- Keep the psychological safety standards we learned in our previous class in mind at all portions of development. Our daily meetings will allow for everyone to voice their concerns or plans for the day and hopefully it'll allow for us to be able connect on a personal level as well.
How you will identify tasks, assign tasks, know when they are complete, and manage work in general?
- We will use our project board to generate TODOs and allow for us to keep track of how long different features will be taking and where we might need to push more resources in to.
What project management tool will be used?
- We will be using GitHub project board so we have all of our tracking board and repos in the same location.
What components of your project will live on GitHub?
- Since we are only working on backend for this project we will have all the components living on GitHub that we can. However, we will need to expand on our problem domain so this may change if we need to alter our idea to match the requests of the client.
How will you share the repository with your teammates?
- We are all a part of the LetsChatItUpWithChatGPT organization and have admin access.
What is your Git flow?
- We will protect our main branch with 2 person authentication that DID NOT submit the merge request to main. We will all work paired programming to resolve features in their own branches to allow for clean code editing and understanding of who was working on what at any given time.
Will you be using a PR review workflow? If so, consider:
How many people must review a PR?
- 2 people who did not submit the PR will have to review as protection on the main branch
Who merges PRs?
- Any of us will be able to after reviews.
How often will you merge?
- We will only merge with feature completion, however if the feature is large and multi-staged we could merge multiple times at succesful testing periods.
How will you communicate that it’s time to merge?
- Daily meeting or during work days if we have a large feature added that is fully functioning. We will be together while working so this may be done through Remo or Slack message.