Agree ways of working

[cliftonc]

Practices

• Work mgmt via Github issues
• Does schedule need to always have us all available
  • Start together - be clear on language
  • After that we can break apart and work in pairs or individually
  • Use issues - assign individuals to manage work
• Standups / Standown
  • Placeholders
    • Monday- 10AM
    • Friday - 4PM
• Tracks will raise issues / questions across repos via issues
• Review process
  • All members are reviewers
  • One reviewer at the start - ideally someone from another company
• How do we resolve disputes / definitions?
  • Definition - functional track.
  • Clifton to own co-ordination with other tracks.

Outputs

• Documentation - markdown in repo
• Diagrams - draw.io
• Spreadsheets - WIP / collaboration - Google docs > transfer to markdown when complete
• API Specification - OpenAPI [ + GraphQL ]
• JSON Schema validation - agree approach
• Mock services - which languages
  • dotnetcore - c#
  • node - typescript / js
  • java
• Monorepo

Principles

• Create document - starting point and then continually / evolve it

Working together

• How will we know if we are finished - to do
• How will we resolve disagreements