Jira

We will use Jira to track issues and manage our project. There is a separate project page for the backend (Circles) and frontend (Circles-FE).

Backend

• We will work 2 week sprints, where you pick up cards from either the backlog or the To Do list, and move them through every process.

• We have

  • tasks: general small issues. Look at them for details. Can also be a new feature.

  • bugs: generally raised by frontend team - these are high priority cards which describe an expected and actual behaviour that we need to reconcile.

  • spikes: these are “research” cards. Look at the description of a spike for details. These will often be design based. These are the exciting cards!

• We will have the following meetings:

  • standup: these are weekly, preferably synchronous discussions on:

    • what have you been working on?

    • what do you plan on working on?

    • did your plan from last standup go to plan? Why/why not?
      
      this is the main ritual we follow to keep track on the project.

  • bi-weekly: Retro

    • this is where we chat more in depth about

      • what is keeping us motivated

      • what is slowing us down

      • giving kudos to your incredible team members!

      • make some actions based on what we learn

Frontend

• We will work in sprints where we strive towards a certain milestone.

• Sprint planning

  • We discuss what we want to deliver

  • Issues are categorised into epics: i.e. Degree Selector, Course Selector, Progression Checker or Term Planner.

  • We assign tasks to individuals.

• During the sprint, try to update your progress on a particular issue by placing it in the relevant descriptor (e.g. ‘in progress’) in the Kanban board.

Integration

• If the frontend team requires certain revisions/additions to the backend API, go to the backend project page and create an issue in the ‘Integrate with frontend’ epic.

• Feel free to discuss these issues in the ‘integration’ channel on discord.