Full project schedule from a brief
Deliverable: A complete schedule built from a written brief — work breakdown structure, dependencies, calendar and milestones — with a critical path you can walk somebody through.
Course
Project scheduling taught as planning rather than as software training — dependencies, the critical path, resource conflicts and tracking a plan once reality starts disagreeing with it.
6 modules · 6 weeks
Deliverable: A complete schedule built from a written brief — work breakdown structure, dependencies, calendar and milestones — with a critical path you can walk somebody through.
Deliverable: The same schedule with resources assigned, every over-allocation identified and resolved, and a written note on what levelling cost in calendar time and why.
Deliverable: A baselined plan updated with four weeks of actual progress, producing a variance report that shows what slipped, by how much, and what it did to the finish date.
Every student gets placement assistance — that is what 100% placement assistance means. It is support for all, not a job for all. We do not promise a specific salary, a specific number of interviews, or placement at any named company, and you should be wary of anyone who does.
It is possible to learn every menu in Microsoft Project and still produce a plan that is useless.
That happens when tasks are linked because they happen in that order rather than because one genuinely cannot start until another finishes, and when durations are whatever makes the end date acceptable. The software recalculates all of it faithfully, which is precisely the danger — the output looks authoritative either way.
So the first module has no software in it. Work breakdown, honest estimating and real dependencies come first, because everything the tool does afterwards is only as good as those.
You will do a forward and backward pass on paper before you let Project compute one.
It takes an afternoon and it is the difference between reading a critical path and trusting one. When a client asks why the finish date moved by three weeks after a two-day delay, the answer requires understanding float — and that understanding does not come from watching a bar turn red.
Resource levelling is where most schedules quietly become fiction.
The tool will happily resolve every over-allocation and hand back a finish date months later than the one you promised. The useful skill is knowing what it did, which assumptions you can challenge, and how to explain the trade-off to somebody who only wants the original date. The second project is specified to force exactly that conversation.
Every real project slips, and the schedules that matter are the ones being tracked when it happens.
The tracking module covers baselines, variance and forecasting, and the last project is a plan four weeks into trouble. Presenting that honestly — what moved, by how much, what it means for the end date — is the part of the job that actually distinguishes a planner, and it is not a software skill.
Questions
No. The first module covers work breakdown, estimating and dependencies as planning concepts before the software appears at all, because people who learn the buttons without the concepts build schedules that look right and mean nothing. Site and coordination experience helps but is not required.
Both do scheduling, critical path and resource management. Primavera is the standard on large infrastructure and EPC projects; MS Project is far more common in IT, manufacturing and mid-sized construction. The concepts transfer almost entirely, so learning one makes the other mostly a matter of finding the equivalent menu.
For a short task list, yes. What Excel cannot do is recalculate a finish date when a dependency moves, find the critical path, or tell you a person is booked twice on the same day. Once a project has real dependencies and shared resources, a spreadsheet stops being a schedule and becomes a picture of one.
It covers what those interviews ask about — critical path, float, levelling, baselines and variance — and the three projects give you schedules to talk through. Whether it converts depends on your sector experience as well, and we will be straight with you about that rather than implying the software alone is enough.
Three details is all we need. A course advisor will call you back.
The Excel that offices actually run on — lookup logic, PivotTables, Power Query pipelines, dashboards and enough VBA to automate the work you repeat every month.
CAD taught to drawing office standard rather than as a tour of commands, because employers judge a drawing on layers, dimensioning and whether it plots correctly.
The four applications every Indian office runs on, taught around the tasks you will actually be judged on rather than as a tour of every menu.
Next step
Tell us what you want to learn and we will help you pick the right course, batch and mode.