Migrating from software engineering to project management

Question

Hi,

I would be glad if you could share your career development experience.

Currently I'm working as a software engineer and I am looking the way to advance to higher position.

I would appreciate any advice regarding the knowledge, formal education or any other useful tip which could help at career building toward project manager and higher positions.

Answer 1

You should be aware that project management is not usually a higher position, but another type of work. Not everyone is suited to it, but give it a try.

I can highly recommend Behind Closed Doors as a best practice guide to managing projects and working with people.

Answer 2

You can start by looking at job sites for PM openings and making a list of skills/experiences they mention as requirements. You can then identify what you have and what you need to get.

Your best bet might be a 'PMP' certification from the Proj Management Institute (www.pmi.org). This is highly recognized and will surely help you in your pitch for a PM position.

If you are trying for PM openings in the same company you are in, then you can start by just letting your seniors know you are interested in such position. I know it does sound as if it does not count for much but it does.

Answer 3

There are volumes oriented towards managing the software development process. A single post will not do justice to the topic you ask.

• Rapid Development - a misnomer because it does not exactly teach how to develop rapidly. Rather it showcases how projects fail. Utterly. The anti-thesis of rapid, actually. Last segment catalogs process practices for various situations and team dynamics.
• Software Project Survival Guide - in summary, a stripped down version of Rapid Development, but practically focused on activities to get your project completed safely.
• Mythical Man Month - Understand that projects are run by people. And people, contrary to what management often believes, seldom work and operate 1 for 1 or add up linearly. Throwing more and more people has diminishing returns.
• Software Requirements 2E - Teaches you all the things that you need to capture from your clients/customers/users.
• Software Estimation - Now that you have your requirements, what is your next step? Guessing how long it would take to finish them all! Plenty of techniques on how to rely on your historical projects (you did capture metrics, right?) to make a better gauge the next time.
• Microsoft Solutions Framework - You do not have to follow the "prescriptive" guidance, but understand the philosophies and culture behind the MSF motion to promote a healthy development environment.
• Beyond Software Architecture - Not exactly project management but covers alot of aspects that is rarely covered in technical material. Issues like licensing, distribution, technical support, deployment, are all important matters in the lifetime of a project. This book is a reminder those are not small activities.

Answer 4

I can suggest everything from Tom DeMarco. Doesn't make you a project manager, but gives you a lot of good ideas.

Answer 5

As it is been noted, project manager does not inherently command a higher position than technical staff however in many organisations it’s the case. It is entirely possible to earn better compensation and have more influence than a project manager by becoming a very competent developer. One can become a project manager:

• By the way of “promotion”. Normally the route you need to aim at is developer –> team lead -> PM or developer -> BA -> PM. Note that being competent developer can do more harm here than good. Soft skills are more important.
• Starting your company or managing a not-for-profit project.
• Getting a formal education in PM.

Good technical ability is certainly helpful but you will mostly compete with people who have non technical degrees and hence are much better at soft skills (communication etc). In any case I suggest doing a formal qualification in software development project management either full or part time as a starting point.

The formal training will give you the benefit of systematic and structured approach to acquiring necessary skills and will force you through the tedious still crucial chores you'd otherwise rather avoid.

Reading individual books is helpful however, normally, a book reflects only a specific viewpoint thereas formal training tends to be more impartial. Also formal training includes many other activities (beyond reading) and provides with an access to the community of practise.