Skip to content

The Process

Jump to bottom
Tiago Amaro edited this page Oct 27, 2016 · 13 revisions

Overview

The basic flow of work in our system:

Backlog > (Design) > Ready > Development > (Acceptance) > Review > Test > (Acceptance) > Done

Backlog

All pipelined work should go into the backlog for scheduling Bugs for immediate attention can go into the ready column on the relevant board. cc CTO/leads

Design

  • anything requiring UI/UX treatment
  • special case that may be handled orthogonally to actual development

Ready

  • work pulled from backlog ready for development
  • bugs for immediate attention

Development

  • work currently in development

Review

  • work in the PR queue for peer review

Test

  • work requiring testing

Acceptance

  • anything requiring stakeholder approval (generally larger pieces of UI/UX related work)

Done

  • live on production

Testing & Acceptance

For bug fixes and small pieces of work, if the developer can confidently push into production they are free to do so.

Some work requires more formal testing and acceptance.

Testing

After the PR has been accepted, developer moves card into testing.

The branch should be indicated on the card.

Acceptance & Approval

Anything requiring formal approval (basically the bigger front-end features and UI/UX related work) will need to be marked as approved before the PR can be merged and deployed

Developers can iterate with stakeholder in an environment as work progresses. If the stakeholder is happy in a staging environment, approval can be indicated on the card and move directly to testing or deployment as appropriate.

Deployment

  • deploys are made through Sentinel (more details at the doc/ops/deployment.md file)
  • production environment will only receive updates from the stable
  • it is good practice to tag a production deploy.
    • e.g. git tag `date "+v%Y-%m-%d-T%H%M%S%z"` && git push origin stable --tags

Trello

We have 4 boards in trello:

Backlog Forthcoming work, to be scheduled

Website Customer-facing website, ecommerce, and marketing

Systems Back-end spree issues and related systems

Special Circumstances Small self contained projects, eg Home Page refresh.

Clone this wiki locally