Over a million developers have joined DZone.

Being a Boss

· Agile Zone

Learn more about how DevOps teams must adopt a more agile development process, working in parallel instead of waiting on other teams to finish their components or for resources to become available, brought to you in partnership with CA Technologies.

In some manner or another, I've served in roles frequently referred to as "boss" for over 20 years. In a few cases, I owned the company, in whole or in part. In many more instances, I held some rank that granted me authority over the work-lives of others. I've learned a great deal over the years. And I am definitely still learning.

If you'll indulge me, I'd like to share what little I have learned about being a boss.

The first lesson - Don't be a boss.

Be a mentor, a guide, a confidant, a facilitator, a shield, and a coach. But don't be a boss.

Nobody likes a boss.

boss 1 (bôs, bs)
n.
One who makes decisions or exercises authority.

v.tr.
To give orders to, especially in an arrogant or domineering manner.

v.intr.
To be or act as a supervisor or controlling element.
boss 2 (bôs, bs)
n.
A cow.

On second thought, some people do like cows.

Discover the warning signs of DevOps Dysfunction and learn how to get back on the right track, brought to you in partnership with CA Technologies.

Topics:

Published at DZone with permission of Michael Norton, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

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

{{ parent.tldr }}

{{ parent.urlSource.name }}