The Project Management Handbook: Principles, Practices & Frameworks Table of Contents 1. Chapter 1: Foundations of Project Management & Organizational Context 2. Chapter 2: Project Initiation, Scope Definition & Stakeholder Dynamics 3. Chapter 3: Project Planning, Budgeting, Scheduling & Risk Management 4. Chapter 4: Agile Frameworks, Scrum & Adaptive Delivery 5. Chapter 5: Quality Governance, Performance Evaluation & Project Closeout 6. Master Comprehensive Glossary (Alphabetical Index) Chapter 1: Foundations of Project Management & Organizational Context 1.1 What is Project Management? A project is a unique endeavor that typically involves a specific set of deliverables and a sequence of tasks executed to reach a defined outcome. Project management refers to applying knowledge, skills, tools, and techniques to project activities to satisfy requirements. Every project moves through a structured project life cycle, traditionally consisting of four core phases: 1. Initiation: The launchpad phase where goals, deliverables, resources, budget, and key people are identified. 2. Planning: Establishing processes, using productivity tools, and creating documentation such as schedules, timelines, and budgets. 3. Executing: Carrying out the actual work required to achieve the project goals. 4. Closing: Evaluating project performance, celebrating accomplishments, and finalizing project records. A project manager (PM) guides projects from inception to completion, acting as a leader who leverages organizational and interpersonal skills. When an individual oversees multiple interrelated projects across business programs or products, they serve as a program manager. Organizations often support these efforts through a Project Management Office (PMO), an internal department responsible for establishing and maintaining project standards. 1.2 Methodologies & Delivery Models A project management methodology provides guiding principles and operational processes throughout the life cycle. Major delivery models include: ● Waterfall (Linear): A sequential approach where tasks and phases are structured in strict order; preceding phases must conclude before the next begins. ● Agile (Iterative): An adaptive approach where project phases overlap, and work is delivered incrementally through repeated cycles (iterations). ● Lean & Six Sigma: Lean focuses on eliminating operational waste. Six Sigma emphasizes reducing

defects and variability by enforcing consistent quality processes. When merged into Lean Six Sigma, teams rely on the DMAIC roadmap: Define, Measure, Analyze, Improve, and Control. 1.3 Organizational Structures & Culture Projects operate within broader structural boundaries: ● Classic (Functional) Structure: A traditional, top-down hierarchy led by functional managers heading specific departments. ● Matrix Structure: A grid-like reporting format where project personnel report both to direct departmental functional leads and to project/program managers. A company's operational environment is shaped by corporate governance (the system determining how goals and objectives are achieved) and organizational culture (shared values, norms, and collective personality). Understanding these systems helps team members develop ownership—taking personal accountability for task success. 1.4 Leadership & Interpersonal Dynamics Project leaders frequently operate without formal organizational authority over team members. Influencing without authority requires strong interpersonal skills such as active communication, conflict resolution, and motivational insight. Projects also rely on change agents, who focus on internal organizational effectiveness and guide staff through structural transitions. Chapter 2: Project Initiation, Scope Definition & Stakeholder Dynamics 2.1 Initiating the Project The initiation phase lays the foundation for all upcoming work. A project typically begins with a project proposal and a formal business case, which outlines why the investment should be undertaken. Key elements defined during initiation include: ● Project Goal & Success Criteria: Establishing what the effort will achieve and the criteria used to determine if it was successful. ● Project Charter: The foundational document that formally details the project’s scope, constraints, and core objectives. ● Cost-Benefit Analysis: Weighing projected monetary and organizational returns against expected costs. 2.2 Scope Management & The Triple Constraint Project boundaries are defined by scope—the agreed-upon parameters of what will and will not be executed. ● In-Scope vs. Out-of-Scope: Tasks directly tied to achieving the baseline objectives are in-scope; extraneous tasks are out-of-scope. ● Scope Creep: The uncontrolled expansion of project scope without corresponding adjustments to time, cost, or resources. ● Triple Constraint: The fundamental balance among scope, time, and cost. Adjusting one

boundary inevitably impacts the other two. 2.3 Stakeholder Identification & Governance Stakeholders represent any individuals or groups affected by or invested in the project outcome: ● Key/Primary Stakeholders: Individuals who benefit directly from the deliverables or wield high decision-making power (including the project sponsor, who is ultimately accountable for delivering business benefits). ● Secondary Stakeholders: Individuals indirectly impacted by project changes or outcomes. ● Steering Committee: The high-level governing body holding the organizational authority to authorize budget, scope, and timeline changes. To organize oversight, project managers use stakeholder analysis and the Power-Interest Grid to map influence against interest. Stakeholder Category Level of Influence DOCX+ 1 Level of Interest DOCX+ 1 Strategic Engagement Approach DOCX+ 2 Key Players High High Manage closely, engage regularly, secure buy-in Context Setters High Low Keep satisfied, consult on major changes Informed Champions Low High Keep adequately informed, leverage interest Monitored Group Low Low Monitor with minimal effort, communicate as needed Roles are clearly defined using a RACI Chart, delineating who is Responsible, Accountable, Consulted, and Informed for each project deliverable. Chapter 3: Project Planning, Budgeting, Scheduling & Risk Management 3.1 Work Breakdown & Task Sequencing The planning phase translates project scope into actionable execution structures. ● Work Breakdown Structure (WBS): A hierarchical breakdown that deconstructs milestones,

