If "how we work" was a codebase, we'd have the same ideals for it that we do for our code:
- We'd want fast deploys so that our teammates could benefit from improvements quickly.
- We'd want it to be easy to change.
- We'd want a
script/bootstrapso new coworkers could hit the ground running. - We'd want test-specs so we know whether a process is working.
- We'd want a
git blameso we could see why a process got added.
That's why:
- We keep our desktop procedures on the Web, so they're always up-to-date.
- We keep our desktop procedures in a repo so that we can accept pull requests to it.
- We organize them starting with Essential Responsibilities so that it's easier to see how the procedures fit together.
- We include Goals and Rationale along with Procedures so that we can see what a process is attempting to solve — which makes it easier to change.
- Clone the repo (or use GitHub's Edit File feature) to make changes and create a pull request for them.
- Follow the style guide for our Desktop Procedures.
- We'll talk through changes during our weekly Retrospectives and merge or discard them then.