Link Search Menu Expand Document
Virtues

TL;DR

If at any step you need some help then speak to an Architect:

DataTechArchitects@sainsburys.co.uk

The Decision Forum

As a Smarter Working initiative, The Decision Forum has now adopted an Asynchronous Decision Making process.

What is it ? Asynchronous decision-making is a strategy that enables geographically and culturally distributed software teams to make decisions more efficiently. link

What is different ?

  • No further face-to-face weekly Decision Forum meetings.
  • Monthly review sessions to communicate any decisions ratified in the month.
  • A Virtual Agenda replaces the current Agenda
  • Independent discussions on the Proposal or Virtue currently on the Virtual Agenda via the Github Repo link

What is same ?

  • Proposals and Virtues continue to be raised as Pull Requests (PR) on the Github Repo link
  • Decisions still voted on using the Approval mechanism in Github.
  • Decision Forum communication continue on Teams and Slack Channels

What’s is in it for me ?

  • Fewer meetings means you get time back.
  • Read and discuss the PR when its convenient to you.
  • No need to wait until the meeting to raise any questions, issues or comments. Do it immediately on the PR.

Where can I get more information and help ?

  • Slack link
  • Teams link
  • DataTechArchitects@sainsburys.co.uk

Getting On The Virtual Agenda link

Rules:

  • no Milestone you are not on the agenda
  • no Due Date you are not on the agenda
  1. create your documentation (see sections below).
  2. create a Pull Request with the right prefix (quoted to highlight spacing):
    • “DISCUSSION : “
    • “DECISION : “
  3. create a Milestone with the same name.
  4. set the Milestone’s due date to be the date.
  5. attach the Pull Request to the Milestone.

How to create a Proposal

  1. create a branch with a meaningful name.
  2. create a new directory in proposal
  3. write your README.md (use this file name)
  4. your proposal will be added to the agenda for discussion until the due date
  5. ask for feedback.
  6. get a deeper understanding.
  7. PR to merge into main.
  8. Go to create a Principle, Standard or Pattern

How to create a Virtue (Principle, Standard or Pattern)

  1. create a branch with a meaningful name.
  2. find the pillar and domain in the Aspire Blueprint link
  3. create a new directory(s) in one or more of: (if the pillar and domain are missing add these directories)
    • principle
    • standard
    • pattern
  4. write your README.md (use this file name)

How to get a Virtue accepted by the community

  1. create a milestone prefixed DECISION:
  2. give the milestone a due date.
  3. create a PR with the right prefix (see below) and a link to your milestone.
    • #major - when you make incompatible changes
    • #minor - when you add functionality in a backwards compatible manner
    • #patch - when you make backwards compatible bug fixes
    • Semantic Versioning link
  4. your virtue will be added to the agenda for decision until the due date
  5. get the community to approve or request changes to your PR.
  6. after the due date the result is automatically ratified.
  7. generate metadata for the virtue.
  8. merge the PR request.