Introduction to Project Management

IT projects slip for predictable reasons: unclear scope, schedules nobody tracks against, stakeholders who surface late, and risks no one planned for. When technical staff run project-based work without a shared PM vocabulary, the result is rework, budget overruns, and scope creep.

Who to assign: This beginner-level course fits IT Practitioners who are moving into coordinator or junior PM roles. It also fits Team Leads who own task tracking and status communication, and any engineer who regularly contributes to cross-functional projects. No prior PM experience is required.

Time investment: About 5.7 hours across seven skills of roughly 45–50 minutes each. The skills cover roles, scope, schedule, cost, risk, communications, and stakeholder management. Most learners can finish in one to two weeks alongside normal workloads.

What changes for your team: Instructor Bob Mailer compares predictive (Waterfall) and Agile approaches, including where Scrum and predictive approaches fit and how they may be used together. That makes the course useful for organizations standardizing project vocabulary across technical teams. Learners practice:

• Breaking deliverables into work breakdown structures (WBS)
• Defining scope and identifying project work
• Estimating costs top-down and bottom-up
• Writing risk plans before execution begins
• Watching for variance and routing it through change control

Change-management note: This is foundational training, not certification prep. Teams pursuing credentials can follow it with CBT Nuggets CAPM or CompTIA Project+ training.

Rolling it out: Build a Playlist that sequences the two, then use Team Reporting to confirm completion across your project contributors.

IT projects rarely fail on technical skill alone. They stall when scope drifts, schedules slip without anyone noticing, risks go unplanned, and stakeholders surface late. This course gives IT teams a shared project management vocabulary and a practical framework for keeping work on track.

• Fewer surprises from scope creep: Your team learns to break a big deliverable into a work breakdown structure with smaller, trackable work packages. Each piece of work becomes easier to understand, assign, and connect back to the project deliverable.
• Clearer schedule coordination: Team Leads learn how schedules help keep everyone on the same page, using the same language, and working from the same plan. The course also introduces predictive, Agile, and hybrid approaches so teams can match the method to the work.
• Risk plans in place before execution: IT practitioners learn to define probability and impact up front. That gives them a plan to follow when a risk hits mid-project, instead of improvising under pressure.
• Smoother stakeholder alignment: Through real-world scenarios, your team practices identifying stakeholders early, navigating conflicting interests, and escalating appropriately. They also learn to ask customers the right questions about vision and minimum quality.

Scenarios include an Agile mobile app broken into user stories, an enhanced-authentication feature decomposed for a product owner, and long-lead predictive projects. Together, they help IT Directors decide when Agile, Waterfall, or hybrid approaches fit the work.

Knowledge

• How projects close the gap between where an organization is and where it wants to be, and how a project management office (PMO) assigns a project manager and cross-functional team members
• The core responsibilities of the project manager, the role of the customer and product owner, and when predictive, Agile, or hybrid approaches fit the work
• How scope is defined and broken down, from epics into user stories in Agile and from deliverables into smaller, manageable pieces in a work breakdown structure (WBS)
• How schedule and budget connect, including top-down and bottom-up cost estimates and why predictive scheduling suits long-lead-time projects
• Why variance is the central measure of project health and how change control responds to a negative variance
• How a risk plan sets probability and impact before risks are identified, and how stakeholder identification, conflicting interests, and escalation affect delivery

Ability

• Break a project deliverable into a WBS whose work packages roll into the schedule and budget and roll back up as work completes
• Turn a high-level request, such as a mobile ordering app, into prioritized user stories with a clear definition of done
• Connect planned work, schedule expectations, and budget estimates so project progress can be measured clearly
• Track planned work against actual progress to spot variance early and raise changes through change control
• Build a risk plan before execution and choose a response strategy, such as exploiting a positive risk
• Identify stakeholders up front, manage conflicting interests, and communicate status clearly through dashboards and presentations