The PMBOK® Guide's 7th Edition is A Guide to the Project Management Body of Knowledge. ezRACI helps aspiring PMPs get ready and also offers a free subscription to students.
Aligned to PMP Domains & PMBOK 7th Edition
A1. A project is a temporary endeavor undertaken to create a unique product, service, or result. It has a defined beginning and end and differs from ongoing operations. PMP candidates should know this definition cold—it's foundational to the exam.
A2. Projects are temporary and unique, while operations are ongoing and repetitive. Operations sustain the business, but projects create change. For example, implementing a new EHR system is a project; managing patient admissions is operational.
A3. The five process groups are:
Initiating
Planning
Executing
Monitoring and Controlling
Closing
These are not the same as phases—process groups are cyclical and applied as needed throughout the project lifecycle.
A4. The PMBOK defines 10 knowledge areas:
Integration
Scope
Schedule
Cost
Quality
Resource
Communications
Risk
Procurement
Stakeholder
These help structure processes and tools used throughout the project.
A5. A project charter is a formal document that authorizes the project and gives the project manager authority to apply resources. It includes objectives, high-level scope, stakeholders, and key constraints. It’s created during the Initiating phase.
A6. Typically, the project sponsor creates and signs the charter. The project manager may help draft it, but it’s the sponsor who gives formal authorization.
A7. A stakeholder is anyone who is impacted by or can impact the project—including customers, team members, sponsors, suppliers, and regulators. Stakeholder management is a core PMP topic.
A8. The project manager is responsible for meeting project objectives by leading the team, managing constraints (scope, time, cost), and communicating with stakeholders. They’re the glue between strategy and execution.
A9. The triple constraint refers to scope, time, and cost. A change to one affects the others. Sometimes, quality is added as the fourth constraint.
A10. A deliverable is a measurable product or result (e.g., software module), while a milestone marks a point in time (e.g., "Design Complete"). Milestones track progress; deliverables track outputs.
A11. Progressive elaboration means the project is developed in steps, with increasing detail as more is learned. It allows flexibility in early planning and refinement as scope clarifies.
A12. The project lifecycle describes the phases a project goes through—typically: Concept → Planning → Execution → Closure. It's tailored by organization or industry.
A13. OPAs are internal assets like templates, policies, lessons learned, or historical data that can guide project planning and execution. Tools like ezRACI help manage and apply OPAs consistently.
A14. EEFs are external or internal conditions that affect the project—like laws, culture, tech infrastructure, or market conditions. They influence planning but are outside your control.
A15.
Functional: Projects are siloed by department.
Matrix: Shared resources; project managers and functional managers coexist.
Projectized: PM has full authority; teams are built around projects.
A16. A RACI matrix defines who is Responsible, Accountable, Consulted, and Informed for each task or deliverable. It ensures role clarity and reduces confusion. Tools like ezRACI let you create dynamic, shareable RACI matrices aligned to PMBOK principles.
A17. It’s the central document that integrates all subsidiary plans (scope, schedule, cost, etc.). It’s not a single plan, but a collection of documents guiding execution and control.
A18. Monitoring is observing progress; controlling is taking corrective actions when things go off track. They’re linked but distinct.
A19. A baseline is the approved version of scope, schedule, or cost that is used for performance comparison. For example, if your cost baseline is $100k, you compare actuals to that to track variance.
A20. Lessons learned are insights captured after a phase or project to improve future efforts. It’s formally documented during Closing, but smart teams like those using ezRACI gather them continuously and assign action owners in real time.
PMBOK Knowledge Area: Integration Management
A21. It’s the coordination of all project elements into a unified whole. Integration ensures that planning, execution, and changes are aligned to meet project objectives.
A22.
Develop Project Charter
Develop Project Management Plan
Direct and Manage Project Work
Manage Project Knowledge
Monitor and Control Project Work
Perform Integrated Change Control
Close Project or Phase
A23. It’s the process of formally authorizing the project. It identifies the PM, outlines the high-level scope, and gives the PM authority to begin project work.
A24. The project sponsor typically signs it, signaling official project kickoff and buy-in from leadership.
A25. It’s the master document integrating all subsidiary plans (scope, schedule, cost, quality, etc.) and guides project execution and control.
A26. It’s the execution of the tasks defined in the PM plan to achieve project goals. It involves coordinating people, processes, and resources.
A27. This involves capturing and using both explicit knowledge (documents, databases) and tacit knowledge (experience, insights) to benefit the current and future projects.
A28. By tracking, reviewing, and reporting project progress to meet performance objectives. This includes variance analysis, forecasts, and trend reviews.
A29. It’s the process of reviewing, approving, and managing changes to project scope, cost, and schedule. All change requests must be evaluated before implementation.
A30. The Change Control Board (CCB) or project sponsor typically decides, but the PM facilitates the process and ensures documentation and communication.
A31. Tools include change request forms, impact assessments, tracking logs, and change control systems—like those integrated with ezRACI, which can assign change roles using RACI matrices.
A32. Final deliverables are verified, contracts closed, lessons learned documented, and team members released. It ensures formal closure and knowledge transfer.
A33. Configuration management ensures that product specifications and deliverables remain consistent and are properly documented and controlled throughout the project lifecycle.
A34.
Corrective: Align performance with plan
Preventive: Avoid future deviations
Defect Repair: Fix existing product issues
A35. A group of stakeholders who review and approve or reject change requests. Members may include the sponsor, PM, key customers, and SMEs.
A36. A centralized database of past project lessons, documentation, risks, and outcomes. Tools like ezRACI can link tasks to knowledge entries for context-rich decision-making.
A37.
Explicit: Process docs, reports, charts
Tacit: Know-how, instincts, interpersonal insights
A38. Because it involves bringing everything together—schedules, budgets, quality, risks—and ensuring alignment across all areas of the project.
A39. Description of the change, requestor, date, impact, decision, and implementation status. It’s a living document and part of the PM Plan.
A40. ezRACI helps define and track role accountability for integrated actions (like change approvals, issue response, phase closure) through RACI matrices and Gantt timelines—ensuring alignment across stakeholders.
PMBOK Knowledge Area: Scope Management
A41. Project scope refers to the work required to deliver a product, service, or result with the specified features and functions. It defines what is included—and what is not.
A42.
Product Scope: The features and functions of the product/service/result
Project Scope: The work required to deliver the product
Product scope is the “what,” project scope is the “how.”
A43.
Plan Scope Management
Collect Requirements
Define Scope
Create WBS
Validate Scope
Control Scope
A44. It defines how the project team will plan, execute, validate, and control the project scope. It’s a subsidiary plan within the overall PM Plan.
A45. Interviews, focus groups, surveys, brainstorming, observation, document analysis, and prototypes. Requirements gathering is critical for stakeholder satisfaction.
A46. The RTM links requirements to deliverables, tests, and objectives, ensuring nothing is missed. It supports scope validation and control.
A47. A detailed narrative that includes project scope, product scope, deliverables, exclusions, constraints, and assumptions. It becomes the reference for validating and controlling scope.
A48. A hierarchical decomposition of the total project scope into manageable deliverables (work packages). It enables better planning, estimating, and tracking.
A49. The lowest-level deliverables in the WBS, where cost and duration can be estimated and responsibility can be assigned. Think: “doable chunks.”
A50. It provides detailed descriptions of each work package in the WBS, including deliverables, milestones, risks, and resources required.
A51. It’s the process of formally accepting completed deliverables. Usually involves the customer or sponsor reviewing and approving outcomes.
A52. Usually, the customer, sponsor, or key stakeholder signs off on deliverables to confirm they meet agreed-upon requirements.
A53. The uncontrolled expansion of project scope without changes to time, cost, or resources. It usually occurs when changes are made without formal approval.
A54. Use a formal change control process, clear documentation, stakeholder alignment, and tools like ezRACI to assign who can approve or reject scope changes.
A55.
Scope Creep: Unauthorized scope additions from stakeholders
Gold Plating: The team adds extras that weren’t requested—usually to impress, but it adds risk
A56. Monitoring project scope and managing changes to it. It ensures that all requested changes are evaluated and only approved ones are implemented.
A57. It breaks work into components that can be estimated and scheduled. Work packages lead to activities (for scheduling) and cost estimates (for budgeting).
A58. It’s the foundation for project planning. It ensures nothing is forgotten, enables RACI assignment, and feeds schedule and budget planning. Tools like ezRACI support WBS-to-RACI alignment.
A59. Stakeholders help define, clarify, and validate requirements. Their early and continuous engagement prevents rework and improves satisfaction.
A60. ezRACI lets you assign RACI roles to each WBS work package and requirement. This helps clarify who owns what, reduces rework, and ensures stakeholder alignment—key to successful scope delivery.
PMBOK Knowledge Area: Schedule Management
A61. It involves the processes required to manage timely completion of the project. This includes planning, developing, and controlling the schedule.
A62.
Plan Schedule Management
Define Activities
Sequence Activities
Estimate Activity Durations
Develop Schedule
Control Schedule
A63. It defines how the schedule will be developed, managed, executed, and controlled—including formats, thresholds, and reporting frequency.
A64. An activity is a distinct task that must be performed to produce a project deliverable. It is derived from work packages in the WBS.
A65. Determining the logical order of activities, identifying dependencies using tools like network diagrams or dependency lists.
A66.
Finish-to-Start (FS) – Most common
Start-to-Start (SS)
Finish-to-Finish (FF)
Start-to-Finish (SF) – Rare
A67.
Lead: Allows an activity to start before the previous one finishes
Lag: Adds delay between two activities
A68. The longest path through the project, determining the shortest time to completion. If any activity on the critical path is delayed, the entire project is delayed.
A69. Float = Latest Start (LS) – Earliest Start (ES)
Or
Float = Latest Finish (LF) – Earliest Finish (EF)
It tells you how much time an activity can be delayed without delaying the project.
A70.
Total Float: Time an activity can slip without delaying project
Free Float: Time it can slip without delaying the next activity
A71. Critical Path Method (CPM), Program Evaluation Review Technique (PERT), Monte Carlo simulations, and resource optimization (leveling/smoothing).
A72. Performing tasks in parallel that were planned in sequence to save time. It increases risk of rework.
A73. Adding more resources to shorten the schedule without changing scope—often increases cost and may impact quality.
A74. The approved version of the schedule, against which progress is measured. It’s locked down after initial planning.
A75. Adjusting the project schedule to resolve resource conflicts. It may extend the schedule to avoid overloading resources.
A76. SV = Earned Value (EV) – Planned Value (PV)
It indicates if the project is ahead or behind schedule.
A77. SPI = EV / PV
1 = ahead of schedule,
<1 = behind schedule
=1 = on schedule
A78. A visual summary of major events or deliverables in the project. It’s used to report progress to senior stakeholders.
A79. Gantt charts visualize activities over time, show task dependencies, and make it easy to track schedule status. ezRACI includes built-in Gantt views with RACI overlays for better collaboration.
A80. ezRACI allows PMs to assign deadlines and RACI roles to each task on a Gantt timeline—so teams know who owns what, by when, across cross-functional initiatives. This keeps schedules visible and on track.
PMBOK Knowledge Area: Cost Management
A81. It involves planning, estimating, budgeting, financing, funding, and controlling costs so that the project is completed within the approved budget.
A82.
Plan Cost Management
Estimate Costs
Determine Budget
Control Costs
A83. A document that outlines how costs will be estimated, tracked, reported, and controlled. It includes units of measure, thresholds, and rules of performance measurement.
A84. Forecasting the monetary resources needed to complete project work. It includes labor, materials, equipment, and contingency.
A85.
Analogous Estimating
Parametric Estimating
Bottom-Up Estimating
Three-Point Estimating
Expert Judgment
A86.
Direct Costs: Tied directly to project work (e.g., team salaries, software tools)
Indirect Costs: Shared costs like admin or overhead (e.g., electricity, HR staff)
A87.
CAPEX (Capital Expenditures): Long-term assets (e.g., equipment, buildings)
OPEX (Operational Expenditures): Day-to-day operations (e.g., salaries, utilities)
A88. The approved, time-phased budget for the project. It includes all authorized costs and is used for comparison during performance tracking.
A89. Funding requirements describe when and how much money will be needed. This includes reserves and contingency funding.
A90. A technique that combines scope, schedule, and cost performance to assess project health. It uses metrics like EV, PV, AC, SV, and CPI.
A91. The authorized budget for the work scheduled to be done at a specific point in time. Also called Budgeted Cost of Work Scheduled (BCWS).
A92. The value of work actually completed at a specific point in time. Also called Budgeted Cost of Work Performed (BCWP).
A93. The total cost incurred for work completed. Also known as Actual Cost of Work Performed (ACWP).
A94. CV = EV – AC
It shows whether you're under or over budget.
0 = under budget
<0 = over budget
A95. CPI = EV / AC
CPI > 1 = cost-efficient
CPI < 1 = over budget
CPI = 1 = on budget
A96. A forecast of the total project cost at completion. Common formulas:
EAC = BAC / CPI (if current trend continues)
EAC = AC + Bottom-up Estimate to Complete (new estimate)
A97. VAC = BAC – EAC
If positive, you're projected to finish under budget. If negative, over budget.
A98. TCPI = (BAC – EV) / (BAC – AC)
It shows the cost performance required to finish on budget.
A99. A technique to identify and manage contingency and management reserves for unexpected risks and cost overruns.
A100. ezRACI allows you to assign RACI roles to cost planning, approvals, and variance tracking tasks—ensuring that finance, PMs, and stakeholders stay aligned on who owns what budget-wise. Gantt views and audit logs also improve traceability for financial compliance.
PMBOK Knowledge Area: Quality Management
A101. It ensures that the project and its deliverables meet stakeholder expectations and quality standards. It focuses on process effectiveness and product fitness.
A102.
Plan Quality Management
Manage Quality
Control Quality
A103.
Manage Quality: Ensures that processes are being followed (process-oriented)
Control Quality: Focuses on deliverables meeting specs (product-oriented)
A104. CoQ includes:
Prevention Costs (training, process improvement)
Appraisal Costs (inspection, testing)
Failure Costs (rework, defects)
A105.
Prevention: Keep errors from occurring
Inspection: Identify errors after they’ve occurred
A106.
Internal Failure: Defects found before delivery (e.g., rework)
External Failure: Found after release (e.g., recalls, lawsuits)
A107.
Cost-benefit analysis
Benchmarking
Design of experiments
Cost of quality
Logical models
A108.
Process analysis
Root cause analysis
Quality audits
Design for X (DfX)
Problem-solving techniques
A109.
Inspections
Statistical sampling
Control charts
Checklists
Defect analysis
A110. A structured, independent review to determine whether project activities comply with organizational policies, processes, and procedures.
A111. A methodology aimed at reducing defects and variability using statistical techniques. It’s often used in quality-focused industries like healthcare and manufacturing.
A112. A graphical display showing process stability over time, with upper and lower control limits. Useful for identifying trends or out-of-control conditions.
A113. A bar graph that shows which causes contribute most to a problem (80/20 rule). Helps prioritize quality issues.
A114.
Assurance: Proactive process improvement (Manage Quality)
Control: Reactive product evaluation (Control Quality)
A115. Specific measures used to assess quality (e.g., defect density, uptime, rework percentage). They are defined in the quality management plan.
A116. A statistical technique used to identify which variables influence outcomes. Often used in manufacturing and product development.
A117. Selecting a random subset of outputs for inspection to reduce costs. Often used in Control Quality processes.
A118. If seven consecutive data points fall on one side of the mean in a control chart, it signals a non-random issue—even if within control limits.
A119. Because perceived quality can influence project acceptance more than technical quality. A deliverable must meet both technical and customer expectations.
A120. ezRACI enables you to assign ownership to quality planning, reviews, audits, and approvals using RACI matrices. It ensures that QA and QC roles are clearly defined and traceable—supporting compliance-heavy industries like healthcare and finance.
PMBOK Knowledge Area: Resource Management
A121. It involves planning, acquiring, managing, and leading the project team and physical resources. It ensures the right people and materials are in place at the right time.
A122.
Plan Resource Management
Estimate Activity Resources
Acquire Resources
Develop Team
Manage Team
Control Resources
A123. A RAM shows how project activities are assigned to roles or people. A RACI matrix is a type of RAM. ezRACI automates this process to clarify ownership and reduce miscommunication.
A124. It clarifies who is:
Responsible for doing the work
Accountable for final decisions
Consulted for input
Informed about progress
This improves team coordination.
A125.
Org Charts show hierarchy
RACI maps roles to specific tasks or deliverables
Together, they provide clarity across teams.
A126. A hierarchical representation of resources by category and type (e.g., labor, materials, equipment). It’s similar to a WBS but for resources.
A127.
Human Resources: Team members, SMEs, PMs
Physical Resources: Equipment, tools, supplies, space
A128. The process of securing the necessary team members, either from within the organization or externally (contractors, vendors).
A129. Adjusting the schedule to address resource conflicts or overallocations. It may extend project duration but prevents burnout and bottlenecks.
A130. Adjusting activities so that resources are used evenly, without extending the project timeline. Often less disruptive than leveling.
A131.
Training
Team-building exercises
Recognition and rewards
Clear communication of goals and roles
A132.
Forming – Team meets
Storming – Conflict and competition
Norming – Collaboration grows
Performing – Productive, self-directed
Adjourning – Project ends, team disbands
A133.
Leadership: Motivating, inspiring, guiding vision
Management: Planning, organizing, controlling day-to-day execution
A134. Use conflict resolution techniques:
Collaborating
Compromising
Accommodating
Forcing (if urgent)
Avoiding (if necessary short-term)
A135.
Recognition programs
Goal alignment
Skill development opportunities
Regular feedback
Empowerment and autonomy
A136.
Responsibility: Doing the task
Accountability: Owning the outcome
In RACI, there can be multiple Responsible, but only one Accountable.
A137. It shows availability of people and equipment—including holidays, planned absences, or maintenance downtime.
A138. A formal or informal review of a team member’s performance. Helps identify growth areas, training needs, or recognize top contributors.
A139. High-influence stakeholders (like sponsors or functional managers) can affect resource availability, priorities, or team structure. Their support is critical.
A140. ezRACI allows you to visually assign and track resource responsibilities across workstreams using RACI matrices and integrated timelines. It prevents duplication, clarifies ownership, and improves handoffs—especially across cross-functional teams.
PMBOK Knowledge Area: Communications Management
A141. It involves planning, managing, and monitoring communications so stakeholders receive the right information at the right time, in the right format.
A142.
Plan Communications Management
Manage Communications
Monitor Communications
A143. Because poor communication is the leading cause of project failure. Clear, timely, and targeted communication ensures alignment and minimizes confusion.
A144.
Stakeholder communication requirements
Communication methods (email, meetings, dashboards)
Frequency and format
Responsible senders/receivers
Escalation procedures
A145.
Push: Email, newsletters
Pull: Intranet, shared folders
Interactive: Meetings, calls, chats
A146.
Correct
Concise
Clear
Coherent
Controlling (the flow of information)
A147. A process to identify who needs what information, when, and how, based on their role, influence, and interest in the project.
A148. By using a stakeholder engagement matrix and adjusting for:
Power/influence
Location/time zone
Level of interest
Technical vs. executive roles
A149.
Formal: Reports, presentations, status meetings
Informal: Hallway chats, ad-hoc calls, Slack messages
Both are valuable—informal often reveals emerging issues faster.
A150. A model showing how messages are encoded, transmitted, received, and decoded—emphasizing feedback loops and noise barriers.
A151.
Method: Interactive, push, or pull
Technology: Email, MS Teams, Zoom, dashboards
Choose the right method and tech for the stakeholder and message type.
A152.
Communications: The actual exchange of information
Communications Management: The structured planning and control of those communications
A153.
Language or cultural differences
Technical jargon
Time zone or location issues
Emotional noise (stress, burnout)
A154. Use scheduled standups, shared workspaces (like ezRACI), and real-time collaboration tools. Set communication expectations and norms early.
A155. Use open dashboards, frequent status updates, and shared visibility into progress. Assigning RACI roles in ezRACI helps ensure communication flows clearly by role.
A156. Consolidating data into project reports, dashboards, and presentations to communicate progress, risks, and results to stakeholders.
A157. Effective communication drives engagement by keeping stakeholders informed, involved, and satisfied. It reduces resistance and increases buy-in.
A158.
Feedback from stakeholders
Survey results
Meeting attendance and participation
Missed deliverables due to miscommunication
A159. ezRACI assigns RACI roles, timelines, and status updates—so everyone knows who is responsible, what’s due, and when to follow up. It reduces noise and keeps communication role-aligned.
A160. It clarifies communication paths—who to consult, who to update, and who must take action—so you're not emailing 15 people hoping someone replies.
PMBOK Knowledge Area: Risk Management
A161. A risk is an uncertain event or condition that, if it occurs, could have a positive or negative effect on one or more project objectives such as scope, time, cost, or quality.
A162. The process of identifying, analyzing, responding to, and monitoring risks throughout the project lifecycle. It includes both threats and opportunities.
A163.
Plan Risk Management
Identify Risks
Perform Qualitative Risk Analysis
Perform Quantitative Risk Analysis
Plan Risk Responses
Implement Risk Responses
Monitor Risks
A164.
Qualitative: Prioritizes risks based on probability and impact
Quantitative: Assigns numerical values to estimate risk exposure or potential cost/time impact
A165. A document that lists identified risks, along with details such as probability, impact, owner, responses, and status.
A166. A hierarchical decomposition of risk sources (e.g., technical, external, organizational) that helps categorize and track risks.
A167.
Risk Appetite: The degree of uncertainty an organization is willing to accept
Risk Tolerance: The specific range of variation acceptable before action is triggered
A168. The person responsible for monitoring the risk and executing the risk response strategy. Assigned during the planning stage—easily tracked using ezRACI roles.
A169.
Avoid
Mitigate
Transfer
Accept
A170.
Exploit
Enhance
Share
Accept
A171. A buffer added to the schedule or budget to address identified risks. It’s managed by the project team and is separate from the management reserve.
A172. The remaining risk after a response strategy has been implemented.
A173. A new risk that arises as a result of implementing a risk response.
A174. A matrix that plots risks based on likelihood and consequence, used in qualitative risk analysis to prioritize risk response planning.
A175. A quantitative risk analysis technique using random sampling and probability distributions to model the impact of risks on project outcomes.
A176. A method to determine which risks have the greatest impact on project outcomes—often visualized with a tornado diagram.
A177. Continuously. Risks evolve throughout the project, so the register should be updated at every planning cycle or major change.
A178. Through risk audits, status meetings, performance indicators, and reviewing triggers for identified risks.
A179. It clarifies who is Responsible for monitoring and responding to each risk, who is Accountable for escalation, and who should be Informed or Consulted—this is where ezRACI shines.
A180. ezRACI allows PMs to assign RACI roles to each risk entry, define escalation paths, and integrate deadlines—making risk ownership and mitigation fully transparent.
PMBOK Knowledge Area: Procurement Management
A181. It involves the processes required to acquire products, services, or results from outside the project team, including contract management and purchasing.
A182.
Plan Procurement Management
Conduct Procurements
Control Procurements
A183. A decision process used to determine whether project work should be done in-house or outsourced, based on cost, expertise, timeline, and capacity.
A184. A document that outlines how procurement will be handled—including contract types, vendor selection criteria, documentation, and contract management approach.
A185.
Fixed Price (FP) – Firm cost
Cost-Reimbursable (CR) – Seller reimbursed for costs + fee
Time & Materials (T&M) – Hourly/daily rate + expenses
A186. The seller agrees to a set price, regardless of cost changes. This puts more risk on the seller.
A187. The buyer pays the actual costs plus a fixed fee. This is often used when scope is not fully defined.
A188. A hybrid model where the buyer pays for actual hours worked and materials used—often used for consultants or short-term services.
A189. A detailed description of the work to be performed by the vendor. It must be clear and complete to avoid disputes.
A190. A meeting with potential vendors to clarify project requirements and allow equal understanding before submitting bids.
A191.
Weighting systems
Screening systems
Independent estimates
Expert judgment
Negotiation
A192. A formal system used to manage changes to contracts, ensuring proper documentation, review, and approval.
A193. A structured review of the procurement process to identify lessons learned, best practices, and contract performance issues.
A194. A procurement is considered closed when all contract terms have been fulfilled, deliverables accepted, and documentation finalized.
A195.
Delivery delays
Scope misalignment
Legal disputes
Cost overruns
Vendor bankruptcy
Risk responses should be included in both the contract and project risk plan.
A196. The process of overseeing external suppliers, including relationship building, performance evaluation, compliance tracking, and issue resolution.
A197.
Procurement: Purchasing goods/services
Outsourcing: Transferring internal functions to an external provider
A198. Procurement decisions directly affect budget, timeline, and risk exposure. Delays or overruns from vendors can derail project performance.
A199. By clearly identifying who is Responsible for vendor engagement, who is Accountable for final approvals, and who must be Consulted or Informed at each step—this is easy to do in ezRACI.
A200. ezRACI allows PMs to assign roles to contract drafting, approvals, invoice tracking, and vendor reviews, creating a collaborative procurement workflow that ensures alignment and avoids bottlenecks.
PMBOK Knowledge Area: Stakeholder Management
A201. It involves identifying all stakeholders, analyzing their needs and expectations, and developing strategies to engage and influence them throughout the project lifecycle.
A202.
Identify Stakeholders
Plan Stakeholder Engagement
Manage Stakeholder Engagement
Monitor Stakeholder Engagement
A203. Any person or organization that can affect or be affected by the project, including team members, customers, sponsors, vendors, and even the public.
A204. A document that contains information about identified stakeholders, including contact details, roles, influence, interest level, and engagement strategies.
A205. The process of categorizing and assessing stakeholders based on their level of interest, power, influence, and impact on the project.
A206. A visual tool used to categorize stakeholders based on:
High Power / High Interest: Manage closely
High Power / Low Interest: Keep satisfied
Low Power / High Interest: Keep informed
Low Power / Low Interest: Monitor only
A207. A stakeholder classification method based on:
Power
Legitimacy
Urgency
It helps identify which stakeholders should receive the most attention.
A208.
Engagement involves fostering participation and buy-in
Communication is about information exchange
Engagement is more strategic and relationship-focused.
A209. A plan that outlines how to involve stakeholders effectively, including goals, channels, timing, messaging, and role assignments.
A210. Early involvement, tailored communication, transparency, and regular feedback. Use of RACI matrices helps stakeholders understand their role and accountability.
A211.
Unaware
Resistant
Neutral
Supportive
Leading
The goal is to move stakeholders toward “Supportive” or “Leading.”
A212.
Fear of change
Lack of communication
Misalignment of expectations
Competing priorities
Address these through proactive engagement.
A213. Continuously—especially during phase transitions, major deliverables, or change events. Use your RACI and ezRACI dashboards to update accountability as needed.
A214. A visual technique to categorize stakeholders and tailor your engagement strategy. This often includes power-interest or influence-impact grids.
A215. Prioritize based on project objectives, influence levels, and organizational alignment. Use RACI matrices to clarify who has authority and who is a consultative voice.
A216. Trust builds openness and reduces resistance. It enhances collaboration and increases the likelihood of support during tough project phases.
A217. Buy-in means stakeholders support and believe in the project goals and outcomes. Without it, even a well-executed project may fail to be adopted or sustained.
A218.
Surveys
One-on-one interviews
Feedback forms
Stakeholder sentiment analysis (qualitative)
Adoption/usage metrics for project outcomes
A219. ezRACI lets you assign stakeholders to RACI roles per task or milestone, making engagement transparent and structured. It also tracks timelines and communication status so nothing falls through the cracks.
A220. By showing each stakeholder their expected involvement, RACI matrices reduce confusion, avoid duplication of effort, and help manage expectations from day one.
Aligned to PMBOK 7th Edition and PMP Agile Content
A221. Agile is a value-driven, iterative approach to managing work, where teams deliver working solutions in small increments, respond to change quickly, and emphasize collaboration over rigid plans.
A222.
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
A223. Key principles include:
Early and continuous delivery
Welcome changing requirements
Frequent delivery of working solutions
Close collaboration
Empowered individuals
Face-to-face communication
Sustainable pace
Technical excellence
Simplicity
Self-organizing teams
Regular reflection and adaptation
A224. Scrum is a lightweight Agile framework based on sprints, with defined roles (Scrum Master, Product Owner, Team), artifacts (backlog, increments), and ceremonies (daily standups, retrospectives, etc.).
A225. Kanban is a visual workflow management method that focuses on limiting work in progress (WIP), continuous delivery, and improving flow efficiency.
A226. Lean focuses on eliminating waste, optimizing processes, and maximizing value. Lean principles influence Agile by emphasizing efficiency and flow.
A227. A sprint is a time-boxed iteration (typically 1–4 weeks) where a team delivers a usable, potentially releasable product increment.
A228.
Product Backlog: Ordered list of all desired features
Sprint Backlog: Subset of backlog items selected for the current sprint
A229. A servant leader who removes impediments, facilitates meetings, and protects the team from distractions—ensuring Scrum values are upheld.
A230. The person responsible for maximizing the value of the product, managing the product backlog, and ensuring the team builds the right thing.
A231. Velocity is the amount of work a team completes in a sprint—measured in story points, hours, or number of items. It's used to forecast future capacity.
A232. A visual representation showing work remaining over time during a sprint. It helps track progress and identify scope creep.
A233. Short descriptions of a feature from an end-user perspective, usually formatted as:
“As a [user], I want [feature] so that [benefit].”
A234.
Independent
Negotiable
Valuable
Estimable
Small
Testable
A235. A shared understanding of what it means for work to be complete—including coding, testing, documentation, and acceptance criteria.
A236. Combining predictive (waterfall) and adaptive (Agile) approaches. For example, planning is done upfront, while execution uses Agile sprints.
A237. When a project has both known and unknown elements—such as compliance needs (predictive) alongside evolving requirements (Agile).
A238.
Agile: Continuous engagement
Predictive: Formal checkpoints
Agile promotes faster feedback and adaptability.
A239. Risks are addressed continuously via:
Short feedback loops
Backlog refinement
Frequent testing
Early delivery
Regular retrospectives
A240. ezRACI lets Scrum and Agile teams define roles for Epics, Features, Stories, and Tasks using RACI matrices—even across departments or vendors. It complements tools like JIRA or Azure DevOps with visible responsibility, improving collaboration across the sprint lifecycle.
Aligned with PMBOK 7 Performance Domains + Organizational Systems
A241. The project environment includes internal and external factors that influence project success—such as organizational structure, company culture, and regulatory constraints.
A242. EEFs are conditions outside the PM's control that influence the project, like:
Market conditions
Legal regulations
Infrastructure
Organizational culture
A243. Internal tools, templates, historical data, policies, and procedures that can be leveraged on current projects. Tools like ezRACI help organize and reuse OPAs efficiently.
A244. A framework of rules, policies, and decision-making hierarchies that guide how projects are initiated, executed, and controlled.
A245. A structure that defines who makes what decisions, approval thresholds, and how oversight is maintained—especially important in regulated or high-risk projects.
A246.
Project charters
Stage gate review templates
Decision authority matrices (often paired with RACI)
Audit trail logs
Escalation plans
A247.
Governance: Defines structure, direction, and policies
Management: Executes plans, manages teams, delivers outcomes
Both must align for project success.
A248. PMs must tailor methods and artifacts based on project size, complexity, culture, delivery approach (Agile vs Predictive), and industry needs.
A249. A collection of interrelated elements working together to achieve a goal. Projects are systems that interact with other systems in the organization.
A250. It means looking at the project as part of a bigger picture, considering dependencies, feedback loops, and unintended consequences.
A251. It helps PMs anticipate ripple effects, manage complexity, and engage stakeholders holistically—especially in change-heavy or matrixed environments.
A252. A collection of portfolios, programs, projects, and operations that work together to deliver value to stakeholders. This is a major theme in PMBOK 7.
A253.
Project success: Met objectives (on time, budget, scope)
Product success: Solved the right problem or met user needs
A project can be on time but still fail if the product doesn't provide value.
A254.
Stakeholders
Team
Development Approach and Lifecycle
Planning
Project Work
Delivery
Measurement
Uncertainty
A255. It focuses on engaging stakeholders effectively, ensuring alignment with project goals and timely feedback.
A256. Ensures that intended outcomes are met and value is delivered consistently through output, capability, or benefit.
A257. By creating transparency, defining accountability, and offering structured decision-making—tools like ezRACI reinforce this by showing who owns what.
A258. A centralized body that standardizes project practices, supports governance, manages portfolios, and provides guidance and tools for PMs.
A259.
Supportive: Provides templates and training
Controlling: Enforces compliance
Directive: Directly manages projects
Tailor the model based on maturity and scale.
A260. ezRACI provides visual governance frameworks through dynamic RACI matrices and timeline-based accountability. It enables project audits, approvals, stakeholder visibility, and role-based control—all core to effective governance.
Based on PMI's PMP Exam Content Outline & Application Process
A261. The Project Management Institute (PMI), a global nonprofit professional organization based in the U.S., offers and administers the PMP certification.
A262. You need:
A 4-year degree, 36 months leading projects, and 35 hours of project management education
OR
A high school diploma or associate’s degree, 60 months leading projects, and 35 hours of education
A263. Any formal course, workshop, or training covering project management processes and knowledge areas (in person or online, including bootcamps).
A264.
Create an account on pmi.org
Submit application with experience details
Wait for approval (5–10 days)
Pay the fee and schedule your exam
A265.
PMI Members: $405
Non-members: $555
Membership costs about $139 and provides other benefits too.
A266.
180 questions
230 minutes
2 breaks
Question types include: multiple choice, multiple response, matching, hotspot, and fill-in-the-blank
A267. Out of 180 questions, 175 are scored and 5 are pretest/unscored, used to validate future questions.
A268.
People (42%) – Leadership, communication, conflict
Process (50%) – PM processes and techniques
Business Environment (8%) – Strategy, compliance, and value
A269. Over 50% of the PMP exam now includes Agile and hybrid methodologies, in line with real-world trends and PMBOK 7.
A270.
Follow a structured study plan
Use PMBOK + Agile Practice Guide
Enroll in a prep course
Take mock exams
Review weak areas systematically
A271.
PMBOK Guide 7th Edition
Agile Practice Guide
Rita Mulcahy’s PMP Prep
PM PrepCast
LinkedIn Learning PMP Path
PMP mock tests (e.g., PrepCast, Udemy)
A272. Most candidates spend 60–120 hours over 6–12 weeks preparing, depending on experience and availability.
A273.
Daily 1-hour focused sessions
Weekly mock tests
Flashcard reviews during downtime
Use tools like ezRACI to structure your study schedule with roles and deadlines
A274. No. The PMP exam is scenario-based, and the PMBOK is just one reference. You'll need to combine it with Agile frameworks, real-world application, and exam simulators.
A275. It provides foundational Agile concepts that appear heavily on the exam—especially around roles, ceremonies, mindset, and Agile planning techniques.
A276. Very important. Most questions are real-world scenarios requiring judgment and understanding of leadership, ethics, and trade-offs—not just definitions.
A277. PMI does not disclose a fixed score, but most experts estimate a passing score of around 70–75%. Scoring is based on psychometric analysis.
A278. You can retake the exam up to 3 times in one year. Analyze your performance report and focus on weaker domains before reattempting.
A279. A random selection process where PMI verifies your experience and education claims. You’ll be asked to submit documentation—just be honest and keep records!
A280. ezRACI can serve as a study plan accountability tracker—assigning yourself or a peer Responsible/Accountable roles for sections, milestones, and review sessions. You can also create Gantt timelines to structure weekly goals.
Includes RACI, Gantt charts, and practical project documentation use
A281. Software or systems that help project managers plan, execute, monitor, and control projects—including Gantt charts, task boards, RACI matrices, dashboards, and resource trackers.
A282. A Responsibility Assignment Matrix that maps each task or deliverable to who is:
Responsible
Accountable
Consulted
Informed
It’s critical for role clarity and reducing ambiguity in execution.
A283. Use it at the start of any project or phase, especially during planning, role changes, or cross-departmental handoffs. It’s also useful when stakeholder confusion or delays begin to surface.
A284.
Clarifies responsibilities
Prevents duplicate work
Improves communication
Increases stakeholder accountability
Reduces conflict and confusion
A285. Spreadsheets, project templates, whiteboards—or specialized software like ezRACI, which offers dynamic, real-time, shareable RACI matrices with Gantt overlay capabilities.
A286. A Gantt chart is a timeline view of project tasks, showing start/end dates, dependencies, progress, and resource assignments. It's essential for visualizing project timelines.
A287.
Tasks or milestones
Start and end dates
Duration
Dependencies
Progress tracking
Resource assignments (optional)
A288.
Easy timeline visualization
Highlights overlaps and critical path
Enhances stakeholder communication
Assists with deadline and dependency tracking
Supports progress monitoring
A289. During project planning and tracking, especially for longer or complex efforts involving multiple teams, phases, or dependencies.
A290. Gantt charts show what’s being done and when, while RACI shows who’s doing what. Together, they provide a complete view of ownership and timing, which ezRACI integrates natively.
A291. A formal document that authorizes the project, names the PM, defines high-level scope, objectives, constraints, and identifies key stakeholders.
A292. A hierarchical breakdown of project deliverables into smaller, manageable work packages. It's the basis for estimating, scheduling, and assigning RACI roles.
A293. The approved version of the schedule that’s used to measure progress and control variances throughout execution.
A294. A tool used to track:
Risks
Assumptions
Issues
Dependencies
It’s often part of a PM’s regular reporting process.
A295. A log of experiences, challenges, and solutions documented throughout the project, typically updated during retrospectives or closing phases.
A296. A document that outlines how communication will be handled, including frequency, formats, channels, audiences, and who is responsible.
A297. A document listing all stakeholders, including their role, power, interest, communication needs, and preferred engagement method.
A298. A comprehensive document that integrates all subsidiary plans (scope, schedule, cost, quality, etc.) to guide project execution and control.
A299. Templates reduce startup time, promote consistency, ensure nothing is forgotten, and support compliance—especially valuable in regulated environments.
A300. ezRACI includes pre-built templates for RACI matrices, Gantt timelines, compliance frameworks, and stakeholder workflows, making it easy to standardize operations, speed up planning, and ensure every project starts with clarity.
Aligned to PMBOK lifecycle models and common delivery frameworks
A301. A series of phases that a project goes through from start to finish. Each phase represents a logical progression of work and decision points, tailored to organizational needs.
A302.
Initiation
Planning
Execution
Monitoring & Controlling
Closing
These phases may be iterative, sequential, or overlapping.
A303.
Project Lifecycle: Focuses on the work to build the product
Product Lifecycle: Focuses on the product's existence from launch to retirement
A304. A checkpoint between project phases where the project is evaluated before proceeding. It involves go/no-go decisions based on performance, ROI, or compliance.
A305.
Predictive (Waterfall): Scope is known; work follows a defined sequence
Iterative: Feedback drives progressive refinement
Adaptive (Agile): Work is broken into small increments with regular reviews and re-planning
A306. When requirements are stable and well-defined, like infrastructure or compliance-driven projects.
A307. When requirements are evolving, when rapid feedback is needed, or the final solution is uncertain (e.g., software development, innovation projects).
A308. A model where the project delivers usable chunks of the product in each iteration. Each increment builds on the previous one until completion.
A309. A progressive elaboration technique where near-term work is planned in detail, while future work is kept at a higher level and detailed later.
A310. Performing phases or activities in parallel instead of sequentially to compress the schedule. It introduces risk if rework is needed.
A311. Adding additional resources to critical tasks to accelerate the schedule. It increases cost and potentially reduces quality.
A312. A significant point or event in the project. Milestones are often used to mark phase transitions, approvals, or key deliverables.
A313. Any tangible or intangible output produced as part of the project, such as reports, software modules, designs, or prototypes.
A314. Finalizing all activities to formally complete the phase or project. This includes deliverable acceptance, resource release, and lessons learned.
A315. The practice of continuously refining the plan and deliverables as more information becomes available.
A316. Starting the next phase before the current one is fully complete. Used to compress schedules, though it increases risk.
A317. A formal meeting to align stakeholders, introduce the project team, and review the project charter, scope, and high-level plan.
A318. The sequence of tasks that determines the shortest possible project duration. Delay on any critical path task delays the project.
A319. Based on:
Stakeholder involvement
Risk tolerance
Requirement stability
Team experience
Industry standards
A320. ezRACI enables teams to define RACI roles across lifecycle phases, visualize dependencies using Gantt charts, and document decisions, deliverables, and phase transitions clearly—supporting both Agile and traditional approaches.
Focused on change control, impact analysis, and stakeholder alignment
A321. Change management is the structured approach to controlling, evaluating, and implementing changes to a project’s scope, timeline, budget, or quality.
A322.
New stakeholder requirements
Unexpected risks
Resource constraints
External regulations
Shifting business priorities
A323.
Identify change
Document the request
Perform impact analysis
Review and approve/reject
Implement change
Update documentation
A324. A formal document used to submit and evaluate proposed changes, often including origin, reason, impact, and urgency.
A325. A process to assess how a proposed change would affect:
Scope
Schedule
Budget
Resources
Risks
Stakeholders
A326. A designated group that reviews and approves/rejects change requests based on the project’s impact and alignment with goals.
A327. The PM ensures that:
All changes are documented
Impact is assessed
Stakeholders are informed
Approved changes are implemented and tracked
A328.
Configuration Management: Ensures consistency of product specifications
Change Control: Ensures project changes are tracked and controlled
They work together to preserve system integrity.
A329. Uncontrolled expansion of project scope without corresponding adjustments to time, cost, or resources. It’s often caused by poor change control or unclear RACI roles.
A330. It records all changes, including their status, decisions, and justifications. It serves as a historical audit trail for compliance and lessons learned.
A331.
Use structured communication plans
Tailor messages to roles
Update dashboards, send formal notices
Use RACI matrices to clarify impact and next steps
A332.
Corrective actions
Preventive actions
Defect repairs
Scope changes
Schedule or cost adjustments
A333. Changes initiated to avoid potential future issues, like updating outdated processes or increasing test coverage.
A334.
Have a clear scope baseline
Use a RACI matrix to assign change control roles
Implement a formal change request process
Involve key stakeholders in early reviews
A335. Stakeholders or teams become overwhelmed or disengaged from too many project changes, often due to poor prioritization or communication.
A336.
Approved: Sanctioned by CCB or sponsor
Implemented: Changes that have been fully executed in the plan
A gap between the two causes confusion.
A337. Agile embraces change by design, using short cycles (sprints), product backlogs, and continuous feedback—making it less disruptive than in predictive models.
A338.
Waterfall: Requires formal review and documentation
Agile: Change is built into iterations and backlog refinement
A339.
Use Agile for flexible components
Use formal change control for fixed elements
Sync changes through integrated tools like ezRACI that show who owns what in both Agile and traditional streams
A340. ezRACI allows you to:
Assign RACI roles to each change request
Track approvals and dependencies on Gantt charts
Show which stakeholders are Informed or Consulted
This visibility streamlines change implementation and avoids bottlenecks.
Core topic for scoping, estimating, and planning effectively
A341. A WBS is a hierarchical decomposition of project deliverables into smaller, manageable components called work packages.
A342. To break complex work into smaller, more manageable tasks, making it easier to estimate cost and duration, assign resources, and track progress.
A343.
Levels (phases or deliverables)
Work packages (lowest level tasks)
WBS codes (numbering system)
Each level provides greater detail.
A344. The lowest-level element in a WBS that can be estimated, assigned, scheduled, and tracked independently.
A345. The WBS must include 100% of the project scope—nothing more, nothing less. Every deliverable must be accounted for.
A346. By identifying all work packages, it allows PMs to accurately estimate costs, assign budgets, and control scope creep.
A347.
WBS: Focuses on deliverables
Task list: Focuses on actions
WBS is structured by outcomes; tasks are derived from WBS items.
A348. A supporting document that explains each work package—including scope, deliverables, responsible parties, resources, risks, and acceptance criteria.
A349. It eliminates ambiguity, ensures clarity, and helps prevent rework or overlap by detailing exactly what is included in each component.
A350. Work packages from the WBS become activities in the project schedule, forming the foundation for timeline and Gantt chart creation.
A351. The process of subdividing project deliverables into smaller, more manageable parts to enable better estimation and assignment.
A352.
Identify major deliverables
Break down deliverables into smaller components
Continue until manageable work packages are formed
Assign WBS codes
Define in the WBS dictionary
A353. During the planning phase, right after scope definition. It’s a foundational input to cost, schedule, and resource planning.
A354. It becomes hard to manage, track, and maintain—resulting in micromanagement and unnecessary complexity.
A355. It leads to missed deliverables, vague assignments, inaccurate estimates, and increased risk of rework and scope creep.
A356. Yes! Agile teams can use a WBS to decompose features into epics, stories, and tasks. It's compatible with story mapping and backlog refinement.
A357. RACI roles can be assigned at the work package level to show exactly who is responsible, accountable, consulted, and informed for each deliverable.
A358. It provides clarity on what needs to be verified or validated and defines deliverables that will undergo quality reviews and sign-offs.
A359. It enables early identification of work scope gaps, promotes better estimates, and ensures ownership is assigned to all parts of the project.
A360. ezRACI allows users to import or create WBS structures and assign RACI roles to each work package, track progress via Gantt timelines, and ensure stakeholder accountability at every level.
Key for planning, tracking, and accelerating project timelines
A361. It’s the process of planning, estimating, scheduling, and controlling the time allocated for project tasks to ensure timely completion of the project.
A362. Identifying and documenting the specific actions needed to produce deliverables. Activities are derived from WBS work packages.
A363. Determining the logical order of activities, considering dependencies and constraints. It creates the foundation of the project schedule.
A364. Classifying how tasks relate:
FS (Finish-to-Start)
SS (Start-to-Start)
FF (Finish-to-Finish)
SF (Start-to-Finish)
These are used to build the project network diagram.
A365. A visual representation of activity sequencing, showing dependencies and paths from project start to finish. It's used for critical path analysis.
A366. A technique to identify the longest sequence of dependent tasks that determines the shortest time to complete the project. Any delay here delays the project.
A367.
List all activities
Estimate durations
Define dependencies
Map out paths
Identify the path with the longest duration
A368.
Float (or slack) is the amount of time a task can be delayed without delaying the project
Calculated as LS – ES or LF – EF
A369.
Total Float: Time a task can be delayed without affecting the project end date
Free Float: Time a task can be delayed without delaying the start of the next dependent task
A370. It shows the most time-sensitive tasks—those with zero float. Managing these tightly is essential for on-time delivery.
A371.
Fast-tracking: Overlapping tasks
Crashing: Adding more resources
Both increase risk and cost but can compress schedules.
A372. A key point in the schedule, often marking the completion of a phase, approval, or external dependency. Milestones have zero duration.
A373. The approved version of the schedule, used to measure performance and track variance during execution.
A374. SV = EV – PV
A measure of how much ahead or behind schedule the project is in terms of value earned.
A375. SPI = EV / PV
1 means ahead of schedule, <1 means behind. It's a key Earned Value metric.
A376. It shows tasks, start/end dates, durations, and dependencies over time. Gantt charts help track progress, overlaps, and schedule adherence.
A377. Tasks with float can be deferred or shifted, helping PMs optimize resource use without affecting deadlines.
A378.
Baseline: Original approved plan
Actual: What really happened
The comparison reveals delays or early finishes.
A379.
MS Project
Primavera
Smartsheet
JIRA
ezRACI (combines Gantt + RACI role tracking for timelines)
A380. ezRACI allows users to define tasks, assign RACI roles, and visualize all dependencies via Gantt charts. This makes schedule accountability crystal clear—perfect for PMs juggling complex timelines.
Real-world soft skills that PMP test and real PMs need every day
A381. Because miscommunication is the #1 reason projects fail. Clear, consistent, and tailored communication builds trust, engagement, and alignment.
A382.
Interactive: Meetings, calls, chats
Push: Emails, memos, status reports
Pull: Shared dashboards, portals, wikis
A383. Analyze stakeholders’ power, influence, interest, and role, then tailor communication frequency, tone, and format accordingly.
A384.
Communication plans
RACI matrices
Stakeholder registers
Dashboards
ezRACI timelines with communication responsibilities
A385.
Active: Two-way exchange (calls, meetings)
Passive: One-way consumption (status reports, dashboards)
A386. A formal document outlining how stakeholders will be engaged, what messages they’ll receive, and what channels will be used.
A387.
Unaware
Resistant
Neutral
Supportive
Leading
Your goal is to move everyone closer to “Supportive” or “Leading.”
A388.
Identify root cause (e.g., unmet need, lack of clarity)
Listen empathetically
Involve them early
Use a RACI matrix to define boundaries and expectations
A389.
Competing priorities
Misaligned goals
Poor communication
Role ambiguity
Lack of involvement
A390.
Collaborate (win-win)
Compromise (partial satisfaction)
Force (authority-based)
Withdraw (delay resolution)
Smooth (downplay differences)
Collaboration is usually best.
A391.
Conflict resolution: Handled by PM or team internally
Escalation: Raised to higher authority due to scope, authority, or risk
A392.
Set clear roles and expectations using RACI
Communicate early and often
Encourage transparency
Document decisions
A393. Ensuring all stakeholders understand and agree on goals, roles, and scope. Misalignment leads to rework, delays, and dissatisfaction.
A394. When stakeholders become disengaged due to overcommunication, constant changes, or unclear progress. Fix it with streamlined updates and clear accountability.
A395.
Invite them to demos and reviews
Include them in backlog refinement
Keep communication frequent and transparent
Use tools like ezRACI for shared visibility into ownership and progress
A396. A technique to visualize stakeholder influence, interests, and relationships. Helps PMs identify power dynamics and build effective engagement strategies.
A397.
Survey feedback
Participation in meetings
Speed of approvals
Willingness to contribute resources
Sentiment tracking
A398. By clearly showing who makes decisions and who provides input, RACI matrices reduce overlap, clarify responsibilities, and improve transparency.
A399. ezRACI assigns RACI roles to every initiative, making stakeholder communication intentional and trackable. You can use Gantt views, notes, and real-time updates to inform and align key stakeholders.
A400. Build a project-level RACI matrix and review it with all key stakeholders. It instantly clarifies roles, prevents finger-pointing, and creates shared understanding.
Helping PMs prove value, track progress, and drive data-informed decisions
A401. KPIs (Key Performance Indicators) are quantifiable metrics used to assess project performance in areas like schedule, budget, quality, and stakeholder satisfaction.
A402. A KPI should be:
Specific
Measurable
Achievable
Relevant
Time-bound
(aka: SMART)
A403.
Schedule Variance (SV)
Cost Variance (CV)
Earned Value (EV)
Customer Satisfaction
% Tasks Completed
Risk Exposure
Resource Utilization
Budget Burn Rate
A404. A technique that integrates scope, schedule, and cost data to assess performance. It includes metrics like EV, PV, AC, SPI, and CPI.
A405. The authorized budget assigned to scheduled work at a point in time. It’s the baseline to compare against actuals.
A406. The budgeted value of the work actually completed by the status date. It shows true project progress.
A407. The real cost incurred for work performed by the reporting date. Used to assess budget efficiency.
A408. CPI = EV / AC
CPI > 1 = under budget
CPI < 1 = over budget
CPI = 1 = on budget
A409. SPI = EV / PV
SPI > 1 = ahead of schedule
SPI < 1 = behind schedule
A410.
Lagging: Reflect past performance (e.g., variance, quality defects)
Leading: Predict future performance (e.g., velocity trends, risk exposure)
A411. Depends on project complexity and stakeholder needs—weekly for tactical updates, monthly for strategic reviews, and real-time dashboards for critical data.
A412. A visual display that shows current status of schedule, budget, scope, risks, and issues—often using red/yellow/green indicators (RAG status).
A413.
Number of open risks
% of mitigated risks
Average time to close a risk
Risk exposure by category
Risk response effectiveness
A414.
Defect density
% of tests passed
Rework effort
Customer-reported issues
Compliance to acceptance criteria
A415.
% capacity used
Actual hours vs planned
Team member allocation
Task completion rate by role
A416.
Status reporting: Point-in-time snapshot
Progress reporting: Compares actuals against baseline over time
A417. Reporting that shows differences between planned and actual performance, helping PMs investigate root causes and corrective actions.
A418.
Feedback surveys
Net Promoter Score (NPS)
Qualitative interviews
Engagement levels (attendance, input, collaboration)
A419. ezRACI provides automated role-based reporting, dynamic RACI views, and Gantt overlays—making it easy to visualize ownership, deadlines, and blockers for stakeholders at every level.
A420. By assigning who is Responsible and Accountable for each KPI, RACI matrices prevent finger-pointing and ensure timely metric updates across workstreams—especially in cross-functional teams.
Critical for PMP success and leading high-performing teams
A421. Ethics builds trust, transparency, and credibility—essential qualities for stakeholder support, team alignment, and long-term success.
A422. A guideline that outlines expected behavior in four key areas:
Responsibility
Respect
Fairness
Honesty
A423. Owning decisions and their consequences—accepting accountability and avoiding blame-shifting.
A424. Valuing diverse perspectives, cultural differences, and individual contributions, and treating everyone professionally.
A425. Making impartial decisions, avoiding favoritism, and disclosing conflicts of interest.
A426. Providing truthful information, avoiding deception, and setting realistic expectations.
A427. Disclose the conflict immediately, avoid decision-making in affected areas, and follow your organization's escalation procedures.
A428. Acting in alignment with values, standards, and agreements, even when it's hard or unpopular.
A429.
Document observations
Address privately and respectfully
Escalate via appropriate channels if behavior continues
Use PMI’s Code of Ethics as a reference
A430. A leadership philosophy where the PM supports, empowers, and enables their team—putting others’ needs ahead of their own authority.
A431. EQ is the ability to recognize, understand, and manage emotions—your own and others’. High EQ leads to better collaboration, leadership, and conflict resolution.
A432.
Self-awareness
Self-regulation
Motivation
Empathy
Social skills
A433. Choosing actions that are not only effective, but also morally sound and aligned with organizational and societal values.
A434. Assess the ethical, quality, and legal risks. Communicate concerns to stakeholders and escalate if necessary. Prioritize long-term integrity over short-term gain.
A435. Creating a culture where all voices are heard and valued, regardless of background, role, or style. This enhances creativity and decision-making.
A436. By demonstrating honesty, punctuality, empathy, follow-through, and transparency. Teams mirror what leaders model.
A437. It erodes trust, increases turnover, undermines stakeholder confidence, and can lead to project failure or reputational damage.
A438. Reporting unethical or illegal activity within the organization—ideally through a protected and anonymous process.
A439. By encouraging open communication, not punishing mistakes, listening actively, and respecting diverse viewpoints. Safe teams are high-performing teams.
A440. ezRACI promotes transparent responsibility and accountability, eliminates role confusion, and reduces bias by ensuring roles are assigned by function, not favoritism—creating a fairer, more trust-driven project culture.