Technical Skills and the Software Project Manager

I was recently asked on Quora:  "In the path to becoming a Software Project Manager does being a generalist help more and provides more value or being a technical expert (specialist) is the best way to go?"

It is one of those questions that makes more assumptions than it should.  So my answer was a bit broader than the question itself.  I wrote:

You will almost inevitably become a generalist as part of the process of developing good skills as a Software Project Manager.  But you don't need to explicitly follow that path to become one.

Becoming a deep(er) technical expert in an area that really excites you is not strictly necessary, either, but has a few excellent advantages:

  1. You will have a deep understanding of how it feels to be a deep technical expert working "for" a Project Manager -- which is a very important perspective to have.
  2. You will have "something to fall back on" if you don't like (or are not successful at) being a Software Project Manager.
  3. Related to #2: Often deep domain experts make more money and are considered by management to be more valuable/irreplaceable than Project Managers -- so even if you like (and are good at) being a Project Manager, you may like getting paid more even more, and you'll have the option if you are a good deep technical expert as well.

In short, study and practice Software Project Management, to become a Software Project Manager.  This would consist both of project management training, and in developing people skills (motivation, communication, change management, persuasion, influencing and political skills). If you don't like the idea of using those people skills every day, this is not the career path for you.

Consider the choices within your technical career development path in a broader context -- not just how they contribute to a single goal, but how they can map into many different opportunities as you and your options grow and change over time.

http://qr.ae/G2vfP

Popular Posts