Home

Squad rules of engagement

We work in the open by default - if something needs to be dealt with in private we deal with that be exception.

What open looks like for us:

Github

A new squad gets a new repository on the Notbinary Github.

This repository is used for:

• Online Kanban board
• Issues are used for tracking ongoing tasks
• All code and prototypes
• Github Pages/Wiki site to document outcomes and decisions (for Service Standard assessment and knowledge transfer)
• Weeknotes should be published at the end of each week summarising activity and URL circulated to the team and client(s)

Slack

Each squad has a private channel on the Notbinary Slack.

Slack is the default team communication channel.

This channel includes

• A user-group so all members can be contacted at once
• Invited members from the client-side (one channel guests in Slack parlance)
• ‘The Standup Alice’ chatbot to handle daily updates via Slack

Email

When email communication is required with the client(s) the team email should be BCC’d in to all communications (for example epc-team@notbinary.co.uk) to ensure nothing is lost in team members inboxes if they are unavailable (the archive can be searched via Notbinary’s Google Groups account).

Meetings

We have ’Show and Tells’ per sprint. These are facilitated by the Delivery Lead. They should also act as the primary stakeholder meeting for broader conversations.

Otherwise seek to minimise large group meetings. Where possible one-to-one or small target conversations with subject matter experts are our preference.