Project Management

This deck is designed to give you a solid foundation in the core concepts of project management. It covers the essentials, from understanding what a project actually is and how it differs from day-to-day operations, to the role of the project manager and the widely recognized PMBOK framework. You'll explore the five process groups, key knowledge areas like scope, time, cost, and quality management, and the principles that keep projects on track from start to finish.

The cards are well suited for beginners who are just stepping into the world of project management, as well as students preparing for exams or certifications such as the PMP or CAPM. If you're already working on projects and want a refresher on terminology and structure, this deck can also serve as a handy reference to reinforce what you already know in practice.

To get the most out of your study sessions, try reviewing the cards in small batches rather than cramming everything at once. Spacing your reviews over several days helps move information from short-term memory into long-term retention. As you work through the deck, try connecting each concept to a real project you've experienced, whether that's planning a small event or coordinating a team task at work. This kind of practical link makes the ideas stick and helps you recall them more naturally when you need them.

Project management is the disciplined application of knowledge, skills, tools, and techniques to project activities in order to meet clearly defined requirements. At its core, it is about planning, organizing, and controlling resources so that specific goals are achieved within well-understood constraints. A project is a temporary endeavor, with a defined beginning and end, undertaken to create a unique product, service, or result. This distinguishes it from operations, which are the ongoing, repetitive activities that sustain a business day after day. Because projects are finite and unique, they require deliberate coordination that ordinary operational routines do not demand.

Every project is shaped by the triple constraints, sometimes called the iron triangle: scope, time, and cost. These three dimensions are interdependent, so that increasing scope typically pushes time or cost upward, and tightening the schedule often inflates cost or trims scope. Many practitioners also treat quality as a fourth constraint sitting at the center of the triangle, because it is influenced by how the other three are balanced. The person charged with navigating these trade-offs is the project manager, who plans, executes, and closes the project while leading the team, engaging stakeholders, and handling risks and changes along the way.

To bring consistency to this discipline, the Project Management Institute publishes the Project Management Body of Knowledge, or PMBOK. The PMBOK guide outlines standards, best practices, and terminology, and its current edition organizes content around ten knowledge areas and five process groups. It is also useful to distinguish project management from related concepts. A project delivers a unique outcome; a program coordinates a group of related projects to obtain benefits that none of them could achieve alone; and a portfolio is a collection of projects and programs aligned with strategic objectives. Understanding these levels helps organizations see how individual efforts roll up into broader strategy.

The PMBOK describes five process groups that represent the phases every project moves through, often iteratively rather than strictly once. The Initiating process group is where the project is formally authorized and the project charter is created, with high-level risks, milestones, and stakeholders identified. The Planning process group then develops the project management plan, a master document that bundles subsidiary plans covering scope, schedule, cost, quality, resources, communications, risk, procurement, and stakeholder engagement. Once planning is sufficiently advanced, the Executing process group takes over, coordinating people and resources to deliver the project outputs through activities such as directing work, acquiring and developing the team, managing communications, engaging stakeholders, and procuring goods and services.

Running in parallel with execution, the Monitoring and Controlling process group tracks, reviews, and regulates progress and performance. It is responsible for controlling changes, scope, schedule, cost, quality, and risks, comparing actual results against the plan and triggering corrective action when needed. Finally, the Closing process group formalizes completion by obtaining stakeholder acceptance, releasing resources, archiving documents, and capturing lessons learned so that future projects benefit from what this one revealed.

These process groups draw on ten knowledge areas that describe the subject matter to be managed. Integration Management ties all the other areas together, coordinating activities such as developing the charter, producing the management plan, directing work, managing knowledge, and closing the project. Scope Management ensures that what is and is not included in the project is clearly defined and protected from uncontrolled expansion. Schedule Management, often called Time Management, covers defining activities, sequencing them, estimating durations, building the schedule, and controlling it. Cost Management plans, estimates, budgets, and controls costs to keep the project within its approved budget.

The remaining knowledge areas address the human, informational, and external dimensions of a project. Quality Management plans, manages, and controls quality so that deliverables meet stakeholder expectations, using tools such as Pareto charts and cause-and-effect diagrams. Resource Management covers identifying, acquiring, developing, and managing both the team and physical resources. Communications Management ensures that information is generated, collected, distributed, stored, retrieved, and disposed of in a timely and appropriate way. Risk Management plans responses, identifies, analyzes, prioritizes, implements, and monitors risks, recognizing that risks can be either threats or opportunities. Procurement Management handles the purchase of products, services, or results from outside the organization, including make-or-buy analysis and contract administration. Stakeholder Management identifies and plans engagement with the people and groups whose interests are affected by the project, using tools such as a stakeholder register and an engagement assessment matrix.

