Project Management Fundamentals
For anyone new to the field or the responsibility — whether in a specialised department or given the responsibility to handle it on their own
This module gives anyone new to project management a solid, practical foundation in the PMI framework — enough working vocabulary and enough hands-on skill to plan, schedule, budget and monitor a real project from day one. It runs over 18 hours and is also offered as a full three-day course. It moves from core PMI terminology through the full planning chain — outcome, deliverables, Work Breakdown Structure, schedule and budget — to monitoring progress with PMI's own performance indicators. This is a practical foundation module, not a PMP exam-preparation programme: it does not count toward PMP certification credit hours, and it deliberately keeps to entry-level tools rather than professional-grade software.
See the 17 topics, and what participants can do afterwards
- What Is Project Management? Defining the DisciplineParticipants can explain, in one paragraph and in plain language, what project management actually covers — enough to correct the common assumption that it is 'just scheduling'.
- Projects vs. Operations, Programmes & PortfoliosParticipants can correctly classify a piece of work from their own organisation as a project, an operation, or part of a programme — and explain why the label matters.
- The Project Life Cycle: PMI's Five Process GroupsParticipants can place any activity on a live project into the correct process group, and spot when Monitoring & Controlling has been neglected.
- The Ten PMI Knowledge Areas — A Manager's MapGiven a real problem from their own work, participants can name the knowledge area it belongs to and one tool associated with it.
- Core PMI Terminology Every Manager Must KnowParticipants can use each term correctly in a sentence about their own project, without hesitating or reaching for a glossary.
- The Project Manager and the Sponsor: Roles and AuthorityParticipants can state clearly, for their own project, which decisions belong to the sponsor and which belong to the project manager.
- Starting From the Outcome: The Business Case and Project CharterParticipants draft a one-page charter for a project of their own, starting with the outcome, not the activities.
- Defining Deliverables and ScopeParticipants draft a scope statement for their own project, including an explicit list of exclusions.
- The Work Breakdown Structure (WBS): From Deliverables to Work PackagesParticipants build a full WBS for their own project, down to a work-package level they could hand to a team member today.
- Sequencing and Scheduling: Building a Gantt ChartEvery participant leaves with a software-built Gantt chart for a real project of their own, and can explain which tasks sit on the critical path.
- Bottom-Up Budgeting: From Work Package Cost to Project BudgetParticipants produce a costed, work-package-level budget for their own project, with a stated contingency reserve.
- Monitoring & Controlling: Tracking Progress Against the BaselineParticipants set up a simple, repeatable tracking cadence — what gets checked, how often, and against what baseline — for their own project.
- Earned Value Basics: Planned Value, Earned Value and Actual CostParticipants calculate PV, EV and AC for a sample project by hand, and for a slice of their own project.
- Performance Indices and Forecasting: CPI, SPI, and Estimate at CompletionParticipants calculate CPI and SPI for a sample project, interpret whether each is healthy, and produce a simple EAC forecast.
- Change Control and Issue ManagementParticipants can run a real change request from their own project through the log-assess-approve-update sequence.
- Project Closure: What 'Done' Actually MeansParticipants draft a closure checklist for their own project, including the specific sign-off they need from their sponsor.
- Closing Habits for Entry-Level Project ManagersParticipants leave with one written habit they commit to applying on their very next project.



