Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Worst Practices Teams

DZone's Guide to

Worst Practices Teams

· Agile Zone ·
Free Resource

The Agile Zone is brought to you in partnership with Techtown Training. Learn how DevOps and SAFe® can be used either separately or in unison as a way to make your organization more efficient, more effective, and more successful in our SAFe® vs DevOps eBook.

Exec Summary

Borrowing from Newton’s 3rd Law, and in the context of Information Technology at a sufficiently large organization:

For every “best practices” team, there is an equal (in magnitude) and opposing
“worst practices” team silently going round the organization making things worse.

Just one example:

Printer names

There’s often a group within an organization who are authorized to name printers, and are passionate about encoding location information and more into the printer name. Names like H12G174P result.

Instead, printers should always have names. A team that’s co-located benefits from being able to remember printers, cognitively map their locations, verbally pass on their whereabouts: “Godzilla is color and prints on both sides, it’s the one by the water cooler”. You should go as far as to make DNS entries for them that match their name, so that Mac and Linux users can more easily find them.

Google offices had/have names for printers like ‘Snoopy’, ‘Superman’, ‘Dilbert’, and made that pretty prominent on the printer, if not with a picture of the same pinned up on the wall above it.

 

Adopting a DevOps practice starts with understanding where you are in the implementation journey. Download the DevOps Transformation Roadmap, brought to you in partnership with Techtown Training

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}