Inspectre

Team:

• Andrew Kim
• Brannon Starnes
• Min Xie
• Raaj Vardhan
• Scott Lease

Description

Searching for a fright? Inspectre is an application that lets users search for haunted locations of interest near them. Locations will contain backstories, reviews of the location, and pictures.

Cooperation Plan

• What are the key strengths of each person on the team?
  • Andrew - affinity for the backend work
  • Brannon - frontend, flexible in a team environment, easy-going, reigning things back in.
  • Min - backend, problem-solve, debug
  • Raaj - communication, project management, organization
  • Scott - experimenter, organizing
• How can you best utilize these strengths in the execution of your project?
  • Pair people together based on their proficiencies and cover each other's weaknesses.
• In which professional competencies do you each want to develop greater strength?
  • Andrew - project planning
  • Brannon - get better at backend stuff
  • Min - organization abilities
  • Raaj - frontend familiarity
  • Scott - frontend familiarity
• 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?
  • Morning standup meetings, make sure everyone is aware of the moving parts and what needs to happen before starting work for the day. 9:00am-9:30am
  • Post-lunch meetings to plan the second half of workday 1:30 pm-2:00 pm
  • End of day meeting to discuss integrating the work done over the day and review pushes and plan after-hours work. 5:00pm-5:30pm

Conflict Plan

• What will be your group’s process to resolve conflict, when it arises?
  • Bring it up in meetings/open channels of communication. We're adults here.
• What will your team do if one person is taking over the project and not letting the other members contribute?
  • First of all, no one will really want to. If it happens we'll communicate and escalate to TA/Instructors if unresolved.
• 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?
  • Pairing people up to cover each other's weaknesses, rotate working pairs to make sure everyone works together.
• How will you raise concerns to members who are not adequately contributing?
  • Open communication, escalate if necessary.
• How and when will you escalate the conflict if your resolution attempts are unsuccessful?
  • If it doesn't resolve after talking about it, we will alert a TA/Instructor regarding the ongoing issue.

Communication Plan

• What hours will you be available to communicate?
  • Open for messaging 24hours, expect a response between 9:00 am-6:00 pm PST.
• What platforms will you use to communicate (ie. Slack, phone …)?
  • Slack
• How often will you take breaks?
  • As needed. Lunch from 12pm-1:30pm
• What is your plan if you start to fall behind?
  • Adjust MVP as needed. Figure out where obstacles are and whether or not they are within scope.
• How will you communicate after hours and on the weekend?
  • Slack
• What is your strategy for ensuring everyone’s voice is heard?
  • Everyone needs to talk at standup. Equal time for sharing. Switch roles of meeting moderator, scribe, etc. every meeting. How will you ensure that you are creating a safe environment where everyone feels comfortable speaking up?
  • Speak with respect, not shooting down people's ideas, disagree respectfully. Essentially treat everyone with dignity.

Work Plan

• How you will identify tasks, assign tasks, know when they are complete, and manage work in general?
  • Trello. Break down features of the application into tangible parts. Assign teams to tackle those parts. Collaborate with entire team during integration and push into the main branch - end of day meeting.
• What project management tool will be used?
  • Trello, Envision, and Miro

Git Process

• What components of your project will live on GitHub?
  • The entire thing. Front end application, and backend server.
• How will you share the repository with your teammates?
  • We're all in an organization.
• What is your Git flow?
  • main branch for deployable app
  • staging branch for pushes throughout the day, place to integrate each other's work.
  • individual working branches where we do most of the individual coding.
• Will you be using a PR review workflow? If so, consider:
• How many people must review a PR?
  • At least one to review PR and final pushes into main happens during EOD meetings where we can all sign off on it.
• Who merges PRs?
  • Anyone can merge as long as reviews are done.
• How often will you merge?
  • As often as needed for staging. Once a day for main.
• How will you communicate that it’s time to merge?
  • Once we push it up we can message each other to take a look.