Sound planning rests on a few well-established tools that translate the project scope into something schedulers and cost analysts can work with. The Work Breakdown Structure, or WBS, is a hierarchical decomposition of the total scope of work into progressively smaller and more manageable sections called work packages. Once the WBS exists, it becomes the foundation for scheduling, costing, risk analysis, and responsibility assignment. A Gantt chart then visualizes the resulting schedule as a timeline of bars, showing the start and finish dates of tasks, their dependencies, and key milestones. Together, the WBS and Gantt chart turn abstract objectives into a concrete plan that the team can execute and that stakeholders can read at a glance.

Behind many schedules lies the Critical Path Method, or CPM. CPM identifies the longest sequence of dependent tasks in the project, and because the project cannot finish until that longest chain is complete, it determines the minimum project duration. Tasks on the critical path have zero float, meaning any delay in them directly delays the project. Other tasks possess slack, or float, which is the amount of time they can slip without pushing the project finish date. Total float considers the project end, while free float considers only the effect on immediate successor tasks. Where CPM assumes deterministic durations, PERT, the Program Evaluation and Review Technique, uses three time estimates, optimistic, most likely, and pessimistic, to compute an expected duration using the formula \((O + 4M + P)/6\), giving a probabilistic view of the schedule.

When resources are constrained, the Critical Chain Method extends critical path thinking by accounting for resource availability and introducing buffers such as project buffers, feeding buffers, and resource buffers to protect the critical chain from uncertainty. Once a plan is approved, it becomes a baseline: an approved reference version of scope, schedule, or cost against which performance is measured. Baselines can only be changed through formal control processes, which protects the integrity of comparisons over time.

To measure how the project is really doing, managers rely on Earned Value Management, or EVM, which integrates scope, schedule, and cost into a single performance framework. Three core values drive the analysis: Planned Value, or PV, the value of work scheduled to date; Earned Value, or EV, the value of work actually completed; and Actual Cost, or AC, the cost actually incurred for that work. From these, two indices summarize project health. The Schedule Performance Index, computed as \(SPI = EV / PV\), indicates schedule efficiency, with values above 1 meaning the project is ahead of schedule and values below 1 meaning it is behind. The Cost Performance Index, computed as \(CPI = EV / AC\), indicates cost efficiency, with values above 1 meaning the project is under budget and values below 1 meaning it is over budget. Together, SPI and CPI give an early warning that something requires corrective action.

Risk Management ensures that uncertain events, which can affect objectives positively or negatively, are identified, analyzed, prioritized, and addressed. The process begins with planning how risk activities will be conducted, continues through identification and qualitative and quantitative analysis, and culminates in response planning, implementation, and ongoing monitoring. Responses generally fall into four categories: avoid, mitigate, transfer, or accept. To keep this work organized, teams maintain a risk register that documents each risk, its probability and impact, an owner, the chosen response, and the current status. For complex projects, quantitative techniques such as a Monte Carlo simulation can run thousands of scenarios using probability distributions for durations and costs, producing forecasts of completion dates, cost exposure, and the likelihood of meeting targets.

Stakeholder Management runs alongside risk work because the people and groups affected by a project can shape its success as much as any technical decision. Stakeholder analysis identifies relevant parties, assesses their power, interest, and influence, and uses tools such as a power and interest grid or a salience model to develop engagement strategies. A stakeholder register captures who they are, while an engagement assessment matrix tracks their current and desired levels of engagement. With that picture in hand, the project manager can plan how and when to communicate with each stakeholder group.

Resource Management focuses on the people and physical assets needed to do the work. It includes planning how resources will be managed, estimating what is required, acquiring the team and materials, developing team capabilities, managing the team throughout execution, and controlling resources as the project unfolds. A common tool for clarifying who does what is the RACI matrix, in which R stands for Responsible, A for Accountable, C for Consulted, and I for Informed. By assigning exactly one Accountable person per task and clarifying who is Responsible, Consulted, and Informed, the RACI matrix removes ambiguity and prevents important activities from falling through the cracks.

