In the spirit of the Joel Scale for software dev, I propose an initial version of a scale for IT and operations folks.

• 3 points: all production infrastructure is redeployable in exactly the current form with a well-documented, automated system. /or/ 2 points: almost all infrastructure is like that, with a few exceptions which are properly backed-up off-site and have clear, tested redeployment documents. /or/ 1 point: most infrastructure is redeployable in exactly the current form, with well-documented exceptions and good reasons for those exceptions.

• 3 points: standard per-employee hardware is in stock and a new employee can be set up completely with less than an hour of work by one IT person. Everything will work and there is a Day One FAQ or similar document. An all-remote employee can be set up with less than an hour of work plus an overnight hardware delivery and a ten minute phone call. /or/ 2 points: standard per-employee hardware is in stock and a new employee can be set up on one workday’s notice; everything will work. Adding an all-remote employee takes less than an additional hour of work. /or/ 1 point: if a manager notifies IT that a new employee will start 5 or more workdays in the future, everything will be ready on that day. There is a complete checklist that every manager can see. 0 points: a new employee can start work, given two weeks notice. negative points: if the new employee can’t actually do anything on their first day

• 2 points: the dev bug tracker is separate from the IT ticket tracker. Both are easily searchable. 1 point: the dev bug tracker can link to a dependency in the IT ticket tracker. 0 points: the dev bug tracker also serves as the IT ticket tracker. negative points: IT work is not ticketed

• 3 points: all changes go through version control. All changes have associated tickets. Security-related changes require approval. There is a tested emergency procedure to get a major change through in 4 hours or less. /or/ 1 point: all changes go through version control. All changes have associated tickets. Security-related changes require approval. 0 points: each version is archived, even if it isn’t shipped negative points: changes are made to the production/development system

• 1 point: there is a reasonable, tested, well-documented policy for making exceptions. Exceptions are logged and reviewable. Exceptions are approved before being made. Exceptions are reviewed later and acknowledged, removed, or made part of policy. 0 points: there is an understanding that exceptions will need to be made, and they get logged. negative points: there are no exceptions allowed, so of course they aren’t logged

• 3 points: dependencies are tracked, tested, and brought into local repositories so that all subsequent builds are reproducible. 2 points: dependencies are tracked, tested, and locked to specific versions 0 points: dependencies are tracked and the build is tested negative points: dependencies are pulled from “HEAD” at every build time.

• 3 points: increasing pay automatically follows from increased competence and demonstrated responsibility 1 point: pay increases can be argued rationally negative points: if you want more money, you should find a different job