PMP: Project Management Professional PMP: Project Management Professional (PMI) Project Management Institute (PMI) - Certified PMP 1 / 120 A critical system integration requires a full end‑to‑end environment, but your agile‑hybrid release trains only spin up ephemeral test environments per sprint. The integration team needs stable shared environments, yet cost constraints discourage long‑living environments. How can you satisfy both needs? Require each team to maintain its own long‑living environment. Use local developer machines for integration testing. Implement a “golden” integration environment that is refreshed nightly from sprint artifacts and shared across trains, with strict access rules. Delay integration until after all sprints complete. 2 / 120 Your global hybrid project operates across five time zones. Daily stand‑ups are at 8 AM PST, which is midnight for some team members, leading to poor participation. Which adjustment respects both agile principles and global constraints? Keep the time fixed and require attendance. Rotate the stand‑up time each sprint so no one is always at an inconvenient hour, and record meetings for those who can’t attend. Eliminate daily stand‑ups and replace them with asynchronous status emails. Split the team into two pods, each with its own stand‑up. 3 / 120 Your hybrid project leverages feature toggles to deploy incomplete features safely. However, toggles have proliferated to 30+ in production, causing technical debt and complexity for testers. What is the best plan to manage toggle debt in an agile‑hybrid context? Ignore the toggle count and focus on functionality. Postpone toggle clean‑up to a dedicated refactoring project after release. Include toggle clean‑up tasks in every sprint until count is below a threshold, and enforce a “toggle retirement” step in the Definition of Done. Remove all toggles at once in a single maintenance window. 4 / 120 A key external auditor expresses concern that your agile teams don’t produce traceable documentation for every release, as required by company policy. The audit could block go‑live. What hybrid documentation strategy addresses the audit without heavy overhead? Write separate detailed design documents for each sprint. Provide raw code repositories as evidence. Defer audit until after go‑live. Generate automated release notes and link them to user‑story IDs, ensuring traceability. 5 / 120 Your hybrid project tracks critical defects in a traditional defect‑tracking tool, while your agile team logs user stories in Jira. As defects rise, visibility is poor and resolution time lags. Which integrated process improves defect tracking and resolution? Abandon the defect tool and log everything in Jira. Retain separate tools and manually reconcile weekly. Integrate the defect tool with Jira to sync critical defects as high‑priority backlog items, and enforce rapid triage within sprints. Create a separate defect‑resolution team outside of agile. 6 / 120 You’re adopting an agile‑hybrid model in a highly regulated banking environment. Every feature must pass security and compliance checklists before deployment. These checks happen outside of your sprint cycles and cause hand‑offs and context loss. What streamlined approach maintains compliance without multiple hand‑offs? Move all security checks to a final “compliance sprint.” Embed a compliance engineer directly in each agile team to perform in‑sprint security reviews. Outsource compliance reviews to an external audit firm post‑release. Rotate compliance responsibilities among developers in each sprint. 7 / 120 The organization’s agile CoE mandates backlog refinement every week, but your hybrid project sprint length is three weeks. The team feels refinement sessions are too frequent and disrupt flow. What’s the best scheduling compromise? Shift to two‑week sprints to match refinement. Schedule refinement sessions every other week and at sprint mid‑point, aligning cadence with team rhythm. Continue weekly refinements regardless of feedback. Eliminate formal refinement and handle revisions during planning. 8 / 120 Your hybrid project uses traditional schedule baselines for hardware procurement but agile planning for software. A late vendor price increase threatens both hardware budget and the sprint cost forecasts. How should you manage this dual‑track risk? Absorb the cost in agile contingency reserves only. Request a change order on the hardware contract and ignore sprint forecasts. Delay procurement to the next fiscal cycle. Treat the vendor increase as a project‑level risk, update both the cost baseline and the sprint budget forecasts, and communicate to stakeholders. 9 / 120 A critical team member skilled in both agile facilitation and technical design is overwhelmed acting as both Scrum Master and lead architect. Sprints are slipping and design decisions stall. What hybrid role‑management approach addresses this? Rotate Scrum Master duties among team members each sprint. Split the role: appoint a dedicated Scrum Master and a separate technical lead, redefining responsibilities. Hire an external coach to assist only on design issues. Consolidate both responsibilities under a single project manager. 10 / 120 Mid‑project, your sponsor approves a scope increase that adds several high‑priority epics. You have no additional budget. Your plan uses Agile Release Trains with PI (Program Increment) planning every 10 weeks. What is the best way to incorporate the new epics? Insert an ad‑hoc planning session immediately to triage and add stories to the current PI, risking overload. Push the extra epics to the end of the current PI’s stretch objectives. During the next PI planning, re‑rank all features, adjust capacity allocations, and update the program backlog. Reject the scope increase until budget is secured. 11 / 120 You’re leading a hybrid transformation pilot: some teams are fully agile, others remain waterfall. You must roll out common tooling. The agile teams relish lightweight boards, while the waterfall teams need detailed task logs and approvals. How do you implement a unified toolset that supports both styles? Standardize on waterfall views only to keep compliance. Deploy two separate tools and integrate them via middleware. Choose the agile board functionality only and train waterfall teams on agile. Configure the tool to offer both a Kanban/Scrum board and a Gantt view, with customizable workflows per team. 12 / 120 Senior management insists on monthly steering‑committee reports with earned value metrics, yet your agile teams track progress via story points and velocity. The translation between these metrics is error‑prone. Which approach bridges agile metrics and earned value reporting best? Ignore earned value; report only agile metrics. Map story points to budget cost using a “cost per point” conversion factor, and calculate EV accordingly. Run a parallel earned‑value tracking system outside of sprint tools. Report only schedule variance using sprint forecasts. 13 / 120 Your product increments depend on a third‑party API that changes frequently. The API team follows strict waterfall release cycles, while your team moves in two‑week sprints. These mismatched cadences lead to integration failures at sprint boundaries. What hybrid practice helps synchronize both teams? Establish a bi‑weekly integration sprint where both teams collaborate on API changes. Freeze API interface for the duration of your sprint, regardless of their release schedule. Outsource API integration to a separate sub‑team that buffers interface changes. Switch your team to align with the API team’s waterfall schedule. 14 / 120 In your agile‑hybrid project, regulatory compliance requires that each deliverable passes a formal design review. These design reviews take three days and can’t occur within a sprint. How do you structure sprints to incorporate these external reviews? Plan a “hardening sprint” every third sprint focused solely on design reviews. Include design review tasks in each sprint and accept the overflow into the next sprint. Schedule design reviews at the end of each sprint but outside sprint timebox, and treat them as part of the release process. Push design reviews into a post‑release phase managed by a separate team. 15 / 120 You’re coaching a team that uses a hybrid approach: Scrum for feature development and Kanban for support tickets. The team complains that context switching between sprints and Kanban flow is causing delays and confusion about priorities. What’s the best practice to streamline workflow without losing methodological benefits? Create dedicated swim lanes in the same board—one for sprint items, one for support tickets—and enforce WIP limits per lane. Alternate between two-week sprints and one-week Kanban windows. Merge both workflows into a single Kanban board and abandon sprints. Assign separate teams to Scrum and Kanban work. 16 / 120 Your organization’s PMO mandates that cost and schedule baselines be locked before execution, but your team needs to reprioritize backlog items based on user feedback. The locked baselines hinder the ability to adapt to change. Which tactic best accommodates both constraints? Define release‑level baselines for cost and schedule, and allow flexible backlog reprioritization within each release. Request a formal change request for every backlog reprioritization. Negotiate with the PMO to treat backlog prioritization as out‑of‑scope work Freeze backlog after sprint zero and only reprioritize in the next phase. 17 / 120 A new stakeholder enters mid‑project and demands a detailed Gantt chart for all remaining work. Your team has been working from a prioritized backlog and burn‑down charts. Providing the Gantt chart will require significant effort and may date quickly. What hybrid approach can you use to satisfy this stakeholder while preserving agile delivery? Generate a rolling‑wave Gantt chart based on current backlog estimates and update it at the end of each release. Export the sprint backlog to a project‑management tool and lock it for the stakeholder’s view only. Agree to a one‑time Gantt chart and then transition stakeholder to agile metrics. Refuse the request, explaining that Gantt charts are not compatible with agile. 18 / 120 You manage a hybrid project delivering a packaged software release. The first release is scheduled in four weeks via two-week sprints. Compliance documentation must accompany every release. The compliance lead cannot participate in sprint events due to other priorities, and sign‑offs are running two sprints behind, blocking demos to external partners. How should you integrate compliance into your agile workflow without derailing velocity? Assign a proxy compliance reviewer within the development team to sign off on artefacts. Extend each sprint by two days to allow compliance sign‑off before sprint review. Include compliance tasks in the Definition of Done and treat them as “must‑have” acceptance criteria. Shift compliance work to a post‑sprint phase managed waterfall‑style. 19 / 120 In your hybrid project, the governance board requires detailed design documents and sign‑off before any development can begin. However, the agile teams need to iterate on prototypes rapidly. You notice tension between completing upfront documentation and enabling fast feedback cycles, causing team morale to drop. What is the best approach to balance governance and agility? Propose a “lightweight requirement baseline” consisting of high‑level design artefacts that can be incrementally elaborated during sprints. Insist the governance board waive the sign‑off requirement for prototypes and only enforce it before release. Create parallel tracks: one team handling documentation waterfall‑style and another doing agile prototyping. Delay sprint start until full design documentation is approved to avoid rework. 20 / 120 You’re the Scrum Master for a distributed team working on a hybrid project: the front‑end UI is developed via Scrum sprints, while the back‑end infrastructure is delivered in a traditional waterfall cadence. Mid‑sprint, the infrastructure lead informs you that a critical API endpoint will be delayed by two weeks, which will block several user‑story completions. The Product Owner still expects a full sprint review. What is the most appropriate way to handle this situation? Call an impromptu backlog grooming session to split affected user stories into frontend‑only deliverables and defer the blocked portions. Ask the infrastructure lead to join the next stand‑up and negotiate overtime to meet the sprint goal. Report the delay to stakeholders and cancel the sprint review in favor of a status‑update meeting. Convert the two-week infrastructure delay into a risk and add buffer tasks into the sprint planning for future iterations. 21 / 120 A strategic pivot in your organization shifts funding priorities away from your project’s original business case. The sponsor asks you to continue as planned while seeking new benefits. How should you handle this? Continue execution and deliver as originally scoped, hoping for restored funding Convene a project reassessment workshop to realign scope, objectives, and benefits with the new strategy, then update the business case. Suspend the project until funding returns. Escalate to the PMO for directive. 22 / 120 You’re transitioning your team from a legacy on‑premises toolset to a new cloud‑based collaboration platform. Adoption is low, and productivity lags. What’s the best strategy to drive adoption and minimize disruption? Mandate the new tool immediately and deactivate the legacy system. Provide targeted training, appoint tool champions in each functional area, and run a parallel pilot for high‑value teams. Roll back to the legacy system until full feature parity is achieved. Outsource tool administration to a third‑party managed service provider. 23 / 120 Your project’s KPI dashboard shows that resource utilization is at 95% for the past three weeks, and team morale surveys report rising burnout risks. What proactive measure should you take? Mandate overtime to maintain delivery dates. Reassign some scope to future phases and onboard additional skilled resources. Ignore utilization metrics and focus on project deadlines. Request the sponsor to lower performance expectations 24 / 120 A newly onboarded stakeholder demands last‑minute changes just before your QA cycle. These changes will likely introduce defects and cause rework. What’s the ethical and process‑aligned response? Agree to the changes and extend the QA cycle without cost approval. Document the change request, assess its impact, and submit it through the formal change control process. Reject the stakeholder outright to protect project stability. Implement the changes in production with a rollback plan. 25 / 120 During a governance audit, you find the project’s risk responses were not tracked in Performance Reports, despite being implemented. The auditor flags a compliance issue. What corrective action will both address the audit finding and improve future reporting? Update the risk register with implemented responses and modify the Performance Reporting Plan to include risk response status. Provide verbal assurances to the auditor that responses were executed. Exclude risk responses from future reports to simplify tracking. Create a separate risk response tracking spreadsheet outside of formal reports. 26 / 120 A global stakeholder group requires project artifacts in English, Spanish, and Mandarin. Translating every document will consume 15% of your budget. Which approach optimizes cost while meeting requirements? Translate only executive summaries in all three languages and full detail in English. Use machine translation for all artifacts, followed by peer review. Hire three professional translators for each language for all documents. Publish in English and require stakeholders to use browser translation tools. 27 / 120 Your sponsor asks you to accelerate delivery by skipping non‑critical testing phases. The QA lead warns of increased defect risk and reputational harm. What should you do first? Comply with the sponsor’s request to maintain stakeholder satisfaction. Convene a risk‑impact assessment meeting with QA, DevOps, and business analysts to evaluate consequences. Escalate the sponsor’s directive to the PMO for guidance. Negotiate scope by deferring a minor feature instead of testing phases. 28 / 120 You discover a new regulation mid‑project that invalidates part of your data‑privacy approach. Revising your architecture will require three additional sprints and significant budget impacts. How should you handle this change? Log it as a new risk and evaluate its impact in the next risk review. Initiate a formal change request with updated impact analysis for scope, schedule, cost, and compliance before taking action. Proceed with the original plan and address compliance retroactively in a future release. Escalate to legal for an exemption request. 29 / 120 A high‑impact risk materializes: a key subcontractor declares bankruptcy. Your risk register had identified financial instability as a medium‑probability risk. What’s the immediate priority? Trigger the risk response plan: engage your secondary backup subcontractor under the pre‑negotiated standby agreement. Escalate the issue to the sponsor and pause all related activities until funding is confirmed. Negotiate with the bankrupt subcontractor’s administrator to continue partial work. Update the risk register and wait for the contingency reserve decision. 30 / 120 Your agile‑hybrid project uses two‑week sprints, but regulatory documentation requires formal sign‑off on each deliverable heatmap. The sign‑off process takes four weeks, causing a backlog. What’s the best way to integrate regulatory control without derailing the sprint cadence? Extend sprint length to four weeks to accommodate sign‑off. Include a “regulatory ready” exit criterion in each sprint and hold parallel sign‑off workflows. Move documentation tasks into a separate waterfall track. Defer regulatory sign‑off until after product release. 31 / 120 Stakeholder sentiment surveys indicate declining trust in project leadership after a series of communication breakdowns. Which corrective action should the project manager take to rebuild trust and transparency? Increase the frequency of status meetings without changing the format. Institute an open “office hours” policy where any team member can raise concerns directly. Circulate all meeting minutes and decision logs publicly within the project workspace Create a stakeholder advisory committee to co‑review key project artifacts. 32 / 120 A critical path activity is crashing due to resource shortages. You need to accelerate without adding headcount or increasing risk substantially. Which schedule compression technique is most appropriate? Fast‑track by overlapping design and testing activities, acknowledging higher rework risk. Crashing by authorizing 24/7 shifts for existing resources. Resource leveling to spread effort evenly across the schedule. Rebaseline the schedule and extend the deadline. 33 / 120 You are negotiating a Statement of Work (SOW) with a strategic partner. They propose a cost‑plus contract, but you’re concerned about potential cost overruns and lack of incentive for efficiency. What contract type would better align incentives with performance? Firm‑fixed‑price with performance‐based milestones Time‑and‑materials with a cost cap Cost‑plus‐award‐fee tied to stakeholder satisfaction metrics Indefinite delivery/indefinite quantity (IDIQ) contract 34 / 120 Late in execution, your cost performance index (CPI) drops below 0.9. The sponsor demands you bring cumulative costs back within budget before the next steering committee. Which action is most consistent with PMI’s ethics and best practices? Reallocate contingency reserves from a low‑risk work package to cover current overruns without sponsor approval. Request a formal scope review with the Change Control Board to trade scope features for cost savings. Adjust the estimate at completion (EAC) to reflect current performance and obtain sponsor sign‑off on additional funding. Delay the next invoice to stakeholders until costs realign with the budget forecast. 35 / 120 Your project charter includes a high‑level benefit of “improved customer satisfaction.” During execution, stakeholders debate how to measure this nebulous benefit. What’s the best approach to bring clarity and ensure measurable outcomes? Convene a benefits realization workshop to define specific KPIs (e.g., NPS scores, customer retention rates) and align on measurement frequency. Assign the product owner to develop a survey instrument after go‑live and report results in the first benefits review. Use industry benchmarks to set a target satisfaction score and track actual performance against it. Document “customer satisfaction” as a qualitative benefit, accepting its subjectivity. 36 / 120 A key stakeholder insists on daily status reports via email, while the distributed team prefers asynchronous updates in your collaboration tool. The overload of emails is causing confusion and lost information. Which communication plan adjustment best balances stakeholder needs and team efficiency? Continue daily emails but add hyperlinks to the collaboration tool for detailed data. Propose a daily 10‑minute video stand‑up recorded and posted to the collaboration platform, replacing email reports. Create a custom dashboard that auto‑sends a concise summary via email at a time preferred by the stakeholder. Compromise with twice‑weekly email reports and encourage self‑service access to real‑time project data. 37 / 120 In a matrix organization, one of your senior subject‑matter experts has been repeatedly reassigned by their functional manager during critical design sprints, causing bottlenecks. What is the most collaborative way to ensure sustained SME availability without escalating conflict? Negotiate a formal Resource Management Agreement with the functional manager, defining dedicated capacity for your project. Request the sponsor to reassign the SME permanently to your project. Document the delays in an Issues Log and ask the functional manager to address the resource risk Escalate directly to the PMO to override the functional manager’s assignments. 38 / 120 Your software rollout to 5,000 users is behind schedule because testing in one market uncovered severe localization bugs. The defect backlog now threatens to delay go‑live in all other markets. What is the best risk‑response strategy to apply? Accept the delay, replan the overall schedule, and extend the budget contingency. Transfer the risk by outsourcing bug fixes to a third‑party testing and localization firm under a fixed‑price contract. Mitigate the risk by spinning up additional cross‑functional teams focused exclusively on localization defects, with overtime authorization. Avoid the risk by deploying to unaffected markets on schedule and isolating the problematic region for a later phased release 39 / 120 During the planning of a highly regulated pharmaceutical trial, your Quality Management Plan requires root‑cause analysis of any process deviations. A late‑stage audit uncovers inconsistent documentation practices across two regions, risking non‑compliance. Which tool or technique should you apply first to address the issue systematically? Conduct a Failure Mode and Effects Analysis (FMEA) to quantify potential impacts of documentation lapses. Use the Ishikawa (fishbone) diagram to map all potential causes of inconsistent record‑keeping. Escalate the finding to regulatory authorities and pause all trial activities until resolved. Facilitate a Kaizen event with cross‑functional teams to generate immediate corrective actions. 40 / 120 You’re leading a multinational infrastructure upgrade project. Mid‑execution, your vendor notifies you that a key hardware component will be delayed by six weeks due to a supply chain disruption. This delay will push critical path activities into the next fiscal quarter, jeopardizing your organization’s year‑end reporting goals and bonus structure. What is the most appropriate next step? Convene the Change Control Board to fast‑track approval of a schedule compression plan using both crashing and fast-tracking techniques. Update the project schedule with the new six‑week delay and negotiate a scope reduction to meet the original fiscal deadline. Engage the sponsor and stakeholders in a rebaseline discussion, presenting options for phased delivery or adjusted benefits realization timing Direct the procurement team to source an alternative vendor immediately, absorbing the additional cost to maintain schedule. 41 / 120 You’re closing a project and want to ensure all deliverables meet quality requirements. Which document should be reviewed? Scope statement Quality metrics Requirements traceability matrix Work performance information 42 / 120 You receive a request to change the project's scope. It will require additional budget and time. Who is responsible for approving this change? Project manager Project team Change control board Sponsor 43 / 120 You are leading a cross-functional project. Team members from different departments are not aligned on priorities. What is the best strategy to move forward? Let each department manage its own tasks Facilitate a prioritization workshop to build consensus Assign tasks directly based on your judgment Request departmental leads to make decisions 44 / 120 During project execution, a team member identifies a more efficient process to reduce costs. What should the project manager do? Immediately implement the idea Submit a change request Present it to the sponsor for approval Document it in the lessons learned 45 / 120 Your project is transitioning from planning to execution. Which document should be finalized and signed off before moving forward? Project charter Risk register Project management plan Issue log 46 / 120 You are managing a distributed team across three countries. What’s the best way to ensure consistent communication and understanding? Use email for all communications Use a centralized collaboration tool and agreed-upon protocols Let each team choose their own tools Communicate only with local leads 47 / 120 A project is behind schedule due to a late hardware delivery. To recover time, the project manager adds more technicians to the team. This is an example of: Fast tracking Resource smoothing Crashing Leveling 48 / 120 A project manager creates a scatter diagram to show a potential relationship between the number of overtime hours and defect rates. What is the project manager trying to determine? The root cause A trend A correlation Variability 49 / 120 The project sponsor requests a fast-tracked delivery. You decide to start construction before finalizing all designs, increasing risk. This is an example of Progressive elaboration Crashing Fast tracking Lead time 50 / 120 A key stakeholder frequently interrupts sprint planning with changing priorities. What’s the best way for the project manager to manage this behavior? Restrict the stakeholder from meetings Educate the stakeholder on the importance of backlog stability Allow the changes since the stakeholder is important Change the stakeholder's role in the project 51 / 120 The team has completed several sprints, but stakeholders are unhappy with the product's usability. What should the project manager do? Reassign the team Conduct a sprint review with stakeholders Change the product owner Extend the sprint duration 52 / 120 A project manager is monitoring a supplier’s performance using Service Level Agreements (SLAs). What process are they performing? Control Quality Control Procurements Monitor Communications Monitor Risks 53 / 120 During a project retrospective, the team identifies that poor communication led to unnecessary rework. What should the project manager do next? Update the project schedule Revise the communication management plan Conduct a root cause analysis Escalate the issue to the sponsor 54 / 120 After a team member leaves the project unexpectedly, the project manager updates the risk register to reflect the reduced team capacity. What process is being performed? Perform Qualitative Risk Analysis Implement Risk Response Monitor Risks Control Resources 55 / 120 You’re managing a project in a matrix organization. One of your resources is often pulled away by their functional manager, causing delays. What should you do first? Escalate the issue to the functional manager Raise the issue in a stakeholder meeting Document the impact in the risk register Discuss and renegotiate resource commitment 56 / 120 A project manager wants to visualize the trend of defects over multiple testing cycles. Which tool should they use? Histogram Scatter diagram Control chart Pareto chart 57 / 120 While managing a software deployment project, the customer requests a major change in features midway through execution. The team estimates it will impact the schedule and cost significantly. What is the next step the project manager should take? Reject the change request Implement the change and inform the sponsor Submit the request to the change control board (CCB) Escalate the issue to senior management 58 / 120 A project team member approaches the project manager to express discomfort with another team member's behavior. The project manager listens actively, empathizes, and works to resolve the issue collaboratively. What interpersonal skill is the project manager demonstrating? Problem-solving Emotional intelligence Negotiation Coaching 59 / 120 A project sponsor requests a high-level summary of current project performance to present to executives. What should the project manager provide? Detailed work performance data Work breakdown structure Milestone chart and project dashboard Raw earned value metrics 60 / 120 During a construction project, the project manager identifies that stakeholder expectations are misaligned with the project scope. To resolve this, the project manager decides to schedule a meeting to clarify deliverables and expected outcomes. What is the project manager aiming to achieve? Conflict resolution Stakeholder engagement and alignment Scope creep reduction Requirements elicitation 61 / 120 During a retrospective meeting, two team members disagree about their involvement in a recent work incident, accusing each other of dodging responsibility. To avoid such an issue in the future, the project manager decides to create a RACI matrix. RACI is an acronym for: Responsible, Accountable, Confirm, Inform Recommended, Accountable, Consulted, Inform Responsible, Accountant, Consulted, Inform Responsible, Accountable, Consulted, Inform 62 / 120 A project is 50% complete. During its planning phase, the project manager divided the project into 4 consecutive phases. Now that phase 2 is completed, they’re moving to phase 3. Based on the above table, how much is this project’s Earned Value (EV)? $4000 $5000 $6000 $10000 63 / 120 A project manager is managing a project that consists of implementing an accounting application for a pet store. During a project performance review meeting, they presented the following figures: AC = $4,000, PV = $5,000, and EV = $5,500. What does that indicate about the project? Since both the CV and SV are positive, the project is under budget and ahead of schedule These numbers are insufficient to calculate the project SPI and CPI Since the CV is negative, the project manager has probably spent more than they initially planned to Since the SV is negative, the project is behind schedule 64 / 120 A project manager joins a company, which has recently gone through major organizational changes. The new project manager is very concerned about the team’s lack of motivation and closely monitors when they arrive and leave work. What type of management style does the new project manager exhibit? Theory X Theory Y Theory Z Theory XY 65 / 120 A project manager makes sure that their team has a healthy work environment by providing safe working conditions, job security, and rewarding salaries, with an emphasis on work appreciation. According to Herzberg, which of the following options are NOT example of hygiene factors? Job security Salary Safe working conditions Appreciation 66 / 120 A project manager is managing a biodegradable packaging project. One of the team members informed the project manager that she identified a risk, the printing machine may need maintenance before the end of the project. The project manager estimates the risk’s probability of occurrence as 10% and its cost as $5,000. This risk’s expected monetary value is: $500 -$500 $4500 -$4500 67 / 120 Managing an electric car manufacturing project, a project manager is facing a complicated quality problem that they don’t understand its source and causes. They set a meeting with their team to discuss the matter and to initially trace the problem source back to its root cause. Pareto diagram Chain diagram Scatter diagram Why Why diagram 68 / 120 A project manager notices that his colleague, who is a fellow project manager, shows up at the office with new high-tech gadgets every day. This raises his suspicions that his colleague might be accepting gifts from hardware vendors who will be bidding on one of their company’s upcoming multimillion-dollar contracts. What should the project manager do next? Warn the concerned colleague that such gifts aren’t appropriate and leave it at that Convince his colleague to return the items and stop accepting any gifts from vendors Verify whether these items were gifts from vendors or he purchased them himself Report his colleague to the organization so that a conflict-of-interest investigation can take place 69 / 120 A project manager is assigned to an eco-friendly packaging project. In order to manage involved stakeholders, the project manager starts by analyzing their power, urgency, and legitimacy. Which analysis method is the project manager applying? Stakeholder cube Salience Model Power/Interest Grid Power/Influence Grid 70 / 120 An organization is deliberating over two potential projects that have exactly the same payback period. After doing a benefit measurement analysis, the project manager finds out that Project A has a lower Internal Rate of Return (IRR) than Project B. What project should the organization choose? Project A Project B There is no difference Available information not enough to make a decision 71 / 120 Your Agile team releases functionality every two weeks. A stakeholder insists on performing final acceptance testing only at the end of the project, citing risk of premature sign-off. What should you do? Defer all reviews until project closeout. Ask the stakeholder to attend sprint demos or forfeit acceptance rights. Maintain iterative demos but incorporate final acceptance as part of a predictive-style phase-gate. Delay development until acceptance strategy is resolved. 72 / 120 You’re managing a global hybrid project. Agile teams in different time zones struggle to align on priorities, while stakeholders expect consolidated weekly status in a predictive format. What should you implement? Standardize time zones and require all teams to adjust their work hours. Create a centralized reporting framework that aggregates Agile progress into predictive dashboards and enable asynchronous ceremonies. Transition the entire project to predictive for consistency. Cancel weekly reports and rely on sprint reviews. 73 / 120 Your team delivers a software product in sprints. A predictive client demands a full scope definition and cost breakdown before committing funding. However, product requirements are still evolving. What’s your best course of action? Delay the project until requirements stabilize. Ask the client to provide fixed requirements immediately. Estimate the entire scope using story points and present it as a predictive plan. Use progressive elaboration to provide high-level estimates and adjust scope as clarity improves. 74 / 120 A hybrid project you’re leading uses Scrum for software development and a predictive model for infrastructure. Your infrastructure lead has been missing Agile ceremonies and failing to provide timely updates, causing integration issues. How should you resolve this? Define expectations for cross-model communication and ensure the infrastructure team participates in relevant Agile events. Remove infrastructure deliverables from the integration plan. Isolate Agile and predictive teams and minimize cross-dependencies. Delegate all communication responsibilities to the Scrum Master. 75 / 120 A predictive project requires regulatory testing at multiple stages. The testing team proposes incorporating exploratory testing methods used in Agile to improve test coverage and defect detection. What is the best approach? Reject exploratory testing since it doesn’t follow a test script. Blend traditional and exploratory testing by adding time-boxed exploratory sessions to each formal test phase. Ask the team to use exploratory testing only post-deployment. Postpone testing until all formal documents are reviewed. 76 / 120 The product owner in an Agile workstream of your hybrid project frequently reprioritizes the backlog mid-sprint, disrupting the team’s progress and velocity. Team morale is declining, and burn-down charts are erratic. What should the project manager do? Increase the sprint length to accommodate more changes. Allow developers to bypass backlog items and work on technical tasks. Replace the product owner with a more experienced stakeholder. Coach the product owner on respecting sprint boundaries and reinforce backlog grooming during sprint planning. 77 / 120 A critical milestone is approaching in your hybrid project. Your Agile team is ready to demo key features, but senior leadership—used to predictive reviews—expects a detailed sign-off document with full traceability. What should you do? Convert the demo into a formal presentation without showing working software. Create a hybrid review structure that includes a sprint demo, accompanied by mapped deliverables and traceability documentation. Cancel the demo and focus on documentation. Delay the milestone to give the Agile team time to document their work. 78 / 120 During an iteration review in a hybrid project, a client stakeholder expresses disappointment that user stories did not fully reflect business processes. The Product Owner clarifies that the client had not participated in story grooming or sprint planning. How should this situation be addressed? Reassign the Product Owner for lack of communication. Reject the feedback since it was not provided during sprint planning. Emphasize the importance of stakeholder participation in backlog refinement and update the stakeholder engagement plan accordingly. Add the requested stories to the next sprint regardless of prioritization. 79 / 120 A predictive project nearing closure has completed all deliverables. However, an executive stakeholder claims that the project did not meet business expectations due to a lack of flexibility and engagement throughout execution. What should the project manager do to prevent this in future projects? Modify project scope to include post-delivery enhancements. Schedule additional scope reviews at the end of each project phase. Conduct stakeholder engagement reviews during planning and consider blending agile feedback loops into future delivery. Initiate a new project for the requested improvements. 80 / 120 A cross-functional team working on a hybrid project is experiencing delays in completing documentation required by the PMO. The agile team considers it overhead and is focusing solely on velocity and product increments. How should the project manager address this challenge? Enforce strict documentation standards and penalize the team for non-compliance. Remove Agile processes until documentation improves. Submit the reports yourself to reduce friction with the team. Clarify documentation requirements and tailor them to include only essential compliance artifacts while preserving team agility. 81 / 120 You’re managing a project with defined scope and a fixed delivery date. Your agile development team identifies a backlog item that would provide significant value to the customer but is not part of the original requirements. They propose replacing a lower-value feature. What should you do? Approve the change informally and update the documentation after delivery. Perform impact analysis and facilitate a scope change request with stakeholders to consider the value swap. Add the feature if time permits after completing all original requirements. Reject the request since the scope is fixed. 82 / 120 In a hybrid project, a key vendor delivers components late for two consecutive iterations, disrupting your Agile team’s development plan. The vendor contract was established under a fixed timeline with milestone penalties in the predictive framework. What is your best course of action? Terminate the vendor and use internal resources for future work. Ignore the vendor delays and proceed with placeholder components. Enforce contractual penalties, and adjust your Agile roadmap to reflect realistic timelines and vendor constraints. Escalate the issue to the product owner and continue development. 83 / 120 You are managing a predictive project and receive feedback that your team is disengaged, with low morale and limited ownership. Some team members express interest in using Agile practices to foster collaboration. The sponsor insists the project stick to original methodologies due to contractual constraints. What’s the most effective response? Replace the team with more motivated personnel. Convert the entire project to Agile to increase engagement. Introduce collaborative elements like daily stand-ups and retrospectives within the existing structure without impacting formal deliverables. Reiterate the importance of compliance and maintain the current model. 84 / 120 During the project planning phase of a predictive software implementation, a key stakeholder requests that Agile concepts such as backlog grooming and demos be incorporated into the traditional schedule. You are concerned about maintaining consistency with regulatory deliverables and approval gates. What should you do? Reject Agile practices to avoid disruption to the approved plan. Integrate Agile ceremonies in parallel with the existing plan and align deliverables with regulatory milestones. Break the project into two separate initiatives—Agile and predictive. Convert the entire project to a hybrid model and cancel existing baselines. 85 / 120 You're overseeing a hybrid project with Agile feature development and predictive regulatory compliance components. While reviewing status, you find that the compliance tasks are falling behind, yet Agile development is proceeding at full speed. This mismatch could delay integration testing and impact launch. What action should you take? Slow down Agile development until compliance activities catch up. Re-prioritize backlog items that are not dependent on compliance milestones and synchronize cross-stream dependencies. Escalate the delay and ask for additional compliance resources. Transition the compliance workstream to Agile for better speed. 86 / 120 Your team is developing an enterprise-level HR management platform. The core system is built using a predictive approach, while a mobile app component is developed iteratively using Agile. The mobile team wants to push early releases to beta testers, but the core team insists that no component can go live until full system integration. What is the most appropriate response as project manager? Block the Agile team's release until predictive integration is complete to avoid inconsistency. Transition the entire project to Agile to remove constraints. Require all teams to delay releases until formal UAT is complete. Propose a phased release strategy that allows non-dependent Agile components to be piloted while preserving integration for final release. 87 / 120 A distributed agile team is delivering functionality across four product areas. One of the business stakeholders begins contacting individual developers directly with feature changes during the sprint. This has led to confusion, rework, and inconsistent delivery across stories. What should the project manager do? Reinforce the role of the Product Owner as the single point of contact for backlog changes and provide coaching to the stakeholder. Allow the developers to make quick changes as needed and review them during the sprint retrospective. Escalate the stakeholder's behavior to the steering committee. Ask the Scrum Master to remove the stakeholder from sprint ceremonies. 88 / 120 Your project is in the execution phase of a predictive model with tightly defined scope, cost, and schedule baselines. An executive sponsor, impressed by a recent industry innovation, asks your team to explore integrating a new feature that was not in the original requirements. The team estimates that implementing the feature would impact both budget and schedule significantly. What should you do next? Reject the request immediately since the scope is already baselined and the project is mid-execution. Initiate formal change control procedures to evaluate the request's impact and ensure alignment with business objectives. Ask the team to work overtime to accommodate the change without altering the schedule or budget. Add the feature informally and include it in the lessons learned log. 89 / 120 A predictive project team is falling behind due to slow change approvals and excessive documentation overhead. The PMO is open to introducing Agile techniques to improve execution speed but is concerned about audit trail requirements. What should you propose? Eliminate documentation requirements during sprints and create reports retrospectively. Convert the entire project to Agile and inform the PMO afterward. Incorporate lightweight Agile ceremonies and digital change logs to satisfy both agility and compliance. Retain predictive processes and limit Agile adoption to internal team meetings only. 90 / 120 Your organization wants to adopt hybrid methods but has deeply entrenched predictive controls. A senior manager suggests running a pilot Agile project. However, the procurement process still demands fixed-price contracts with complete scope documentation before work begins. How can you support Agile delivery within these constraints? Request full exemption from procurement policies for the pilot. Deliver the entire project using waterfall to comply with procurement. Propose phased contracting with fixed scope for early phases and flexible terms for later phases. Outsource procurement separately and run Agile internally. 91 / 120 Your predictive project’s critical path includes deliverables from an Agile vendor. The vendor’s sprints do not align with your planned milestone delivery. This has led to late handovers and impacted subsequent work. What is your best course of action? Require the vendor to match your predictive milestones regardless of sprint planning. Create shadow tasks in your schedule to monitor the vendor without changing the milestone. Split the contract to isolate Agile deliverables from critical path items. Adjust your milestone schedule to better align with the vendor’s Agile delivery cadence and renegotiate interface points. 92 / 120 A hybrid project is struggling with stakeholder engagement. Agile stakeholders want more frequent demonstrations and fast iterations. Predictive stakeholders want detailed documentation and fixed reporting intervals. How should the project manager address this divide? Pick one engagement model and apply it across all stakeholders for consistency. Alternate between Agile and predictive reporting methods each month. Tailor stakeholder engagement strategies by stakeholder group and offer dual communication streams to meet both needs. Escalate the issue to the PMO and follow their direction exclusively. 93 / 120 During a critical phase of your predictive project, a stakeholder pushes for Agile-based visual boards for tracking work, citing lack of visibility into task status. Your team is following the work breakdown structure and Gantt charts closely, and doesn’t see value in changing tools. What is the most balanced response? Transition all work tracking to Agile boards immediately. Introduce Kanban or task boards as a visual supplement to your existing schedule and track progress in both. Refuse the stakeholder request to avoid redundancy. Direct the stakeholder to review existing reports. 94 / 120 You are managing a program with multiple projects—some run Agile and others predictive. While consolidating project reports, you notice inconsistent formats, mismatched KPIs, and difficulty in aggregating status updates for executive stakeholders. What should you do to improve alignment? Ask all teams to switch to predictive KPIs to enable simpler aggregation. Provide separate dashboards and let stakeholders interpret data differently per project. Create a standardized reporting template that accommodates both Agile and predictive data points and provide training across teams. Report only milestone-based updates to reduce inconsistency. 95 / 120 A highly visible predictive government project requires strict reporting and documentation. The project team wants to apply Agile estimation techniques like story points to improve planning accuracy. However, the PMO only accepts time-based estimates. What is the best way to bridge both expectations? Use Agile estimation internally but continue reporting traditional estimates to the PMO without translation. Ask the team to abandon story points and adopt only time estimates. Request an exemption from the PMO to use Agile metrics for this project. Translate story points to hours using historical velocity and report effort estimates in both formats. 96 / 120 An Agile team under your supervision is ahead of schedule delivering features. However, the client’s testing team is only available on a fixed schedule based on the predictive milestone plan. The early deliveries are sitting idle, and the team’s morale is dropping due to lack of feedback. How should you handle this situation? Slow down the sprint pace to align with the original testing schedule. Collaborate with the client to adjust the test schedule and establish a feedback loop within the Agile cadence. Switch the team to documentation and training until the testers are available. Add extra sprints for minor enhancements until feedback is received. 97 / 120 You are managing a hybrid project with monthly planning meetings and bi-weekly sprint reviews. One of the sprint reviews exposed a critical dependency between two agile teams that was not identified during the predictive planning phase. This dependency is now impacting the overall timeline. What is the best immediate course of action? Add buffer tasks in the schedule to absorb future delays. Instruct teams to work independently and resolve dependencies as they occur. Update the project schedule to reflect the dependency and include it in the next sprint planning discussion. Restructure team assignments and reassign ownership of related components. 98 / 120 A predictive project is experiencing delays due to internal decision bottlenecks and long approval cycles. Several team members suggest adopting Agile ceremonies like daily stand-ups and retrospectives to improve communication. Senior management is skeptical about mixing methods. What is the most effective way to proceed? Escalate the delays and request management intervention to enforce faster decisions. Pilot select Agile practices within the existing predictive framework to demonstrate value and reduce friction. Recommend a full transition to Agile lifecycle and terminate predictive planning. Continue with existing structure to avoid introducing confusion during execution. 99 / 120 Your project team is developing a product using Agile methods, but the contract with the client is fixed price with defined scope and deliverables. Midway through the project, the client asks for additional features based on recent market research. The team is open to adding value, but the fixed contract poses a constraint. How should the project manager respond? Ask the team to incorporate the changes incrementally without notifying the client about delays. Initiate formal change control procedures to assess the scope, timeline, and cost impacts, and seek contract adjustment. Accept the change as a competitive differentiator and realign priorities in the backlog. Reject the change due to the constraints of the fixed-price contract. 100 / 120 Your project team recently transitioned to a hybrid model. The development team uses Scrum, but your organization’s quality assurance department follows a traditional sequential testing process. After Sprint 3, defects from Sprint 1 are still unresolved because the QA team did not participate during the sprints. What is the best step to address this challenge? Delay sprint reviews until QA finishes testing all prior sprints. Split the QA team into two groups—one for Agile and one for Waterfall testing. Escalate the issue and request QA resources be replaced with Agile testers. Integrate QA activities into each sprint by involving QA representatives in sprint planning and definition of done. 101 / 120 You're leading a hybrid project where infrastructure is deployed through a predictive plan, while feature development uses Agile. Midway through the project, the infrastructure deployment is delayed by two weeks due to resource constraints. The Agile team continues delivering stories, but system testing cannot begin without the infrastructure. The client is growing impatient. What should you do to maintain transparency and minimize schedule impact? Continue story development and queue all completed features for future release without stakeholder updates. Move the entire team to infrastructure work until it’s caught up. Adjust the release roadmap and conduct regular cross-team syncs to align sprint deliveries with updated infrastructure milestones. De-prioritize stories dependent on infrastructure and replace them with low-priority backlog items. 102 / 120 During the planning phase of a predictive enterprise ERP deployment, stakeholders from multiple departments begin requesting continuous demos of partially completed modules. However, your current project plan shows no deliverables until the end of Phase 2, three months away. You understand the importance of engagement but need to protect scope and schedule. What is the most effective approach? Introduce Agile concepts by breaking down future deliverables into smaller, reviewable increments. Postpone the stakeholder demos until Phase 2 completion to preserve efficiency. Provide mock data and screenshots instead of working demonstrations. Refuse the request and focus on hitting Phase 2 milestone commitments. 103 / 120 A software delivery team working within a hybrid environment has missed its release deadline because integration testing across modules was not synchronized. The agile development teams completed their sprints on time, but the predictive release planning did not factor in delays from an external vendor API. The sponsor is concerned about systemic breakdowns in planning. What should the project manager do first? Shift future sprints to a three-week cadence to allow more buffer time. Conduct a lessons learned session focused on coordination between agile teams and predictive milestones, and update the risk register. Remove external dependencies from the critical path and reschedule deliverables accordingly. Request an extension from the sponsor and add the missed features to the next iteration. 104 / 120 While managing a predictive construction project with strict regulatory oversight, you initiate a stakeholder engagement workshop. One influential stakeholder demands weekly agile-style check-ins and requests flexible deadlines to accommodate changing priorities. You recognize the benefits of collaboration but are limited by a rigid contract and fixed milestones. How should you handle this situation? Request a formal change to the project lifecycle methodology to accommodate Agile principles. Explain that predictive projects cannot integrate Agile practices and maintain current stakeholder management plans. Escalate the stakeholder’s request to the sponsor and wait for written direction. Offer bi-weekly informal status reviews while maintaining adherence to the project schedule and scope baselines. 105 / 120 Your project is delivering a new digital banking platform. The front-end customer interface is being developed using Agile practices with two-week sprints, while the back-end system integrations follow a predictive lifecycle. During sprint planning, the Product Owner identifies new customer behavior patterns that suggest a shift in interface design priorities. However, changing these priorities would delay interface testing, which the back-end team needs to complete their integration milestones. What should the project manager do to balance competing lifecycle constraints? Facilitate a joint planning session to align dependencies and allow sprint reprioritization with coordinated milestone adjustment. Freeze interface backlog changes until the next release cycle to protect the integration schedule. Ask the Product Owner to deprioritize the user-driven changes and continue with the original backlog. Instruct the front-end team to document the changes for consideration after user acceptance testing. 106 / 120 A client on your project has introduced a new reporting template and asks you to start using it immediately, even though it doesn’t align with the current Communication Management Plan. What should you do? Begin using the template to maintain client satisfaction. Initiate a change request to evaluate the impact on existing processes. Escalate to the sponsor to reject the request. Add the request to the lessons learned database. 107 / 120 Your predictive project has entered the execution phase. A sponsor requests you to present the expected time of completion based on current performance. Your team provides the following: PV = $100,000 EV = $90,000 AC = $110,000 What metric should you use to forecast project completion? Cost Variance (CV) Estimate to Complete (ETC) To-Complete Performance Index (TCPI) Estimate at Completion (EAC) 108 / 120 You’re in the Monitor Risks process and find that a high-impact risk flagged earlier has now increased in probability. No response plan was defined originally because it was low probability. What is the correct step to take now? Update the issue log and continue monitoring. Remove the risk from the register since it was missed in planning. Reassess the risk using Perform Quantitative Risk Analysis and define a response plan. Escalate to the sponsor to accept the risk and close the register entry. 109 / 120 You’re managing a predictive healthcare IT project. The Change Control Board has become a bottleneck, taking weeks to approve small changes. Several changes have caused schedule delays. How should you optimize the change control process? Bypass the CCB for minor changes and inform them later. Increase the number of CCB members to improve quorum. Implement a change threshold policy where low-impact changes can be approved by the project manager. Defer all changes to a post-deployment phase. 110 / 120 A government-funded project requires strict adherence to Earned Value Management. Your weekly reports show a CPI of 0.7 and SPI of 0.95. The sponsor is requesting continued delivery with no additional funding. Which strategy should you prioritize? Add scope buffers to increase project value. Focus on increasing efficiency to improve CPI while keeping schedule performance stable. Delay schedule to preserve budget and meet CPI goals. Escalate to the funding authority and request variance approval. 111 / 120 You’re closing a high-budget infrastructure project. While preparing the final performance report, the finance team reports that several change orders approved during execution were not updated in the cost baseline. What should you do before final project closure? Forward the discrepancy to the finance department and proceed with closure. Document the variance as a lesson learned and submit the final report. Reconcile the cost baseline with all approved change orders and update project documentation accordingly. Cancel project closure and re-initiate planning. 112 / 120 In a predictive project, your team continuously submits incomplete status reports with missing KPIs. This leads to miscommunication with external auditors and misalignment with the communications management plan. What corrective action should you implement? Increase the frequency of status reporting. Allow each department to design their own reporting templates. Create a separate reporting team and take responsibility away from current members. Conduct a formal training session on reporting standards and revise the RACI matrix for report approvals. 113 / 120 You are in the planning phase of a mission-critical software rollout project. A cross-functional review team identifies that security testing was omitted from the WBS, even though it was included in the scope statement. What is the best course of action? Treat security testing as part of quality assurance and do not alter the WBS. Add it to the lessons learned and track it manually. Delay planning until all WBS omissions are found and corrected. Update the WBS to include the omitted security testing and submit a revised scope baseline. 114 / 120 During the planning phase of a large construction project, one of the stakeholders insists on using a local materials supplier despite concerns over quality and delivery timelines. The procurement team is aligned with using a vetted, international supplier. What should you do? Accept the stakeholder's preference to avoid conflict. Perform a make-or-buy analysis and include the stakeholder’s supplier in a formal evaluation. Proceed with the international supplier and notify the stakeholder after contract award. Allow both suppliers to deliver materials in parallel. 115 / 120 During procurement planning, one of your subcontractors informs you that the initial quote will increase by 15% due to new import taxes. This cost was not accounted for in your original budget estimate. What is the best action to maintain project constraints? Proceed with the new quote and absorb the cost in management reserves. Negotiate a lower rate by reducing scope of the subcontractor’s responsibilities. Revise the cost baseline after submitting a change request and evaluating impacts. Reject the quote and seek a replacement vendor. 116 / 120 During the closing phase, your team discovers a defect in a deliverable that has already been accepted by the client. The contract has a clause that permits defect repair at no cost for 90 days post-handover. What should you do? Raise a change request to formally reopen the project. Log the defect in the lessons learned register and initiate repair immediately as part of contract obligations. Bill the client for the additional work since the project was already closed. Advise the client to report the defect through a support channel. 117 / 120 You’re managing a predictive multi-year engineering project. Halfway through, a regulatory body introduces new compliance requirements. The change affects project scope, duration, and cost. What should be done first? Pause project activities until the team can address compliance requirements. Add a risk response plan for regulatory changes. Initiate a change request to update the scope, cost, and schedule baselines. Start training your team immediately on the new compliance rules. 118 / 120 While performing the Monitor and Control Project Work process, you find that SPI is below 0.8 and CPI is 1.05. Senior management is pleased with cost control, but stakeholders are dissatisfied with schedule delays. What is the best course of action? Request additional budget to increase the pace of work. Revisit the schedule baseline and evaluate fast-tracking or crashing techniques to regain lost time. Delay scope activities to reduce the schedule pressure. Initiate a new risk response plan for unspent budget. 119 / 120 As part of quality management on a predictive project, a contractor is required to provide reports on concrete strength every 48 hours. Three consecutive reports were missed without explanation. What should you do next as the project manager? Issue a formal non-compliance notice and escalate to procurement. Call an emergency meeting with the contractor and record the event in the risk register. Submit a change request to revise quality control frequency. Update the stakeholder register with the missed reports. 120 / 120 While performing schedule development, you discover that several activities lack dependency relationships, making the critical path calculation unreliable. Some team leads argue that their tasks are too independent to be sequenced. What should you do? Leave the dependencies undefined and estimate duration using Monte Carlo analysis. Remove the tasks with no dependencies from the project schedule. Move the tasks to a non-scheduled phase of the project and monitor progress manually. Revisit the activity list and network diagram, and enforce logical relationships for all work packages. Your score isThe average score is 0% 0% Restart quiz