summary tasks, and subtasks. ● Dependencies: Relationships between tasks that dictate sequence. ○ Finish-to-Start (FS): Task A must finish before Task B can begin. ○ Finish-to-Finish (FF): Task A must finish before Task B can finish. ○ Start-to-Start (SS): Task B cannot begin until Task A begins. ○ Start-to-Finish (SF): Task B cannot finish until Task A begins. 3.2 Critical Path Method (CPM) & Scheduling The Critical Path represents the sequence of mandatory tasks that determines the absolute shortest duration required to complete the project. Any delay to a critical path task directly delays the completion date. ● Float (Slack): The amount of time a non-critical task can slip before impacting the scheduled finish date. ● Forward Pass & Backward Pass: Techniques used across dependency networks to determine earliest start/finish dates and latest allowable start/finish dates. ● Buffers: Strategic time added to specific tasks (task buffer) or to the project's overall conclusion (project buffer) to absorb schedule variance caused by optimism bias or the planning fallacy. 3.3 Cost Engineering & Budget Baseline A project budget represents the total financial resources required to execute planned tasks. It encompasses direct costs (labor, project-specific materials), indirect costs (overhead, general utilities), CAPEX (capital expenditures for long-term assets), and OPEX (day-to-day operating expenses). ● Bottom-Up Estimation: Estimating costs for each individual subtask and rolling them up into a comprehensive total. ● Reserves: Budgets typically reserve contingency reserves for identified, quantified risks, and management reserves for unforeseen issues. ● Baseline a Budget: Locking the approved financial expenditure plan into a Project Management Baseline (PMB) to measure and compare spending over time. 3.4 Risk Management A risk is an uncertain event that, if it occurs, impacts project goals; an issue is an active, realized problem. Teams maintain a Risk Register to document: 1. Probability & Impact: Measuring likelihood against the severity of consequences. 2. Root Cause Analysis: Investigating underlying causes using visual tools such as Cause-and-Effect (Fishbone) Diagrams or Decision Trees. 3. Single Points of Failure: Vulnerabilities that, if disrupted, could stall the entire project. Chapter 4: Agile Frameworks, Scrum & Adaptive Delivery 4.1 The Agile Mind-set Designed to manage volatile, uncertain, complex, and ambiguous (VUCA) environments, the Agile

approach prioritizes rapid, iterative delivery over rigid, linear roadmaps. Guided by the Agile Manifesto, agile projects focus on direct collaboration, working deliverables, and responsiveness to change. 4.2 Scrum Framework Scrum structures team delivery around short, fixed iterations called Sprints (typically 1 to 4 weeks long). ● The Three Pillars of Scrum: ○ Transparency: Work, decisions, and progress must be clearly visible to those responsible for outcomes. ○ Inspection: Regular check-ins against Sprint and Product Goals to identify deviations. ○ Adaptation: Adjusting processes or backlog items promptly to prevent further issues. ● Core Scrum Roles: ○ Product Owner (PO): Maximizes product value and manages the Product Backlog. ○ Scrum Master: Facilitates Agile processes, removes team blockers, and coaches the team on Scrum values. ○ Development Team: Cross-functional professionals who build the releasable increment. ● Scrum Ceremonies (Events): ○ Sprint Planning: Setting the Sprint Goal and selecting items for the Sprint Backlog. ○ Daily Scrum (Stand-up): A 15-minute daily coordination meeting to inspect progress. ○ Sprint Review: A collaborative demonstration of the newly finished product increment. ○ Sprint Retrospective: An internal team meeting focused on process evaluation and continuous improvement. 4.3 Agile Estimation & Visual Management ● User Stories & I.N.V.E.S.T.: Requirements are drafted as user stories, evaluated to ensure they are Independent, Negotiable, Valuable, Estimable, Small, and Testable. ● Relative Sizing: Agile teams estimate complexity using Story Points or T-shirt Sizing rather than absolute hours. ● Visual Work Tracking: Using Kanban Boards to display workflow limits (WIP limits) and tracking team output through Burndown Charts and Velocity metrics. Chapter 5: Quality Governance, Performance Evaluation & Project Closeout 5.1 Quality Management Project quality balances customer expectations with technical compliance. ● Quality Planning: Identifying which standards apply and defining how the project will meet them. ● Quality Assurance (QA): Process-oriented activities that verify deliverables are trending toward high-quality standards. ● Quality Control (QC): Product-oriented techniques used to identify and correct defects in finished deliverables. 5.2 Performance Measurement (Earned Value & 3-Point Estimation)

