I've been studying a lot about agile management, and even completed the Certified Scrum Master training. But still I ponder about how they define a traditional manager. Am I traditional?
On one hand, I started managing software teams over 25 years ago. I graduated from the US Air Force Academy and completed too many Professional Military Education programs. I got my Masters in Management over 20 years ago. I've lead big teams and small teams. Sounds like I should fit into the traditional camp.
On the other hand, when agile writers talk about traditional managers, they often equate it to the pointy-haired bosses who dictate every action. They talk about total reliance on command and control authority, process for process sake, and rigid conformance to the plan. Do you picture Michael from "The Office?" Is that really traditional? If so, I am definitely not traditional.
Perhaps we're looking at it the wrong way. It's not a matter of traditional vs. agile management. It's really all about good and bad management. I have never worked for a bad manager - the one agile calls traditional. I know they exist, but I've been lucky.
I've had some good role models. They taught me years ago, long before the agile movement began, that good management is all about setting directions, getting the resources, removing barriers, and then getting out of the way.
This was drilled into me from very early. I still remember quotes I had to memorize when I was a smack (1st year) at the Air Force Academy in 1976.
"Never tell people how to do things. Tell them what to do and they will surprise you with their ingenuity." General George Patton
"A leader is best when people barely know he exists, when his work is done, his aim fulfilled, they will say: we did it ourselves." Sun Tzu
To me these capture the essence of good management. But perhaps, I ponder too much. What do you think?