These are original SimCert study summaries, not reproduced definitions from the PMBOK® Guide or an official PMI glossary.
Governance
Initiating, integrating and closing the project: value creation, governance models, knowledge, quality assurance, change and overall performance control.
A formally chartered group responsible for reviewing and approving or rejecting changes.
A formal proposal to modify any document, deliverable, or baseline.
The process of processing, adjudicating, and communicating contract claims per contract terms.
A short, timeboxed agile ceremony where team members synchronize on progress and identify impediments.
Conditions not under the immediate control of the team that influence, constrain, or direct the project.
Factors outside the organization, such as regulations, that influence project execution.
A summary of project performance used to confirm project closure and formal acceptance.
A contract type that sets a total price for a defined scope of work, placing cost risk on the seller.
The framework of policies, procedures, and structures that guide and oversee project and organizational decision-making.
A formal checkpoint where project status and readiness are assessed against defined criteria.
A development approach combining predictive and adaptive elements to suit different project components.
A voluntary, widely accepted practice or specification within a given industry.
The process of reviewing, approving, and managing changes to deliverables, documents, and the project management plan.
A project document used to record knowledge gained for use in the current and future projects.
Adherence to internal rules and standards established by the organization.
A framework that integrates portfolios, programs, projects, and organizational enablers to achieve strategy.
An organizational structure that standardizes project-related governance and facilitates resource sharing.
A review point at the end of a project phase where a decision is made to continue, modify, or terminate the project.
The framework, functions, and processes that guide portfolio management activities to optimize value.
The rules and processes that ensure fair, transparent, and legal vendor selection.
The coordinated management of related projects and activities to achieve benefits not available from managing them individually.
Adherence to laws, regulations, and guidelines relevant to the project's industry or jurisdiction.
An agile ceremony held at the end of an iteration to reflect on process and identify improvements.
Criteria used to rate or score seller proposals, often including technical, cost, and management approach.
A fixed, short time period during which a team completes a set amount of work in agile delivery.
The deliberate adaptation of the project management approach, governance, and processes to fit the project context.
The approved version of scope, schedule or cost used as the comparison point for performance measurement.
Raising an issue or risk to a higher authority when it exceeds the project manager's threshold or mandate.
The structure of roles, decision rights and policies through which oversight and direction are exercised.
A record of current problems, their owners and resolution status, distinct from risks that have not yet occurred.
The plan for what to buy, from whom, under which contract type, and how the seller will be managed.
A structured technique for finding the underlying source of a problem rather than treating symptoms.
Considering environmental, social and economic impacts of project decisions across the deliverable's life.
Scope
Eliciting and analysing requirements, defining and structuring scope, then validating and controlling what the project delivers.
The ongoing process of reviewing and prioritizing backlog items to prepare them for future iterations.
A document describing how and when the benefits of a project will be delivered and measured.
The process of ensuring the intended value of a program or project is achieved and sustained.
A documented justification of the value and rationale for undertaking a project.
The net quantifiable and qualitative benefit derived from a business endeavor.
A financial technique comparing expected costs and benefits to assess project viability.
An intentional activity to modify a nonconforming product or product component.
An ordered list of everything known to be needed in the product, maintained by the product owner.
The process of monitoring and recording results of quality activities to assess performance and recommend changes.
A description of how individual requirements meet business needs for the project.
The process of drawing out requirements from stakeholders through various techniques.
Uncontrolled expansion of project scope without corresponding adjustments to time, cost, or resources.
Ensuring project objectives and outcomes support the organization's broader strategic goals.
A high-level document outlining an organization's long-term goals and the approach to achieve them.
The continuous process of delivering outcomes that provide value to stakeholders.
The collection of strategic business activities aimed at creating value for stakeholders.
The conditions a deliverable must meet before a customer or sponsor formally accepts it.
The team's shared checklist that an increment must satisfy before it counts as complete.
Agreed criteria that a backlog item must meet before a team pulls it into an iteration.
The smallest releasable increment that delivers value and generates validated learning.
Schedule
Planning schedule management, developing the schedule and keeping delivery timing under control as the work unfolds.
An approach that allows plans to evolve based on new information and changing conditions.
A technique that uses historical data from a similar activity or project to estimate duration or cost.
A schedule compression technique that adds resources to critical path activities for the least additional cost.
The sequence of activities that determines the shortest possible project duration.
Assessment of how a change or event affects project objectives, scope, schedule, and cost.
Techniques used to adjust resource utilization to meet project and organizational demands.
The approved version of the scope statement, WBS, and WBS dictionary, used as a basis for comparison.
A long-lived team of agile teams that plans, commits and delivers value together on a common cadence.
The regular rhythm of activities such as iterations, reviews or releases that gives a project predictable pace.
A chart showing work in each state over time, exposing bottlenecks and growing work in progress.
A logical, resource or external relationship that constrains the order in which work can be done.
A visual board of work states and limits that makes flow, bottlenecks and work in progress explicit.
Schedule adjustments that let a successor start earlier (lead) or force a wait (lag) relative to its predecessor.
Planning near-term work in detail and later work at a higher level, elaborating as information emerges.
The number of work items completed per unit of time, a core flow metric for adaptive teams.
The amount of work a team completes per iteration, used for forecasting rather than for judging people.
A cap on the number of items allowed in a workflow state, used to improve flow and reduce context switching.
Finance
Planning financial management, estimating costs, developing the budget and monitoring the money against delivered value.
A graphic display of process data over time, used to determine whether a process is stable or has predictable performance.
EV divided by AC; measures cost efficiency of work performed.
Outputs are tangible deliverables, while outcomes are the actual changes or benefits resulting from those deliverables.
EV divided by PV; measures schedule efficiency of work performed.
A document describing how and when the project's intended benefits will be delivered and measured.
The pace at which a project consumes its budget over a period, used to forecast funding needs.
Budget held back for unknown-unknown work, released only through management authorisation.
The total cost of conformance (prevention, appraisal) and non-conformance (rework, failure) across the product life cycle.
An integrated technique comparing planned value, earned value and actual cost to measure and forecast performance.
Analysing the flow of work from request to delivery to expose delays and non-value-adding steps.
Stakeholders
Identifying stakeholders, planning engagement and communications, then managing and monitoring both throughout the project.
A communication technique involving fully concentrating on and understanding a speaker's message before responding.
A component of the project management plan describing how project communications will be planned, structured, and monitored.
A situation where personal interests could improperly influence professional judgment or decisions.
A focused session that brings key stakeholders together to define product requirements.
A PMI Code of Ethics value requiring unbiased, objective decision-making free from favoritism.
One of the four PMI Code of Ethics values requiring truthful communication and conduct.
A structured approach to transitioning individuals, teams, and organizations to a desired future state.
A set of principles guiding responsibility, respect, fairness, and honesty for PMI members and credential holders.
A negotiation approach focusing on interests rather than positions to reach mutually beneficial agreements.
The role responsible for maximizing product value and prioritizing the product backlog.
The obligation to act with integrity, accountability, and adherence to ethical standards.
The person or group who provides resources and support for a project and is accountable for enabling success.
The process of developing approaches to involve stakeholders based on their needs, expectations, and influence.
The practice of openly sharing accurate information with relevant stakeholders.
A highly visible display of project progress and health that keeps the team and stakeholders informed without meetings.
The record of stakeholders with their interest, influence, expectations and engagement approach.
Resources
Planning, estimating and acquiring people and physical resources, leading the team and controlling resource performance.
A project manager competency involving identifying and addressing disagreements constructively to maintain team performance.
The ability to recognize and adapt to different cultural norms and communication styles within a diverse team.
The defined levels of empowerment given to individuals or roles to make specific project decisions without further approval.
The ability to identify and manage one's own emotions and those of others to guide behavior and interactions positively.
Frameworks (e.g., Herzberg, Maslow) explaining factors that drive individual performance and engagement, often applied by PMs to sustain team motivation.
A leadership style focused on prioritizing team members' needs and removing obstacles to help them succeed.
A principle emphasizing that teams should work at a pace they can maintain indefinitely without burnout.
A document that records team values, agreements, and operating guidelines to promote a shared understanding among team members.
A model describing stages of team development: forming, storming, norming, performing, and adjourning.
A group of people who work together and collaborate to achieve a common goal despite being in different physical locations.
Anything slowing or blocking the team that the project manager or servant leader is accountable for removing.
A team climate where members can raise problems, admit mistakes and dissent without fear of blame.
Risk
Planning risk management, identifying and analysing risks, planning and implementing responses and monitoring exposure.
A predefined action plan to be executed if a specific risk event occurs.
Budget or time set aside for identified risks that are accepted.
A quantitative risk analysis technique that models the combined effects of uncertainties to determine possible outcomes.
A risk response strategy where the team acknowledges the risk without taking proactive action unless it occurs.
A living record of assumptions and constraints, reviewed regularly because unexamined assumptions become risks.
Prioritising risks by assessing probability and impact so attention goes to the ones that matter.
Numerically modelling the combined effect of risks on objectives, often through simulation.
The degree of uncertainty an organization is willing to accept in pursuit of its objectives.
The measurable level of exposure above which a risk requires a response or escalation.