Project health is evaluated by comparing actual performance to planned baselines. ● Earned Value Management (EVM): ○ $\text{Cost Variance (CV)} = \text{Earned Value} - \text{Actual Cost}$ ○ $\text{Schedule Variance (SV)} = \text{Earned Value} - \text{Planned Value}$ ● Cost Performance Index (CPI): Ratio of earned work value against actual costs incurred. ● Schedule Performance Index (SPI): Ratio of earned work value against scheduled plans. ● Quantitative Estimation Models (PERT & Triangular): Using Optimistic ($O$), Most Likely ($M$), and Pessimistic ($P$) projections: $$\text{Beta Distribution (PERT)} = \frac{O + 4M + P}{6}$$ $$\text{Triangular Distribution} = \frac{O + M + P}{3}$$ 5.3 Project Closeout & Knowledge Handover The closing phase ensures formal completion, stakeholder alignment, and organizational learning. ● Project Closeout Report: A historical record compiling project performance data, outcomes, and elements for future managers. ● Lessons Learned & Retrospectives: Structured documentation detailing what worked, what failed, and practical improvements for future projects. ● Impact Reporting & Executive Summaries: Communicating realized value, business return on investment (ROI), and core metrics through clear storytelling and concise summary artifacts. Master Comprehensive Glossary (Consolidated Alphabetical Index) A  Abandoned project: A project in which inadequate handoff or transition on the project deliverables occurs.  Acceptance criteria: The checklist or pre-established standards/requirements used to determine whether a product, service, process, or user story is satisfactorily complete.  Accessible: Something that is easily used, accessed, or adapted for use by people experiencing disabilities.  Accountability: The state of being answerable for decisions, outcomes, and actions associated with a project.  Action item: A task that needs to be completed.  Adaptation: Adjusting project directions, products, or processes to minimize future variance; one of the three pillars of Scrum.  Adoption: The process by which customers successfully accept, use, and integrate a delivered product or service.  Adoption metrics: Metrics that indicate whether or not a product, service, or process is accepted and used.  Agile: An adaptive project management approach characterized by overlapping phases, short iterations, and continuous collaboration.  Agile Manifesto: The foundational document outlining four key values and 12 principles that define Agile delivery.  Air cover: Support for and protection of a team in the face of out-of-scope requests or criticism from leadership.  Alignment: Reaching operational agreement and consensus between two or more parties.

 Ambiguity: A state in which conditions, scope boundaries, or root causes are unclear or open to multiple interpretations.  Analytics: The process of answering business questions, discovering relationships, and predicting outcomes based on the analysis of data.  Artifact: A project management document, template, or tangible record produced during the project life cycle.  Asana: A digital work management and collaboration platform used to coordinate tasks, assign responsibilities, and monitor workflows.  Authority: An individual's organizational mandate to make binding decisions that commit resources and influence business operations. B  Backward pass: A critical path scheduling technique that works backward from a project’s end date to calculate latest allowable start and finish dates.  Backlog refinement: The ongoing activity of estimating, grooming, and prioritizing user stories and tasks in the Product Backlog.  Bad compromise: A situation that occurs when two parties settle on a so-called solution but the end product still suffers.  Bar chart: A type of chart that uses color and length to compare categories in a data set; useful for comparing values.  Barrier: An impediment, obstacle, or condition that hinders project workflow or progress.  Baseline: An approved, fixed reference point—encompassing scope, schedule, or budget—used to evaluate actual project execution.  Baseline a budget: Formally locking a reference spending projection to compare expenditures against actual costs.  Benchmark / Benchmarking: A recognized point of reference or standard against which project performance and processes are assessed.  Benefits: The anticipated positive gains, value, or financial returns generated by a project.  Beta distribution (PERT): A weighted three-point estimation formula that places fourfold weight on the "most likely" case: $(O + 4M + P) / 6$.  Bottom-up approach: Estimating total project duration or budget by analyzing and summing every lower-level work component in the WBS.  Budget: The estimated total financial resources allocated to fulfill project deliverables.  Budget pre-allocation: A scenario where fixed budget figures are mandated before comprehensive project planning occurs.  Budget risk: The potential that final project costs will exceed baseline projections due to scope changes or planning gaps.  Buffer: Controllable time added to tasks or timelines to absorb unforeseen interruptions or variations.  Bug: A technical issue.  Burndown chart: A visual/line chart showing work completed over time relative to remaining deliverables in a sprint or project; useful for a granular view of tasks.  Business agility: Applying flexible, iterative Agile principles across broader enterprise management domains.  Business case: The foundational rationale justifying the organizational investment in a project.  Business collaboration: Active, continuous partnership with clients and stakeholders to quickly adapt to incoming business data.  Buzzword: An industry term or phrase that becomes widely popular for a period of time. C

 Capacity: The maximum workload individuals or teams can sustainably execute within a given timeframe.  Capacity planning: Allocating team resources to tasks to confirm that requirements do not exceed team capabilities.  CAPEX (Capital Expenses): Expenditures incurred to purchase long-term physical or organizational assets that generate future business value.  Case studies: In-depth, contextual assessments of a specific business situation, project, or organizational change.  Cash flow: The movement of cash into and out of a project over specific operational cycles.  Cause-and-effect diagram: A visual troubleshooting tool, also called a fishbone diagram, used to trace problems to their potential root causes.  Change: Anything that alters or impacts the tasks, structures, or processes within a project.  Change agent: An internal leader or facilitator who guides organizations through transitions to boost effectiveness.  Change control board: A designated group that reviews, approves, or rejects proposed baseline scope or specification changes.  Change log: A record of all notable changes on a project.  Change management: Structured frameworks designed to guide people through adopting new processes, systems, or products.  Character: The qualities or features that make up and distinguish a person, like honesty, integrity, and kindness.  Classic structure: A conventional, functional organizational structure organized by strict top-down reporting hierarchies.  Closing: The concluding life-cycle phase centered on post-project review, administrative closeout, and celebrating team accomplishments.  Coaching: A supportive, two-way leadership style aimed at developing team capabilities, problem-solving, and autonomy.  Coalition: A temporary alliance of teams or organizational groups established to achieve shared business outcomes.  Collaboration: People working together on an activity.  Collaboration tools: Digital applications that enable communication and work coordination across distributed project teams.  Complexity: The degree of interrelatedness, organizational politics, and dependencies influencing a project environment.  Conditional formatting: A spreadsheet feature that dynamically changes cell colors or text formatting based on defined rules.  Confidence level rating: An index reflecting an estimator's certainty regarding the accuracy of time or cost estimates.  Confirmation bias: A type of data bias that refers to the tendency to search for information that confirms preexisting beliefs.  Conger’s four steps: Jay A. Conger's persuasion framework focused on establishing credibility, framing for common ground, providing evidence, and connecting emotionally.  Constructive criticism: Targeted, actionable feedback intended to help the recipient improve a specific deliverable or process.  Contingency budget: Financial funds set aside within a budget to address unforeseen costs or known risks.  Contingency reserves: Budgeted amounts reserved specifically to mitigate identified risks that arise during execution.

 Continuous improvement: An ongoing effort to improve products or services; begins with recognizing when processes and tasks need to be created, eliminated, or improved.  Continuous integration and continuous refactoring: Extreme Programming practices where code changes are integrated and streamlined multiple times per day.  Contract work: Specialized assignments fulfilled by independent contractors or third parties on a project basis.  Control: An experiment or observation designed to minimize the effects of variables.  Corporate governance: The rules, policies, and structures an enterprise uses to guide its operations and achieve its goals.  Cost-benefit analysis: Evaluating expected operational and financial gains against anticipated project expenses.  Cost of quality: The total investment required to prevent defects and ensure deliverables meet specifications.  Cost performance index (CPI): An EVM performance metric calculated by dividing Earned Value by Actual Cost.  Cost variance (CV): The difference between actual cost and budgeted cost; or mathematically, $CV = EV - AC$.  Costs: The financial resources, materials, equipment, and labor required to complete project work.  Critical user journey: The sequence of steps a user follows to accomplish tasks in a product.  Cross-functional team: A team composed of professionals from diverse functional areas collaborating toward a shared outcome.  CSV file: A file format storing tabular information in plain text separated by commas (Comma Separated Values).  Culture mapping: A diagnostic method used to assess company values, norms, and behaviors to predict how change will be received.  Customer satisfaction score: A metric that indicates how well the project delivered what it set out to do and how well it satisfies customer and stakeholder needs.  Customers: The target beneficiaries, internal users, or external buyers of the project's finished deliverable.  Cynefin framework: A conceptual framework used to diagnose operational complexity across five contexts: clear, complicated, complex, chaotic, and disorder.  C-Suite: The senior executive leadership tier of an organization (e.g., CEO, CFO, COO). D  Daily Scrum: A timeboxed 15-minute daily synchronization meeting for Scrum teams to review progress toward the Sprint Goal.  Dashboard: A type of user interface—typically a graph or summary chart—that provides a snapshot view of a project’s progress or performance.  Data: A collection of facts or information; the numbers and feedback available about different aspects of a project.  Data analysis: The collection, transformation, and organization of data to draw conclusions, make predictions, and drive informed decision-making.  Data bias: A type of error that is influenced by one’s inherent beliefs.  Data ethics: The well-founded standards of right and wrong that dictate how data is collected, shared, and used.  Data privacy: The act of protecting a data subject’s information and activity any time a data transaction occurs.

 Data validation: A spreadsheet feature that restricts cell inputs by enforcing predefined options or dropdown lists.  Data visualization: A graphical representation of information to facilitate understanding.  Data-driven improvement frameworks: Techniques used to make decisions based on actual data.  Decision tree: A visual diagram mapping potential decisions alongside their probabilities, resource costs, and projected consequences.  Definition of Done (DoD): A mutually agreed-upon checklist of quality and technical criteria that a user story or increment must meet to be considered complete.  Delegation: Assigning tasks and decision-making responsibilities to team members best suited to complete them.  Deliverable: A tangible, verifiable outcome, product, or result produced to satisfy project requirements.  Dependability: A quality indicating team members are reliable and complete their work on time.  Dependencies / Dependency: Tasks, activities, or milestones that are reliant on one another, dictating execution sequence.  Dependency graph: A network diagram visually illustrating the flow and sequential constraints among project activities.  Dependency management: The process of managing interrelated tasks and resources within a project to ensure that the overall project is completed successfully, on time, and on budget.  Development Team: The cross-functional team members responsible for building the product increment during a Scrum sprint.  Deviation: Anything that alters the original course of action.  DevOps: A methodology combining software development and IT operations to shorten delivery cycles and maintain reliability.  Direct costs: Expenditures directly tied to producing a specific project deliverable.  Disciplined Agile Delivery (DAD): A hybrid scaling framework integrating practices from Kanban, Scrum, XP, and Lean.  Discretionary dependencies: Dependencies that could occur on their own, but the team saw a need to make those dependencies reliant on one another.  Diversity: The set of differences each individual possesses, whether visible or invisible, that gives them a unique perspective on the world and their work.  DMAIC: The five-phase Lean Six Sigma continuous improvement roadmap: Define, Measure, Analyze, Improve, and Control.  Docs: A digital, collaborative cloud word-processing application.  Domain knowledge: Deep specialized expertise in a particular industry, subject matter, or technical field.  Duration: The amount of time it takes to complete or produce something. E  Earliest start date: The earliest calendar date an activity can initiate within a critical path network.  Earned value management (EVM): A methodology that integrates scope, schedule, and cost metrics to assess overall project progress.  Edge case: Rare outliers that the original requirements of the project didn’t account for; deals with the extreme maximums and minimums of parameters.  Effective communication: Transparent, timely information sharing that keeps stakeholders and team members aligned.  Effort estimate / Effort estimation: Projecting the net active labor hours required to complete a task, excluding wait times.

 Empathy: The interpersonal ability to understand and connect with the feelings, viewpoints, and situations of others.  Empiricism: The philosophy that knowledge stems from concrete experience and decisions should be based on observed data.  Engagement: The depth, frequency, and consistency of stakeholder or user participation over time.  Engagement metrics: Metrics that indicate the degree to which a product or service is used—the frequency of use, amount of time spent using it, and the range of use.  Epic: A large body of work or broad functional area that can be broken down into several smaller user stories.  Escalation / Escalation paths: Protocols and actions for enlisting higher-level leadership to remove obstacles, clarify priorities, and validate next steps.  Ethical leadership: A form of leadership that promotes and values honesty, justice, respect, community, and integrity.  Ethical trap: A set of pressures or circumstances that can lead an individual to make unethical professional decisions.  Evaluation: Assessing performance data against established criteria to determine effectiveness and project success.  Evaluation indicator: Specific metrics gathered to address overarching project evaluation questions.  Evaluation presentation: A formal presentation assessing project performance against established operational benchmarks.  Evaluation question: A guiding question designed to investigate the success, value, or efficiency of a project.  Executing: The project life-cycle phase focused on coordinating people and resources to complete planned work.  Executive summary: A high-level introductory summary outlining a report's core purpose, findings, and results.  Expressiveness: Refers to one’s ability to communicate with others.  External dependencies: Tasks that are reliant on outside factors, like regulatory agencies or other projects.  Extreme Programming (XP): An agile software methodology focused on frequent releases, code quality, and engineering excellence. F  Feedback mechanism: A structured channel, such as a retrospective or survey, used to collect stakeholder and team feedback.  Feedback survey: A survey in which users provide feedback on features of a product that they like or dislike.  Finish-to-finish (FF): A dependency relationship where a successor task cannot finish until its predecessor task finishes.  Finish-to-start (FS): A dependency relationship where a successor task cannot begin until its predecessor task finishes.  Fishbone diagram: A visual diagram (also called a cause-and-effect diagram) used to trace problems back to underlying root causes.  Five values of Scrum: The guiding behavioral values of Scrum: commitment, courage, focus, openness, and respect.  Fixed contract: A legal agreement where compensation is tied to delivering predefined milestones or products.

 Fixed costs: Project expenses that remain constant regardless of output volume or task duration.  Fixed start date: A non-negotiable date by which a project task or phase must begin.  Float: The duration an activity can be delayed without delaying subsequent tasks or the project completion date; also known as slack.  Floating task: An unconstrained task whose minor delays will not affect project milestones or delivery dates.  Flow: A continuous delivery principle in Kanban aimed at maximizing efficiency and minimizing work delays.  Flowchart: A schematic diagram illustrating the sequence of steps within a system, process, or workflow.  Force majeure: An unforeseen circumstance that prevents someone from fulfilling a contract due to a major crisis.  Forecast / Projection: An evidence-based estimate or prediction of future schedule, resource, cost, performance, or quality outcomes based on current trends.  Forward pass: A critical path method technique that calculates the earliest possible start and finish dates for project tasks.  Function: A built-in spreadsheet calculation used to process and analyze data.  Functional manager: The department head who oversees administrative and operational activities within a classic organization.  Functional organizations: Companies structured around specialized functional departments (also called Classic organizations). G  Gantt chart: A project-tracking visual and horizontal bar chart illustrating task breakdowns, dependencies, assignees, and timeline durations.  Good product hygiene: Consistently organizing, archiving, and maintaining central project documentation for future access.  Governance: The leadership framework, policies, and decision-making structures that enforce accountability across an organization. H  Happiness metrics: Metrics that relate to different aspects of the user's overall satisfaction with a product or service.  Header: The top row or cell in a data table that identifies the content of a column.  Headline: The one-sentence main point that illustrates a slide.  High-level risk: A significant project risk capable of causing severe damage, requiring direct escalation and mitigation plans.  History: Refers to the level of personal history between oneself and another person. I  Impact: The severity of consequences a project faces if an identified risk occurs; or the belief that the results of one’s work matter and create change.  Impact report: A presentation or deck outlining the value, ROI, and measurable improvements delivered by a project to key stakeholders.  Inclusive leadership: A form of leadership where everyone’s unique identity, background, and experiences are respected, valued, and integrated into how the team operates.  Inclusivity: The practice or policy of including people who might otherwise be excluded or marginalized.  Incremental: Delivering work in small, functional pieces that build upon each other toward the complete solution.

 Indirect costs: Overhead and shared operational expenses that cannot be tied directly to a single project deliverable.  Influence: The level of authority, power, and political capital a stakeholder holds over project outcomes.  Influencer: A leader capable of motivating stakeholders and team members to embrace meaningful change.  Influencing: The ability to alter another person’s thinking or behaviors.  Influencing statement: A conversation opener that sets a person up for success with their audience.  Influencing without authority: Guiding, persuading, and directing cross-functional teams without having direct managerial power over them.  Infographic: A visual representation of information or data intended to present information quickly and clearly.  Information: An organizational source of power that refers to one’s level of access and control over information.  Inherent risk: The raw, unmitigated exposure of a risk, calculated by its combined probability and impact.  Initiation: The foundational project life-cycle phase that defines the high-level scope, objectives, budget, and business justification.  In-scope: Work, features, and activities explicitly agreed upon as part of the project plan.  Inspection: A core Scrum pillar requiring regular reviews of work increments to catch variances and defects early.  Intangible benefits: Value delivered that cannot be quantified directly, such as team morale or brand perception.  Intangible costs: Non-monetary losses resulting from project issues, such as lowered morale or damaged brand credibility.  Interest: The degree to which a stakeholder is impacted by or cares about project operations and final deliverables.  Internal dependencies: The relationship between two tasks within the same project.  Internship: A temporary position providing practical, hands-on industry experience.  Interpersonal skills: Behavioral attributes—such as active listening, empathy, and negotiation— that facilitate team collaboration.  Interpretation bias: A type of data bias that refers to the tendency to always interpret ambiguous situations as either negative or positive.  I.N.V.E.S.T.: A mnemonic guide for evaluating user stories: Independent, Negotiable, Valuable, Estimable, Small, and Testable.  Issue: A current, active, and real operational problem that may affect the ability to complete a task.  Iterative: Developing solutions through repeated, cyclical phases of design, testing, and continuous feedback. K  Kanban: A visual project management system using boards, cards, and column WIP limits to manage workflow and identify bottlenecks.  Kanban board: A physical or digital board tracking work items as they move through columns such as "To Do," "In Progress," and "Done".  Key accomplishments: The section of a project report summarizing the milestone achievements and deliverables that drove success.

 Key performance indicator (KPI): A measurable value that demonstrates how effective a company is at achieving business objectives.  Key results: The quantifiable metrics used within the OKR framework to measure whether an objective has been reached.  Key stakeholders: Highly influential individuals who have a substantial stake in a project's trajectory and outcomes.  Kickback: An illegal payment or bribe provided to an official in exchange for securing favorable business or contracts.  Knowledge: Refers to the power drawn from one’s expertise in certain subjects, unique abilities and skill sets, and ability to learn new things.  Knowledge management: Strategies and systems used to collect, organize, and store organizational lessons and documentation for future use. L  Land: The successful completion of a project based on predefined performance targets and success criteria.  Large-Scale Scrum (LeSS): A framework that scales Scrum principles across multiple teams working on a single product.  Latest start date: The latest possible date a task can begin without delaying the overall project schedule.  Launch: Delivering the project's completed product, service, or system to its end users.  Lean: A continuous improvement methodology that focuses on eliminating operational waste and maximizing value.  Lean Six Sigma: A methodology that combines Lean's waste elimination with Six Sigma's defect- reduction processes.  Legend: The bottom or side section of a chart that gives a small description of each section.  Lessons learned: Documented reflections on successes and setbacks used to improve future project work.  Leverage experts: Consulting subject matter experts to gain specialized insights that improve planning and execution.  Line chart: A type of chart that displays information as a series of data point markers; helpful for showing trends and behaviors over set periods of time or overall.  Linear: Sequential project execution where each phase must finish before the subsequent phase can begin.  Low-level risk: A risk characterized by minor consequences or low probability, requiring basic monitoring rather than immediate escalation. M  Management reserves: A designated budget reserve set aside to address unforeseen risks outside the established risk register.  Managing: Overseeing day-to-day operations, assigning work, resolving blockers, and keeping team performance aligned with goals.  Mandatory dependencies: Tasks that are legally or contractually required.  Materials: Tangible goods, supplies, hardware, or physical inputs required to execute project tasks.  Matrix structure: An organizational hierarchy where staff report both to a direct functional manager and to one or more project leaders.  Medium-level risk: A notable risk with moderate probability and impact that requires ongoing communication and mitigation plans.

 Metric: A quantifiable measurement used to track and assess a business objective, performance, progress, or quality.  Micromanaging: Closely monitoring and directing team tasks to an excessive degree, often reducing autonomy and trust.  Milestone: An important checkpoint within the project schedule that indicates progress and usually signifies the completion of a major deliverable or phase.  Minimum viable product (MVP): A functional version of a product containing only the core features needed to gather feedback from early adopters.  Mission: A clear, enduring statement defining an organization's core purpose, scope, and target audience.  Most likely estimate: A time or cost projection based on typical, realistic working conditions.  Multiple choice question: A closed-ended survey question offering a fixed set of answers.  Mutual benefit: An outcome in which all participating parties gain value.  Mutually beneficial agreement: A negotiated settlement where terms provide clear advantages to everyone involved. N  Need-to-know basis: The practice of sharing information only with individuals who require it to perform their work.  Network: The people one is connected with professionally and personally.  Network diagram: A visual chart showing tasks arranged in sequential order based on their project dependencies.  Never-ending project: A project in which the project deliverables and tasks cannot be completed.  Non-disclosure agreement (NDA): A binding legal contract that prevents the unauthorized disclosure of confidential project information. O  Objective: The ambitious, qualitative goal component of an OKR defining what the organization aims to achieve.  Objective criteria: Neutral standards—such as regulations, market value, or benchmark data— used to guide balanced decision-making.  Objectives and key results (OKRs): A goal-setting framework combining an ambitious objective with measurable key results.  Observer bias: A type of data bias that refers to the tendency for different people to observe different things.  One-pager: A concise, single-page summary document outlining a project's goals, scope, and current status.  On-time completion rate: A productivity metric that helps illustrate to clients and stakeholders how the project is progressing and when they can expect certain deliverables to be ready.  Open-ended question: A question format requiring descriptive, detailed responses rather than simple one-word answers.  OPEX (Operating Expenses): Day-to-day operational costs required to maintain standard business activities.  Optimism bias: A cognitive bias where people underestimate the probability of facing negative events or delays.  Optimistic estimate: A best-case estimation that assumes ideal operating conditions with no unexpected setbacks.  Organizational culture: Shared values, beliefs, communication styles, and workplace norms that define a company's working environment.

 Organizational structure: The formal hierarchy, reporting relationships, and division of authority within an enterprise.  Out-of-scope: Elements, features, or tasks explicitly excluded from a project plan.  Overhead: General business and administrative expenses that cannot be tied directly to a single deliverable.  Ownership: The personal accountability team members take for delivering their assigned tasks successfully. P  Pair Programming: An XP engineering practice where two software developers work collaboratively at a single workstation.  Parallel tasks: Work activities that can be performed simultaneously without waiting on shared dependencies.  PDCA: A four-step process that focuses on identifying a problem, fixing the issue, assessing whether the fix was successful, and fine-tuning the final fix; stands for Plan, Do, Check, and Act.  Personally identifiable information (PII): Data that can directly identify or locate a specific individual, requiring strict privacy safeguards.  Pessimistic estimate: A worst-case estimation assuming substantial delays, risks, and operational complications.  Pie chart: A type of chart divided into sections that each represent a portion of a whole; useful for making comparisons.  Pivot table: A data processing tool used to summarize, analyze, and spot trends across large spreadsheet datasets.  Planning / Planning phase: The project life-cycle stage dedicated to finalizing scopes, establishing schedules, organizing resources, building budgets, and creating risk management plans.  Planning fallacy: The tendency to underestimate task duration, associated costs, and potential project risks.  Portfolio: A collection of programs and projects across a whole organization.  Power grid / Power-interest grid: A 2x2 matrix that categorizes stakeholders based on their influence and interest to tailor communication strategies.  Primary stakeholders / Key stakeholders: People directly invested in or affected by a project's final deliverables.  Probability: The estimated likelihood that an identified risk will occur.  Probability and impact matrix: A risk management tool that prioritizes risks by evaluating their likelihood alongside their potential consequences.  Process improvement: The practice of identifying, analyzing, and improving existing processes to enhance performance, meet best practices, or optimize consumer experiences.  Procurement: Sourcing and acquiring the external services, materials, and supplies needed to complete a project.  Product Backlog: The prioritized list of all features, technical tasks, and fixes that comprise the upcoming project scope.  Product Goal: The long-term target that defines the intended outcome and direction of a product.  Product increment: The usable, tested slice of a product delivered at the end of a sprint, satisfying the Definition of Done.  Product Owner: The Scrum role responsible for managing the Product Backlog and maximizing the value delivered by the team.  Product requirements document: A comprehensive document detailing project specifications and requirements, used primarily in Waterfall models.

 Product roadmap: A strategic visualization showing how a product's requirements, features, and milestones will evolve over time.  Product vision: A guiding summary that defines what a product is, who will use it, and how it aligns with business goals.  Productivity metrics: Metrics that track the effectiveness and efficiency of a project, including items like tasks, milestones, projections, and duration.  Productivity tools: Software applications—such as spreadsheets, docs, and presentation tools— used to manage and track work.  Program: A collection of projects.  Program manager: A professional who oversees and aligns multiple interrelated projects to meet high-level strategic goals.  Project: A temporary endeavor undertaken to create a unique product, service, or result.  Project buffer: Reserve time placed at the end of a project schedule to protect the completion date from delays.  Project charter: A formal document authorizing a project and outlining its core objectives, stakeholders, and boundaries.  Project closing: A process performed to formally complete a project, the current phase, and contractual obligations.  Project closeout report: A historical record and wrap-up document that describes what the team did, how they did it, and what they delivered; evaluates performance against budget and schedule for future reference.  Project goal: The defined outcome a project is initiated to achieve.  Project governance: The oversight framework that guides decision-making and accountability across a project's life cycle.  Project kick-off meeting: The initial gathering where teams and stakeholders align on project vision, goals, and responsibilities.  Project life cycle: The core four-phase progression of a project: Initiation, Planning, Executing, and Closing.  Project management: Applying skills, tools, and methodologies to project tasks to satisfy requirements.  Project management baseline (PMB): An approved, integrated plan for scope, cost, and schedule against which work execution is tracked.  Project management methodology: The collection of principles, processes, and tools used to guide a project through its life cycle.  Project management office (PMO): An organizational body that standardizes project management practices across an enterprise.  Project manager: The professional responsible for shepherding a project through its phases, managing communication, and guiding the team.  Project plan: The guiding document detailing project tasks, milestones, resource assignments, and schedules.  Project proposal: An initial document written to outline project viability and gain approval to proceed with formal initiation.  Project sponsor: An executive or business leader who champions the project, secures resources, and ensures delivery of strategic value.  Project status report: An update that gives an overview of all of a project’s common elements and summarizes them at a given point in time.  Project summary: A brief overview describing project goals, core components, and progress.

 Project task: A discrete work activity or assignment that must be finished within an agreed timeframe.  Project vision: A statement of purpose outlining the business need a project is designed to fulfill.  Projection: A prediction of a future outcome—such as future productivity trends, project durations, costs, performance, or quality—based on current information; also called a forecast.  Psychological safety: An individual’s perception of the consequences of taking an interpersonal risk. Q  Qualitative data: Information about subjective qualities that can’t be measured with numerical data.  Quality: When the outlined requirements for the deliverable are fulfilled and meet or exceed the needs and expectations of customers.  Quality assurance (QA): Process-driven reviews and audits designed to evaluate whether a project is moving toward delivering high-quality products or services.  Quality control (QC): Product-oriented techniques and technical inspections used to identify and fix defects in finished deliverables.  Quality management plan: A document establishing the quality processes, standards, and roles required across a project.  Quality metrics: Metrics that relate to achieving acceptable outcomes, such as number of changes, issues, and cost variance.  Quality planning: Determining which quality standards are relevant to a project and deciding how the team will meet them.  Quality standards: Requirements, specifications, or guidelines used to ensure deliverables and processes are fit for achieving the desired outcome.  Quantitative data: Statistical and numerical facts. R  RACI chart: A matrix detailing who is Responsible, Accountable, Consulted, and Informed for each activity or milestone.  RAG status report: A report that follows a traffic light pattern to indicate progress and status: “red” indicates critical issues that need resolution, “amber/yellow” means potential issues with schedule or budget, and “green” means the project is on track.  Reforecast: Updating future budget projections to reflect actual spending trends during project execution.  Relative estimation / Relative sizing: Estimating task difficulty, complexity, and duration by comparing it directly against other known tasks.  Releasable: Reaching a level of functional and technical completeness that meets requirements for customer delivery.  Release plans: Outlines mapping when specific features or milestones are planned for release to users.  Reporting chart: An organizational diagram showing internal reporting relationships and hierarchy.  Reputation: Refers to how others perceive a person overall.  Request for proposal (RFP): A document issued to prospective vendors inviting competitive bids for products or services.  Requirements: Specifications, conditions, and capabilities that must be delivered to achieve project success.  Reserve analysis: Reviewing remaining project contingency reserves to ensure they match lingering risks.

 Resource availability: The accessibility of personnel, budget, tools, and equipment needed to perform project tasks.  Resource cost rate: The unit cost (such as an hourly rate) associated with using a specific project resource.  Resources: People, equipment, software, funding, and workspace allocated to complete a project.  Retrospective: A meeting held at the end of an iteration or project to discuss successes, failures, and possible future improvements.  Retrospectives and continuous learning: An Agile principle focused on ongoing process reflection, experimentation, and refinement.  Return on investment (ROI): A financial metric comparing the net profit of a project against its implementation cost.  Risk: A potential, uncertain event or condition that could occur and impact project goals either positively or negatively.  Risk appetite: The level of risk exposure an organization is prepared to accept to pursue its strategic goals.  Risk assessment: The systematic process of estimating risk probability, severity, and potential impacts.  Risk exposure: A way to measure potential future loss resulting from a specific activity or event.  Risk management: The process of identifying, evaluating, and addressing potential risks to keep projects within acceptable thresholds.  Risk management plan: The formal strategy detailing how project risks will be tracked, assessed, and handled.  Risk register: A central table, chart, or log capturing identified risks, their severity, assignees, and mitigation plans.  Roadmap: A project-tracking visual that is useful for high-level tracking of large milestones.  ROAM technique: A strategy used to help manage actions after risks arise; stands for Resolved, Owned, Accepted, and Mitigated.  ROCCC: An acronym used in data ethics best practices to ensure that data is reliable, original, comprehensive, current, and cited.  Role: One’s position within an organization or team.  Root cause: The core underlying driver or flaw that gives rise to a risk, defect, or project issue. S  Sampling bias: A type of data bias in which the sample isn’t representative of the population as a whole.  Scaled Agile Framework (SAFe): An enterprise-level framework integrating Lean, Scrum, XP, and DevOps to coordinate large-scale agile delivery.  Scaled question: A survey question requiring respondents to choose a rating along a structured scale.  Schedule: The comprehensive project timetable covering start dates, activity durations, dependencies, and delivery milestones.  Schedule performance index (SPI): An EVM metric measuring schedule efficiency by calculating Earned Value divided by Planned Value.  Schedule variance (SV): The arithmetic difference between Earned Value and Planned Value ($SV = EV - PV$).  Scheduling and work management software: Digital platforms used to plan, track, and visualize tasks across project teams.

 Scope: The agreed-upon work boundaries defining what will—and will not—be delivered by a project.  Scope creep: When changes, growth, and other factors affect a project's boundaries without corresponding increases in time, budget, or resources.  Scope management: The processes used to define, control, and update the work included in a project.  Scope risk: The risk that final deliverables will fail to achieve the specifications or outcomes detailed in the project goals.  Scrum: An iterative Agile framework focused on delivering complex products in short, timeboxed sprints.  Scrum Master: The Scrum servant-leader responsible for guiding the team in Agile principles and removing operational blockers.  Scrum of Scrums: A coordination technique where delegates from multiple Scrum teams meet to manage cross-team dependencies.  Secondary stakeholders: Individuals or teams who are indirectly affected by a project's activities and outcomes.  Sequential tasks: Tasks that must be executed in a specific linear order due to dependencies.  Signal: An observable change.  Signpost: A way to clue the audience in to where a presentation is going and what to expect.  Silo: An isolated working environment where communication and project knowledge remain trapped with a single person or team.  Single point of failure: A critical component or task which, if disrupted, brings the wider project to a complete halt.  Six Sigma: A data-driven quality methodology focused on reducing defects and process variations.  Slack / Float: The time an activity can be delayed without pushing back subsequent tasks or the project schedule.  Slide-based presentation: A deck of digital slides used to summarize and present project proposals, updates, or closeout data.  Slides: A collaborative, cloud-based presentation tool.  SMART action item / SMART goals: Performance targets that are Specific, Measurable, Attainable, Relevant, and Time-bound.  Soft skills: Interpersonal abilities—such as active listening, empathy, and conflict resolution—that help individuals work well together.  Sole-supplier sourcing: Procuring goods or services from a single vendor without opening the contract to competitive bidding.  Solution Design Sprint: A dedicated sprint focused on architecting and testing system solutions before development begins.  Spotify model: An agile scaling approach using squads, tribes, chapters, and guilds to foster team autonomy.  Spreadsheet: A software application used to organize, calculate, analyze, and visualize data in rows and columns.  Sprint: A fixed, timeboxed iteration (usually 1 to 4 weeks) during which a team completes a set list of deliverables.  Sprint Backlog: The subset of Product Backlog items selected by the team to be completed during an upcoming Sprint.  Sprint Planning: The Scrum event where the team determines the Sprint Goal and plans out the work for the upcoming Sprint.

 Sprint Retrospective: An internal meeting held at the end of a Sprint where the Scrum team reviews their processes and identifies improvements.  Sprint Review: An event held at the end of a Sprint where the team demonstrates completed work to stakeholders and gathers feedback.  Stacked bar chart: A type of bar chart that can show part-to-whole variables simultaneously; useful when comparing numerical information; also called a marimekko chart.  Stacey Matrix: A planning tool used to classify projects based on requirements certainty and technical complexity.  Stakeholder: An individual, group, or organization with a vested interest in the execution or outcome of a project.  Stakeholder analysis: The process of identifying stakeholders and analyzing their influence, expectations, and interest in a project.  Stakeholder buy-in: Building support and agreement among stakeholders regarding project objectives and changes.  Stakeholder management: Developing and maintaining relationships with key stakeholders to align expectations and build consensus.  Stakes: The business value, resources, or organizational assets that may be jeopardized if a project falters.  Start-to-finish (SF): A dependency relationship where a successor task cannot finish until the predecessor task has started.  Start-to-start (SS): A dependency relationship where a successor task cannot start until the predecessor task has started.  Statement of work (SoW): A formal contract attachment detailing the specific deliverables, schedules, and terms a vendor must satisfy.  Steering committee / Steering committees: The senior governing body responsible for setting strategic direction, resolving escalations, and approving scope or budget changes.  Story points: A relative estimation unit used to score user story complexity, effort, and risk.  Storytelling: The process of turning facts into narrative to communicate data, impact, and results clearly to stakeholders.  Subject matter expert (SME): A specialist with deep expertise in a particular domain, tool, technology, or business process.  Subtasks: Granular work items that roll up into a larger summary task.  Success criteria: The measurable standards and performance indicators used to determine whether a project has landed successfully.  Summary sheet: A high-level, 1- to 2-page brief summarizing critical project data, timelines, and accomplishments.  Summary task: A parent task heading in a WBS or project schedule that groups related subtasks together.  Survey / Survey question: An assessment tool containing structured questions used to evaluate project quality, stakeholder satisfaction, or process outcomes.  Synthesizing: Combining data points and insights from multiple sources to draw actionable conclusions. T  Task buffer: Reserve time added to a specific, vulnerable task to prevent delays from impacting downstream activities.  Team: A group of people who plan work, solve problems, make decisions, and review progress in service of a specific project or objective.

 Team dynamics and culture: Fostering an inclusive, psychologically safe, and supportive team environment; the conscious and unconscious forces impacting team behavior.  Team members: The cross-functional contributors responsible for completing day-to-day project tasks.  Teamwork: An effective, collaborative way of working in which each person is committed to and heading towards a shared goal.  Test case: A sequence of steps and its expected results.  Three pillars of Scrum: The foundational principles of the Scrum framework: Transparency, Inspection, and Adaptation.  Three-point estimating: An estimation approach that calculates values using optimistic, most likely, and pessimistic projections.  Time and materials contract: A vendor agreement where compensation is based on actual hours worked plus reimbursed material costs.  Time estimation: Estimating the calendar duration or effort required to bring a task to completion.  Time risk: The risk that tasks or overall project delivery will take longer than scheduled.  Timebox / Timeboxing: Refers to setting a strict, non-negotiable maximum time limit allocated to finish an event, task, or deliverable.  Timeout: Refers to taking a moment away from the project to regroup and adjust the game plan.  Time-phase a budget: Scheduling financial expenditures across the project timeline to reflect when costs will actually occur.  Tools: Software applications, templates, and frameworks that assist project teams in planning and managing work.  Total cost of ownership (TCO): The total financial investment required for a project, including upfront execution and ongoing operational costs.  Total duration estimate: The full calendar duration of an activity, combining active effort estimates with external waiting and approval times.  Tracking: A method of following the progress of project activities.  Transferable skill: A general capability—such as communication or problem-solving—that applies across diverse roles and industries.  Transparency: Making processes, metrics, and obstacles visible across the team and leadership; one of the three pillars of Scrum.  Trench wars: Conflicts that occur when two peers or groups can’t come to an agreement and neither party is willing to give in.  Triangular distribution: A simple three-point estimation formula giving equal weight to all outcomes: $(O + M + P) / 3$.  Triple constraint: The fundamental, interrelated balance among scope, time, and cost that bounds every project.  T-shirt sizes: A relative sizing method (XS, S, M, L, XL, XXL) used to estimate task effort and complexity without assigning exact hours. U  Uncertainty: A state characterized by a lack of predictability or high potential for unexpected outcomes.  Urgency: Helping team members understand project priority and the immediate actions needed to maintain momentum.  User acceptance test (UAT): A trial that helps a business make sure a product or solution works for its users.

 User story: An informal, general explanation or concise feature requirement written from the perspective of an end user. V  Value delivery: Prioritizing and executing work to deliver usable value and feedback to stakeholders quickly.  Value roadmap: An Agile planning timeline mapping the anticipated delivery of value and features across future horizons.  Values: Guiding behavioral principles that define how employees and team members collaborate.  Velocity: An agile metric tracking the number of story points or backlog items completed by a team during an iteration.  Vendors: External commercial contractors or suppliers who provide necessary products or services to a project.  Volatility: The rate and unpredictability with which project variables, market dynamics, and operational conditions change.  VUCA: An acronym capturing the modern operational environment: Volatility, Uncertainty, Complexity, and Ambiguity. W  Waterfall / Waterfall project management: A sequential project methodology where phases progress linearly through initiation, design, development, and testing.  Work breakdown structure (WBS): A hierarchical breakdown that organizes a project's full scope into manageable milestones and subtasks.  Work groups: People in an organization who work toward a common goal; based on and assigned by organizational or managerial hierarchy.  Work-in-progress (WIP) limit: A rule in Kanban constraining the number of items allowed in an active workflow state at one time to prevent bottlenecks.