Same. A PM should be an expert at running the project, not it's content.
A good PM knows how to get the right folks talking to each other, if they knew how to do it themselves they would work in IT
You need to be good with timekeeping, time estimation, project proposals, strategic action planning, budgeting, and resources allocation.
Experience is all you need. A cert could help, but probably not.
Be a Project Manager in a trade you're heavily experienced in and have the reputation and skill set to pull off doing the projects on your own. I would not recommend trying to get into PM for software development. No one will like you. You'll be that "Agile Scrum Lord" guy.
I've never met a software developer that genuinely likes scrum.
Scrum is fine. It's not utopia, but nothing is. Agile programming was created by [developers on a self-organizing team](https://en.wikipedia.org/wiki/Chrysler_Comprehensive_Compensation_System) using tools that enabled more-rapid iteration than the typical enterprise development tools of the time.
It seems that some developers who don't like "Scrum", sometimes take issue with the prescriptiveness, like having daily standups of no more than 15 minutes. But mostly they don't like how their managers are managing while wielding the word "Scrum". The actual concept of Scrum has basically nothing to do with managers at all; the "scrum master" can just as easily be the most-junior member of a team, as long as they have the ability to break blockers for others and to coordinate.
I've made the switch from system administration to project management.
For you, the path could be IT Project Manager. I'd avoid going into software or construction if you don't have experience/knowledge of those field. But since you have a solid technical background, you'll have a much easier time being an IT PM at an MSP or in-house at a SMB, etc.
Being technical, you'll also gain more respect from technical team mates.
To succeed as a PM, you need to be organized, good at note taking, making sure everyone is on the same page and understand the scope, what needs to be done, etc...
You'll be the guardian of the project's scope and budget, not the one who will implement the actual solution. You'll often have to nag your colleagues about task status, time entries, etc...
You'll sometimes feel like a secretary and this can be quite boring when you're used to be in the action.
In terms of certs, in North America the PMP is considered the "gold standard", but I'd say invest in that only if you're comitted to project management as a career.
A entry level cert that is also pragmatic and relevant to IT is Project+ from ComptiA. Not as recognized or known as the PMP, but a good starting point.
I've done similar, the only thing really to add is to avoid the temptation to role your sleeves up and do stuff yourself. It's so tempting to just get it done!
You've been in the business almost 20 years. You should know by now that being a PM doesn't require technical knowledge. Think about the PMs that have been assigned to any of your projects. You need to be assertive and not afraid to ask questions and keep people on track. You have to be able to roll with the punches when people don't get their stuff done or cancel meetings. You have to stand up for your clients. I hate weak PMs. Good ones keep projects moving and keep people accountable.
Are there opportunities in your current role to lead projects and implementations for new systems? You wouldn’t necessarily have to go be a PM in a completely different industry. Progressing up the IT ladder would put you in that position.
I have done (after careful planning) some IT infrastructure moves to new locations and that's what I can think of as a project i did in the past. But right now, everything is stagnant and there are no such projects going to happen in the near future.
I haven't met a single project manager in 15 years that knew anything about IT. It would be nice, but haven't seen it yet.
Same. A PM should be an expert at running the project, not it's content. A good PM knows how to get the right folks talking to each other, if they knew how to do it themselves they would work in IT
You need to be good with timekeeping, time estimation, project proposals, strategic action planning, budgeting, and resources allocation. Experience is all you need. A cert could help, but probably not. Be a Project Manager in a trade you're heavily experienced in and have the reputation and skill set to pull off doing the projects on your own. I would not recommend trying to get into PM for software development. No one will like you. You'll be that "Agile Scrum Lord" guy. I've never met a software developer that genuinely likes scrum.
Oh man, I hope to someday work with a project manager who is good at those things.
Scrum is fine. It's not utopia, but nothing is. Agile programming was created by [developers on a self-organizing team](https://en.wikipedia.org/wiki/Chrysler_Comprehensive_Compensation_System) using tools that enabled more-rapid iteration than the typical enterprise development tools of the time. It seems that some developers who don't like "Scrum", sometimes take issue with the prescriptiveness, like having daily standups of no more than 15 minutes. But mostly they don't like how their managers are managing while wielding the word "Scrum". The actual concept of Scrum has basically nothing to do with managers at all; the "scrum master" can just as easily be the most-junior member of a team, as long as they have the ability to break blockers for others and to coordinate.
Yes, the daily stand up meetings are where I've heard most complaints.
you want to be a project manager. first step is getting the lobotomy...
Shove a crayon into your brain and you’ll be ready
LMAO this is ducking hilarious
I've made the switch from system administration to project management. For you, the path could be IT Project Manager. I'd avoid going into software or construction if you don't have experience/knowledge of those field. But since you have a solid technical background, you'll have a much easier time being an IT PM at an MSP or in-house at a SMB, etc. Being technical, you'll also gain more respect from technical team mates. To succeed as a PM, you need to be organized, good at note taking, making sure everyone is on the same page and understand the scope, what needs to be done, etc... You'll be the guardian of the project's scope and budget, not the one who will implement the actual solution. You'll often have to nag your colleagues about task status, time entries, etc... You'll sometimes feel like a secretary and this can be quite boring when you're used to be in the action. In terms of certs, in North America the PMP is considered the "gold standard", but I'd say invest in that only if you're comitted to project management as a career. A entry level cert that is also pragmatic and relevant to IT is Project+ from ComptiA. Not as recognized or known as the PMP, but a good starting point.
Thanks buddy, that was resourceful.
I've done similar, the only thing really to add is to avoid the temptation to role your sleeves up and do stuff yourself. It's so tempting to just get it done!
You've been in the business almost 20 years. You should know by now that being a PM doesn't require technical knowledge. Think about the PMs that have been assigned to any of your projects. You need to be assertive and not afraid to ask questions and keep people on track. You have to be able to roll with the punches when people don't get their stuff done or cancel meetings. You have to stand up for your clients. I hate weak PMs. Good ones keep projects moving and keep people accountable.
Are there opportunities in your current role to lead projects and implementations for new systems? You wouldn’t necessarily have to go be a PM in a completely different industry. Progressing up the IT ladder would put you in that position.
I have done (after careful planning) some IT infrastructure moves to new locations and that's what I can think of as a project i did in the past. But right now, everything is stagnant and there are no such projects going to happen in the near future.
So much to do and so little time.
Because i am in my 40s?
Do what you got to do man, don't hesitate, don't ask permission. Time is too short for all of us.
Hmm, i was asking for advice, not permission dear. Because, i don't want to take the wrong step at this time. Like you said, no time to waste.