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

Being a Boss

DZone's Guide to

Being a Boss

· Agile Zone
Free Resource

See how three solutions work together to help your teams have the tools they need to deliver quality software quickly. 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, b s)
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, b s)
n.
A cow.

On second thought, some people do like cows.

Discover how TDM Is Essential To Achieving Quality At Speed For Agile, DevOps, And Continuous Delivery. 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.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}