Add in Definition of Ready and Definition of Done

This change details our Definition of Ready and Definition of Done. These are by no means final and can be improved over time.

This MR also removes some old/outdated descriptions of how we work.

Definition of Ready (DoR)

The Definition of Ready (DoR) outlines the requirements that enables an issue to enter the Sprint Backlog. The aim is that everybody understands:

• the goal of the issue
• what needs to be done
• what other issues need to be done before

An issue should meet the following criteria:

• Definition Of Done (DoD): The DoD should be made clear
• Acceptance criteria: Everyone should be able to understand what is expected to be delivered
• Weighted: The development team should provide estimations for the complexity of the issue
• QA: Consideration is given to how the issue will be demoed and tested prior to being deployed
• UX/Design: Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
• Personas: Who does this user impact and why?
• Experiments: Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.

Definition of Done

The Definition of Done (DoD) defines when an issue is considered completed and can be closed.

For an issue to be considered Done, it should meet the following criteria:

• The Acceptance Criteria has been met
• Code is tested: Testing includes unit/spec, E2E/automated and manual testing
• Merge requests must clearly outline:
  • What the issue does
  • How the issue can be tested
  • How the issue can be deployed
  • Include a screenshot(s) or a screen recording to demo the issue
• Code has been peer reviewed
• QA has been completed and has been passed
• Code has been moved to the Canary environment

An issue does not need to be:

• Released to end users