We work in the open by default . Of course, if something should be dealt with in private we’ll make an exception.
A new squad gets a new repository on the Notbinary Github. This is used for:
Online Kanban board (Github Projects)
Issues are used for tracking ongoing tasks
All code and prototypes
Github Pages site to document outcomes and decisions
Weeknotes should be published at the end of each week summarising activity and link circulated to the team and client(s)
At the end of an engagement we want to be able to provide a single Github repo that represents everything we did with a Github Pages site that provides all the relevant context — the expectation isn’t that the code is reusable in the open source sense but that all our learning is available and we show our workings (through the code). Also when we do Service Assessments or similar, our ambition is to avoid a slidedeck – we just step through the repo using the Github Pages site as the guide (as such we have created a GOV.UK-esque Pages template — as well as an upcoming Notbinary one).
We are agile not Agile™. Daily updates happen via Slack rather than traditional stand-ups; we do regular retrospectives (using FunRetro and Slack calls); for Alphas we work with a (loosely) one week-sprint cadence but a Kanban-esque backlog. We are #noestimates during Alpha.
For Beta we take a more rigorous approach that is still relatively lightweight by default. Two-week sprints are more likely. Some high-level estimating is likely to creep in. We will also be much more driven by TDD where the ‘stories’ will be much more precisely articulated than during Alpha.
In both cases we maintain public roadmaps as well.
We firmly believe in the words of David Kelley, founder of the global design company IDEO:
“A prototype is worth a thousand meetings.”
The goal of our squads is software, not slideware.