Communications Management ties these threads together by ensuring that project information is generated, collected, distributed, stored, retrieved, and disposed of in a timely and appropriate way. It begins with a communications plan that defines what information stakeholders need, when they need it, in what format, and through which channels. During execution, communications are actively managed, and their effectiveness is monitored and adjusted as the project evolves.

Beyond the universal tools, organizations choose a methodology, or overall approach, that shapes how phases are sequenced and how teams collaborate. The Waterfall methodology is a linear, sequential approach in which phases such as requirements, design, implementation, testing, deployment, and maintenance are completed one after another. Waterfall works well when requirements are fixed and well understood upfront, because its structure rewards thorough planning and clear handoffs between phases. In contrast, Agile project management is iterative and flexible, emphasizing collaboration, customer feedback, and the delivery of working outputs in short cycles. Agile values responding to change over following a rigid plan, and it welcomes evolving requirements even late in the project.

The philosophy behind Agile is captured in the four core values of the Agile Manifesto. The first places individuals and interactions over processes and tools, recognizing that people ultimately deliver value. The second values working software, or working outputs more generally, over comprehensive documentation, because tangible results provide the clearest evidence of progress. The third prioritizes customer collaboration over contract negotiation, encouraging ongoing dialogue with the people the project serves. The fourth favors responding to change over following a plan, since markets, needs, and discoveries shift over time.

Scrum is the most widely used Agile framework. It defines three roles: the Product Owner, who manages the Product Backlog, prioritizes features based on value, and represents stakeholders and customers; the Scrum Master, who facilitates Scrum processes, removes impediments, coaches the team on Agile practices, and safeguards adherence to Scrum rules without acting as a traditional manager; and the Development Team, which does the work of delivering increments. Scrum also defines events such as the Sprint, Daily Scrum, Sprint Review, and Sprint Retrospective, and artifacts such as the Product Backlog, Sprint Backlog, and Increment. A Sprint is a time-boxed iteration, typically two to four weeks long, during which the team builds a potentially shippable product increment, beginning with planning and ending with a review and a retrospective for continuous improvement.

Two practical tools support Scrum teams. Story points estimate the relative effort of user stories using a Fibonacci-like scale such as 1, 2, 3, 5, and 8, taking into account complexity, risk, and effort rather than hours. Velocity, the sum of story points a team completes in a Sprint, is then used to forecast future Sprints and plan releases, helping teams steadily improve predictability. Outside Scrum, Kanban offers a visual workflow management method based on a board with columns such as To Do, In Progress, and Done. By limiting work in progress, Kanban improves flow and enables continuous delivery. Closely related is Lean project management, which focuses on maximizing value by eliminating waste such as overproduction, waiting, and defects, using techniques like value stream mapping, just-in-time delivery, and continuous improvement, or Kaizen.

Every project needs formal mechanisms to start, to change, and to end. The project charter is the document that formally authorizes a project. It names the project manager, defines high-level objectives and scope, identifies key stakeholders, and clarifies the manager's authority level, and it is typically issued by the sponsor. With the charter in hand, the project begins. As work unfolds, scope creep, the uncontrolled expansion of project scope without corresponding adjustments in time, cost, or resources, becomes one of the most common threats. To guard against it, organizations use a formal change control process in which proposed changes to baselines for scope, schedule, or cost are reviewed, evaluated, approved, or rejected, often by a group called the Change Control Board.

Procurement Management handles the acquisition of products, services, or results from outside the organization and covers planning procurements, conducting them, controlling them, and closing them. A key early decision is whether to make or buy, after which the contract type sets the financial arrangement. Common contract types include Fixed-Price agreements, which suit well-defined scopes because the seller bears much of the cost risk; Time and Materials contracts, which charge for labor hours plus materials and are useful when scope is unclear; and Cost-Reimbursable contracts, which reimburse the seller's costs and are appropriate for uncertain or evolving scopes. Beyond PMBOK, some organizations adopt structured methodologies such as PRINCE2, or Projects IN Controlled Environments, a process-based approach built on seven principles, themes, and processes that emphasizes defined roles, staged progress, and continuous business justification.

Closure is more than marking a task complete. The Closing process group finalizes all activities, obtains stakeholder acceptance of the deliverables, releases project resources, archives documents, and, importantly, captures lessons learned. Lessons learned are the documented experiences and insights gained during the project, both positive and negative, recorded throughout the effort and consolidated at closure. They feed into organizational knowledge so that future projects can repeat what worked and avoid what did not. In this way, even a project that ends poorly can leave behind knowledge that improves the next one, closing the loop between execution and learning.