Project Management Course Guide: PMP, Agile, and Practical Delivery

A project is a temporary undertaking that creates a unique product, service, or result. Its business purpose should be explicit before detailed planning begins. For a customer-service portal, the purpose might be reducing avoidable support contacts, not simply launching a website. A project charter establishes authorization, objectives, high-level scope, key stakeholders, and the project manager’s authority. Project governance then defines who funds the work, approves major decisions, accepts deliverables, and resolves escalations. Separate output acceptance from benefits realization: a sponsor may accept the portal at launch, while an operational owner measures its business effects afterward.

Practitioners make this structure usable through decision thresholds, ownership, and communication agreements. Identify who is accountable for security approval, who controls the budget, and who can authorize scope changes. Stakeholder management involves understanding influence, needs, and concerns—not merely distributing status reports. Interview service agents, customers, operations staff, and sponsors early because their definitions of success may conflict. Convert these expectations into measurable objectives and acceptance criteria. For example, distinguish a technical requirement for authentication from a business objective of successful self-service completion, and specify how each will be evaluated.

Predictive delivery emphasizes defining scope and planning execution before substantial implementation. It is useful where requirements are sufficiently stable, dependencies are understood, and late changes are expensive. Agile project management favors short feedback cycles and progressive refinement when uncertainty makes detailed upfront commitments unreliable. These are not synonyms for disciplined versus undisciplined work. Both require planning, risk management, quality control, and stakeholder engagement; they differ in when decisions are made and how change is incorporated. Select an approach by examining requirement volatility, technical uncertainty, regulatory obligations, integration dependencies, and access to users.

Hybrid project management combines approaches at meaningful boundaries. A portal initiative might use predictive procurement and infrastructure milestones while developing customer-facing features iteratively. Define how the components connect: what evidence supports a release decision, which interfaces are stable, and how discoveries affect funding or milestones. Avoid the dysfunctional version of hybrid delivery in which scope, dates, and cost are fixed while teams are told to be Agile. Instead, establish a realistic trade-off mechanism, such as fixing a release window while allowing lower-value features to move. Review the approach when conditions change rather than treating the initial selection as permanent.

The Critical Path Method calculates the longest-duration dependency path through a project network, establishing its minimum duration under the model’s assumptions. Begin by decomposing scope into manageable work packages and then identifying activities, durations, and dependencies. Consider five activities measured in working days: A, requirements, takes 3; B, design, takes 4 after A; C, data preparation, takes 5 after A; D, build, takes 6 after B; and E, integration testing, takes 2 after both C and D. The path A–B–D–E takes 15 days, while A–C–E takes 10. The critical path is therefore A–B–D–E.

A forward pass calculates earliest starts and finishes: A finishes at day 3, B at 7, C at 8, D at 13, and E at 15. A backward pass from day 15 gives C a latest finish of day 13 and latest start of day 8. Because C can start as early as day 3, it has 5 days of total float. Critical activities have zero total float in this unconstrained example. These calculations assume the needed resources are available; resource leveling may change the schedule. To shorten delivery, examine critical-path activities, using crashing or fast tracking only after evaluating added cost, coordination demands, and rework risk.

Earned Value Management integrates scope, schedule, and cost against a time-phased performance measurement baseline. Planned value (PV) is the budgeted value of work scheduled by the status date. Earned value (EV) is the budgeted value of work actually completed. Actual cost (AC) is the expenditure incurred for that work. Suppose a project has a budget at completion (BAC) of $100,000. At a review, PV is $50,000, EV is $40,000, and AC is $45,000. Schedule variance, EV − PV, is −$10,000; cost variance, EV − AC, is −$5,000. The project has completed less budgeted work than planned and spent more than that completed work was budgeted to cost.

The schedule performance index is EV/PV = 0.80, and the cost performance index is EV/AC ≈ 0.89. If current cost efficiency continues, estimated cost at completion is BAC/CPI, approximately $112,500 using the unrounded ratio. This is a conditional forecast, not a certainty. If the variance was exceptional and remaining work follows its original budget, an alternative estimate is AC + (BAC − EV), or $105,000. Select the assumption based on evidence. Earned value also requires credible completion rules, such as weighted milestones or accepted deliverables. Schedule variance is expressed in budget units, not days, so it cannot replace network analysis or reveal the finish date by itself.

The Scrum framework organizes complex work around a Product Owner, Scrum Master, and Developers. The Product Owner is accountable for maximizing product value and effective Product Backlog management; the Scrum Master establishes Scrum and supports team effectiveness; Developers create a usable Increment. Sprints last one month or less. Sprint Planning establishes the Sprint Goal and an initial delivery plan, the Daily Scrum inspects progress toward that goal, the Sprint Review examines outcomes with stakeholders, and the Sprint Retrospective improves how the team works. The Sprint Review is not a mandatory release gate, and usable increments may be delivered before it.

For the portal, a Sprint Goal might be enabling customers to check an order’s status without contacting support. Developers select appropriate backlog items, plan implementation, and adapt their Sprint Backlog as they learn. The Definition of Done supplies shared quality expectations: an increment might require integrated code, passing tests, and relevant security checks. Item-specific acceptance criteria describe behavior, such as handling an unknown order number. Do not equate completing coding with completing work if testing and integration remain. Story points are optional, and velocity is neither a Scrum requirement nor a valid productivity ranking across teams. Evaluate progress through usable outcomes, feedback, and movement toward the Product Goal.

Kanban improves delivery by making workflow visible, controlling work in progress (WIP), and using flow evidence to guide changes. A board alone is insufficient: define where work starts and finishes, entry and exit policies, and how new items are pulled when capacity becomes available. A portal team might visualize development, review, testing, and completion, with explicit WIP limits. When testing reaches its limit, starting more development increases inventory rather than delivery. The better response may be helping test existing work, removing blockers, or reducing item size. Limits should encourage collaboration, not simply create departmental queues.

Useful flow measures include throughput, cycle time, WIP, and the age of unfinished items. Little’s Law relates long-run averages: average WIP equals average throughput multiplied by average time in the system. With a consistent measurement boundary, 12 items in progress and throughput of 4 items per week imply an average cycle time of 3 weeks under stable conditions. This does not promise every item will finish in 3 weeks. Use historical cycle-time distributions for probabilistic forecasts, and investigate aging items before they become delivery failures. State whether measurements use calendar or working time, and avoid combining fundamentally different work types without checking whether the comparison is meaningful.

Risk management addresses uncertain events or conditions that could affect objectives; an issue is something that has already occurred. Record risks with causes, potential consequences, owners, triggers, and planned responses. Suppose a supplier delay has an estimated 25% probability and would create $40,000 in additional cost. Its expected monetary value is $10,000, useful as a decision input but not an automatic contingency allocation. An $8,000 mitigation may look attractive, yet its value depends on how much it reduces probability or impact. Consider residual risk, correlated exposures, schedule consequences, and the reliability of the estimates before approving the response.

Change control connects these decisions to the delivery approach. For a baselined predictive project, assess a proposed change’s effects on scope, time, cost, quality, and risk before authorized approval updates the baseline. In adaptive delivery, backlog ordering can evolve, while Sprint Goal protection and external commitments still matter. Effective preparation for PMP certification develops this situational judgment alongside calculations and terminology. Use PMI’s current examination content outline and eligibility guidance, because requirements and exam content can change. Erudex’s course provides a synthesis of governance, analytical techniques, and adaptive frameworks; course completion alone should not be treated as proof of exam eligibility or a guarantee of passing.