Process Guide

[Alexreid95]

Process Guide

Overview:

This issue is intended to document for our current processes within this project. Once everyone agrees on the document, contents should only be changed once discussed with and agreed by the whole team (Excudling updating schedual).

Values

Project prioritizes a11y: a11y project

• Written in semantic HTML
• Avoids divs (uses React Fragments or appropriate semantic tag)
• Forms are appropriately labelled
• Site is accessible by keyboard navigation (appropriate interactiveelements are focussable)
• Uses WCAG AAA Color contrast in our styling
• Uses aria labels when text is not visible on the screen
• Uses aria-labelledby attribute where necessary

Testing

-Both front and back should have reliable tests 

Schedule

Time	Monday	Tuesday	Wednesday	Thursday
10.00	Standup	Standup	Standup	Standup
11.30	Break	Break	Break	Break
13.00	Lunch	Lunch	Lunch	Lunch
14.00	Standup	X	Standup	Standup
15.45	Break	X	Break	Break
17.45	Checkout	Checkout	Checkout	Checkout

Stand-ups

Standups will be held at 10:00 and 14.00.

In order to keep focus, our aim for standups will be 10min twice a day. They will focus on what you are currently working on, what you plan to do next and if you have any blockers. Discussions at stand up should revolve around things that concern the whole team.

Additional time for discussion can be arranged immediately following standup for questions or getting help from one another. This can be done in pairs or larger groups.

Please review the kanban daily and check that it is up to date.

Commit Messages

• Should include issue #
• Written with 'imperative tone' to describe what a commit does, rather than what it did.
  • E.g. Change color of search bar instead of Changed/changes color of search bar