Dev Processes

Team Rules:

• Will meet minimum twice a week in current class time to work together and talk about project.
• We will communicate using text messaging and discord to work outside of class.

Where we are:

• Our team is in the planning and setup stage, defining our product goals, roles, and collaboration methods before starting development.
• We aim to build a functional and well-documented Job Tracker App that helps users organize and track job applications efficiently, following an agile, sprint-based workflow.

• This is the layout that we have currently. Features like search, clear, filter, and refresh are features that we currently plan on implementing into our app.

Team Collaboration:

• Each member takes ownership of specific areas such as frontend, backend, database, and documentation, while all members contribute to testing and code reviews.

Conflict resolution & accountability:

• We handle disagreements through open discussion and majority rule. All major decisions are documented in issues or meeting notes to keep the process transparent and accountable.

Task Pipeline:

🌿 Branches

• Main Branch
  Where the main code lives. It is what the site is consisted of when the user enters it.

• Dev Branch
  Where the features are added and tested. If we like the layout/config of the dev code, we push that code to the main branch.

• Patch 1 — Gage and Jonathan
  Specifically for making changes to the README.