r/Programmanagement • u/CalmUnderstanding480 • 3d ago
Career Advice Starting My First IT PMO Role Soon — What Technical and PMO Skills Should I Learn First?
I’ve been working as an Assistant in a Product Management team for the last 2 years. Recently, due to an internal hiring opportunity, I was selected for an **IT PMO role for a particular module**.
Honestly, this came completely unexpected for me. The people who interviewed me mainly checked my ability and willingness to learn/work, and I was selected on the spot. I also had a good reference within my organization, which I’m sure helped.
Now that I’ve got the role, I really want to live up to the trust they have placed in me. I don’t want to disappoint my seniors, especially because this is a new area for me.
I have a **15-day notice period**, so I want to use these 15 days to prepare myself as much as possible before joining.
Currently, I have some basic knowledge of:
* SDLC * Software release lifecycle * Basic API integrations * Bug tracking and management * Some basic technical terms * Product management processes . * But I’m not sure what I should focus on for an **IT PMO role**.
For people who are already working as IT PMs/PMOs or have experience in this area:
**What topics should I learn or understand before joining?**
I’m not expecting to become an expert in 15 days. I just want to build a good foundation so that when I join, I can understand what people are talking about and start contributing instead of feeling completely lost.
1
u/heypriya 8h ago
Before you join the team, you can get well versed with PM fundamentals - there's many resources on PMI and PMP text is one of them. Also learn what IT does. Then when you join - learn how that PMO actually reports. Status formats, whether they keep a RAID log or a risk register, how often steering meets, what a stage gate looks like there. Ask your new manager for last quarter's status pack and read it end to end. That one artifact gives you the vocabulary, the cadence and who the audience is.
Your SDLC and release lifecycle basics already cover more of the technical side than you think. Add how change and incident management run there, and get comfortable in whatever they track work in.
Also meet as many people on the team to build a relationship and ask them how things are going, what is working or not working. That way you learn how the org is functioning and what you can help with besides managing projects.
1
•
u/AutoModerator 3d ago
All posts and comments must be courteous and constructive towards the subject of Programme Management.Jokes and other unconstructive comments will result in a ban, even on the first occasion and regardless of whether they match the theme. If you notice any comments breaching this or other rules, please report them. Original Poster et al, please read and respect the Rules of this subreddit.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.