An IT project manager gets technology work finished on time, on budget, and in a way the business actually wants. You are the bridge between people who ask for a system (sales, finance, operations) and people who build it (developers, analysts, cloud and network engineers). The daily work is not coding. It is listening to what the business needs, turning that into scope and a schedule, spotting risks before they bite, running stand-ups and status meetings, tracking budget, and clearing blockers for your team. Why this matters: most IT projects fail from unclear goals, scope creep, and poor com
See the full roadmap free
Every stage from beginner to expert, with lessons, practice drills, projects, interview questions and free resources. Free with a Rolearch account.
Stage 1 of 4 · about 12 weeks
Learn the project life cycle (initiate, plan, execute, monitor and control, close), the triple constraint of scope, schedule and cost, and basic IT literacy: what servers, cloud, databases, APIs and networks are. Practice by writing a one-page project charter and a simple work breakdown structure (WBS) for something real, like migrating a small office to cloud email. Learn Scrum and Kanban basics and run a mini project with a free Trello or Jira board.
The project life cycle and the triple constraint
Every IT project manager task, from tracking milestones to approving changes, hangs on this frame. If you know where a project is in its life and which constraint is under pressure, you always know what to do next.
Basic IT literacy for project managers
You will lead technical staff and translate between business and engineering. You do not need to code, but you must understand the pieces well enough to plan work, spot risk, and ask sharp questions.
Writing a project charter and work breakdown structure
Initiating and planning are where projects are won or lost. A clear charter gets approval and agreement on purpose, and a WBS turns a vague goal into work you can estimate, assign, and track.
Scrum and Kanban basics
Most IT teams work in agile ways, so you must speak the language and run a team board from your first day. These two methods are the most common starting points.
Running a mini project on a free board
Reading is not enough. Running a real project, even a small one, teaches you to track work, guide people, and report progress, which are the core tasks of the job.
Then 3 more stages (about 74 weeks in all) with lessons, drills, projects, 10 interview questions with strong answers and free resources.