Free PMP Practice Exam (2026)
A full-length PMP practice exam for the new exam PMI introduced on July 9, 2026: 180 agile, hybrid and predictive questions in 4 hours, every answer explained, and your score by domain.
1. Choose a set
2. Choose a mode
same as the real exam
A medical device company is building a new infusion pump. The hardware must pass strict regulatory verification, while the companion mobile app has unclear user needs that will change as nurses try it. The sponsor asks the project manager to recommend a development approach. What is the BEST recommendation?
The two parts have very different levels of uncertainty and regulatory control, so a tailored hybrid approach fits best. Forcing full predictive on the app ignores how unclear its needs are, and full agile on the hardware ignores the fixed regulatory work.
You are leading a hybrid project to launch a customer self-service portal. During the first week, you notice that the product owner, the developers, and the support lead each describe the portal's purpose differently. Work has not started yet. What should the project manager do FIRST?
Co-creating the vision with the people doing the work builds shared ownership and understanding. A written statement from the product owner sounds efficient, but people rarely commit to a vision they had no part in shaping.
A hybrid program delivers a software platform with agile teams and a hardware build managed in phases. During a sprint review, the product owner and a functional manager both claim authority to approve a scope trade-off that affects the release date. The team is waiting for direction. What should the project manager do FIRST?
Decision rights should come from the agreed governance framework, so the first step is to check what it says before acting. Giving it to the product owner sounds right, but this trade-off affects the release date, which may sit outside that role's authority.
A hybrid project's agile team will hold sprint planning tomorrow. While reviewing resource calendars, the project manager sees that two of the five developers have approved leave covering most of the next two sprints. The product owner is unaware and expects the usual velocity. What should the project manager do FIRST?
Resource calendars exist so capacity can be planned on facts. The team and product owner should forecast the sprint using the real availability before any other action. Replacing people, cancelling leave or forcing overtime come later, if at all.
At the kickoff of a hybrid project, the product owner says success means releasing within four months, while the operations director says success means zero critical defects at launch. Both are influential and neither seems willing to compromise. What should the project manager do FIRST?
Shared, measurable success criteria agreed early prevent constant conflict later, and the project manager should try to resolve it with the people involved first. Escalating to the sponsor skips the team-level attempt and can damage working relationships.
During risk planning for a predictive construction project, the team quantifies two risks. There is a 30% chance that soil testing reveals contamination, which would add $40,000 in cost. There is also a 20% chance that a $25,000 supplier rebate becomes available if materials are ordered in bulk. Based on these two risks only, how much contingency reserve should the project manager recommend?
EMV combines threats and opportunities. The threat is 0.30 x $40,000 = $12,000 of expected cost and the opportunity is 0.20 x $25,000 = $5,000 of expected savings. The net exposure is $12,000 - $5,000 = $7,000.
An agile team building a customer portal has had two increments rejected at sprint review because pages load too slowly under real traffic. The developers say performance testing is 'something ops does later.' The product owner is frustrated. What should the project manager do FIRST?
The increments fail because the team's idea of 'done' leaves out performance. Adding performance criteria to the definition of done builds quality into every increment instead of inspecting it in later. Hardening sprints and handoffs to ops push the problem downstream.
A PMO requires every project to complete a 40-page planning template. A project manager is leading a four-month internal project with a small, co-located team and stable requirements. Much of the template does not apply. What should the project manager do FIRST?
Tailoring starts by understanding the project context and agreeing the right level of planning with governance. Skipping sections without agreement breaks the PMO process, while filling every section wastes effort on work that adds no value.
Midway through a release, an agile team is meeting its sprint goals, but the business reports little improvement in the outcome the project was funded for. When asked, team members say their job is to finish the stories in the backlog. What should the project manager do FIRST?
The team has lost sight of why the work matters, so reconnecting the backlog to the vision and intended outcomes is the first step. Escalating to the sponsor is premature because the gap can likely be fixed with the team and product owner.
In a predictive infrastructure project, a phase gate review is scheduled for next week. Two deliverables required by the gate criteria will not be complete, and the team lead suggests quietly starting the next phase to protect the schedule. What is the BEST approach?
Phase gates exist so the governance body can make informed go or no-go decisions, including a conditional approval. Postponing the gate looks careful, but it removes that decision from the people who own it and hides schedule pressure.
On a predictive construction project, the lead structural engineer is overallocated in weeks 6 through 8. The contract end date is firm, and the overallocated activities have between 5 and 10 days of total float. The project manager wants to fix the overallocation without moving the end date. Which technique is BEST?
Resource smoothing adjusts activities only within their free and total float, so the critical path and end date do not change. Leveling can push the end date, which the firm contract does not allow. Crashing and fast tracking compress the schedule and do not address the overallocation itself.
Halfway through an agile project, a newly appointed head of compliance joins the steering group. She asks to formally sign off every requirement document before developers start any work, as she did on past projects. What is the BEST approach?
Bringing her into refinement meets her real need, compliance assurance, inside the agile way of working. Producing heavy documents adds delay and wastes effort, while telling her to wait for the finished product ignores a valid concern.
A project manager on a predictive infrastructure project has ranked all identified risks using a probability and impact matrix. The sponsor now asks how likely it is that the project will finish by the contractual date, and how much schedule reserve is needed for 85% confidence. What should the project manager do NEXT?
A probability and impact matrix is qualitative and cannot give the probability of meeting a date. Quantitative analysis such as Monte Carlo simulation models the combined effect of risks and shows the reserve needed for a chosen confidence level.
On a predictive manufacturing project, the quality engineer shows a control chart for a machined part. All measurements are inside the control limits, but the last seven consecutive points sit above the mean. The production lead says nothing is wrong because no point breached a limit. What should the project manager do?
Under the rule of seven, seven consecutive points on one side of the mean signal a non-random pattern, even when every point is inside the limits. The process should be treated as out of control and the cause investigated. Changing limits or specs hides the problem.
A product owner asks when the next release can ship. The remaining release backlog is 198 story points. Over the last four two-week sprints the team completed 30, 36, 33, and 33 points. Which forecast should the project manager share?
Dividing 198 by 36 gives 5.5 sprints and dividing by 30 gives 6.6, so a range of 6 to 7 sprints is honest. A single number from the average hides the real spread in velocity and sounds more certain than the data allows.
A predictive infrastructure project is in execution when the original sponsor leaves the company. The new sponsor, in her first meeting with you, mentions priorities that differ from those you have been working toward. What should the project manager do FIRST?
A new sponsor needs to understand and own the project's purpose, so the charter and business case are the right starting point for that conversation. Raising a change request first jumps ahead before anyone knows whether the objectives truly need to change.
A newly formed PMO in an organization adopting agile asks all Scrum teams to submit weekly Gantt charts and percent-complete reports. Team members complain this adds work and does not reflect how they plan. What should the project manager do?
The PMO has a valid need for oversight, and burnup charts, release forecasts and demos can meet it without forcing a predictive format. Simply complying keeps the peace but adds waste and gives the PMO data that does not reflect real progress.
After the project manager applies a resource optimization technique to a predictive schedule, the forecast finish date moves out by three weeks. The sponsor is surprised, because no scope was added and no estimates changed. Which explanation is MOST likely?
Resource leveling resolves overallocation by delaying work until the resource is free, and it can move activities past their float. That often changes the critical path and extends the finish date. Smoothing, by definition, stays within float and does not move the end date.
During planning on a predictive infrastructure project, the project manager's power/interest analysis shows a regional vice president has high power but little interest in project details. What should the project manager plan for this stakeholder?
High-power, low-interest stakeholders should be kept satisfied with focused information that matters to them. Weekly detailed meetings would overload someone who does not want detail and may turn interest into irritation.
In a hybrid project, the risk register lists a vendor delay risk with a clear trigger and a response plan, but the owner column says 'Team'. The trigger occurred two weeks ago, yet nobody acted because each person assumed someone else was watching it. The delay has now become an issue. To prevent this with other risks, what is the BEST action?
Shared ownership often means no ownership. Each risk needs one named owner who monitors its triggers and makes sure the agreed response happens. The project manager oversees the process but should not own every risk.
A hybrid project delivering medical scheduling software is getting a high number of customer-reported defects, and support costs are climbing. The sponsor proposes cutting the training and design review budget to pay for more support staff. What is the BEST response from the project manager?
Training and design reviews are prevention costs, which are usually the cheapest way to reduce failures. Cutting them tends to raise external failure costs even more. The project manager should use cost of quality data to show this trade-off.
During planning for a warehouse construction project, the procurement lead and the resource lead each submit their subsidiary plans. The procurement plan has steel delivered in week 10, but the resource plan has the steel crew released in week 8. The plan has not yet been baselined. What should the project manager do NEXT?
Integrating subsidiary plans so they are consistent is the project manager's job before the plan is baselined. Escalating to the sponsor is premature because this is a normal planning conflict the project manager should own and facilitate.
Your hybrid project is bringing in two external vendors, each supplying a team that will work alongside your internal developers. Both vendors have their own delivery methods and internal success metrics. What is the BEST approach to build a common direction across all three teams?
A joint chartering session gives everyone the same understanding of the goal and how they will work together. Forcing one process on everyone ignores tailoring and the value the vendors bring, and it will not build shared commitment.
On a hybrid product launch, two steering committee members disagree on which of two epics should be delivered first. Each asks the project manager to support their position, and the next release planning session is in three days. What should the project manager do NEXT?
When decision makers conflict, the PM provides objective impact data and follows the defined escalation path so the right authority decides. Picking an epic alone oversteps the PM's decision rights, even if the value estimate looks sound.
On a hybrid software project, the QA lead and the development lead each believe they are the one who approves the test strategy. Testers are receiving conflicting direction, and two sprints of test automation work have been redone. What is the BEST action for the project manager?
A RACI chart should have exactly one Accountable person per deliverable. Working it out with both leads removes the confusion at its source and keeps the decision within the team. Joint approval or escalation leaves the root cause unresolved.
On a hybrid program, two business units each believe their features will be in the first release. The product owner has been prioritizing the backlog alone, and neither unit understands how decisions are made. What should the project manager do?
Transparent criteria and a shared release goal build trust and align expectations without taking authority away from the product owner. Splitting the release avoids the conversation and may reduce the value delivered.
To address the risk that the main contractor lacks capacity, a project manager on a predictive project decides to split the work between two contractors. A team member points out that having two contractors on the same site could cause coordination problems and disputes over interfaces. What should the project manager do?
A new risk created by a risk response is a secondary risk. It should be identified, analyzed, and given its own response in the risk register. Residual risk is what remains of the original risk after the response, which is a different thing.
A hybrid infrastructure team has logged 180 defects across 14 categories over the last quarter. Capacity is limited, and stakeholders disagree about which problems to tackle first. Which approach should the project manager use to decide where to focus?
A Pareto chart ranks defect categories by frequency so the team can attack the vital few that cause most of the problems. That gives the best return on limited capacity. A vote is subjective, and the other charts answer different questions.
A newly formed agile team is starting a product whose market direction is still uncertain. The sponsor asks the project manager for a detailed 12-month plan showing every feature and its delivery date. What is the BEST response?
A roadmap with progressive elaboration gives the sponsor a long-term view while staying honest about uncertainty. A detailed 12-month feature plan would create false precision, and refusing to plan at all ignores a fair need for direction.
An agile team is starting work on a minimum viable product, but members keep debating which features belong in the first release. The product owner has a vision statement, but the team finds it too high-level to guide these choices. What should the project manager do NEXT?
Story mapping turns a high-level vision into a visible, shared picture of user needs and helps the team agree on a sensible first slice. Having the product owner decide alone may be fast, but it leaves the team without the shared understanding they asked for.
A project manager takes over a predictive construction project midway. A supplier has just reported a three-week delay, and the PM finds that the governance plan defines no tolerance limits for schedule or cost variance. What should the project manager do FIRST?
Without tolerance limits nobody knows which variances the PM can handle and which must go up, so defining them with the sponsor fixes the root gap. Escalating everything sounds safe, but it floods leaders with noise and still leaves the governance gap open.
A hybrid project builds a medical device. Its agile firmware team shares six hardware test rigs with another program. Twice this month the team arrived for planned testing and found every rig in use, which blocked sprint goals. What should the project manager do NEXT?
Physical resources must be planned and coordinated like people. A shared booking schedule fixes the conflict quickly, and adding rig availability to sprint planning stops it from coming back. Buying equipment or demanding exclusive use should only follow analysis and agreement.
On a predictive ERP rollout, the stakeholder engagement assessment matrix shows the warehouse supervisors as resistant, while the desired level is supportive. Go-live is four months away. What should the project manager do FIRST?
You cannot plan an effective engagement strategy until you know why people resist. A sponsor directive may force compliance on paper but tends to deepen resistance and hide real concerns.
An agile team is planning the next iteration and has room for one more item of similar size. Feature F is expected to deliver $40,000 in business value. A technical story would remove a performance risk that has a 50% chance of causing $100,000 in rework later. The product owner prefers Feature F because customers can see it. What should the project manager advise?
A risk-adjusted backlog ranks risk responses alongside features by value. The risk's expected value is 0.50 x $100,000 = $50,000, which is more than the $40,000 from Feature F. Using the full $100,000 impact ignores probability.
An agile team's escaped defects have risen for three sprints in a row. The team lead suggests adding a full manual regression cycle at the end of each sprint. The retrospective is tomorrow. What should the project manager do?
The retrospective is where the team should examine why defects escape and agree on an improvement experiment for the next sprint. Jumping to a fix before finding the root cause may add cost without solving the problem. Self-organizing teams own their process improvements.
A software team runs two-week sprints, while a hardware vendor delivers boards at fixed quarterly milestones. In the last two quarters, integration problems were discovered only after each board arrived, causing weeks of rework. What should the project manager do?
Aligning cadences around shared integration points lets each side keep a suitable approach while reducing late surprises. Adding a test phase after arrival still finds problems late, and forcing the vendor into sprints is often not realistic for hardware.
On a predictive construction project, site crews say they do not see how their daily tasks connect to the larger goal of opening a community hospital. Morale and attention to detail have started to slip. What is the BEST action for the project manager?
People commit more when they understand the purpose behind their work, so connecting daily tasks to the hospital's benefit addresses the root cause. More inspections treat the symptom and do nothing to rebuild motivation.
An organization running a mix of agile and predictive projects wants a PMO that offers templates, coaching and lessons learned, but leaders do not want it to enforce compliance or manage projects directly. Project managers will keep full control of their methods. Which PMO structure BEST fits this need?
A supportive PMO acts as a consultant and resource hub with a low degree of control, which matches the stated need. A controlling PMO also supplies templates, but it requires compliance, which leaders explicitly do not want.
An agile team needs an experienced application security specialist for the next three sprints to complete authentication features. The functional manager offers a junior analyst who has never done security testing, because the senior specialist is busy on another project. What should the project manager do FIRST?
Team acquisition often means negotiating with functional managers, and a clear picture of the impact makes that negotiation work. Assessing the gap first gives the facts needed to get the right person or agree a sensible alternative. Hiring or cutting scope before understanding the gap is premature.
A sponsor new to agile asks the team to produce a detailed Gantt chart showing every task through the end of the year. The team works in two-week sprints with a product roadmap and release burnup. What is the BEST response from the project manager?
The project manager should understand the information need behind the request and tailor existing artifacts to meet it. Building a year-long Gantt chart creates false precision and work that agile planning deliberately avoids.
An agile team must decide whether a new message queue technology can handle the expected peak load. Estimates for the related user stories range from 3 to 21 points because nobody on the team has used it before. The product owner wants to commit to a release date this week. What should the project manager suggest FIRST?
A spike is a time-boxed experiment that reduces uncertainty before the team commits. It gives real data on whether the technology works and supports a more reliable estimate. Averaging or padding estimates hides the risk instead of reducing it.
A regulator asks a predictive construction project for evidence that its testing procedures are being followed and are effective. The project has hundreds of passed inspection records. The site manager suggests sending the inspection logs. What should the project manager do?
The regulator wants confidence in the process, which is quality assurance, not more product checks, which is quality control. A quality audit examines whether processes are followed and effective. Inspection logs only show that individual outputs passed.
While finalizing the project management plan for an ERP rollout, the project manager notices that the quality management plan calls for three rounds of user acceptance testing. None of this testing appears in the schedule or the cost estimates. The baselines have not yet been approved. What should the project manager do NEXT?
The plan is not yet baselined, so the project manager simply integrates the components by adding the testing work to schedule and cost. A change request is only needed after baselines are approved, so it adds needless overhead here.
Two departments are merging their reporting processes through a hybrid project. Early discussions show that one department measures success by cost savings while the other measures it by reporting speed, and each assumes its own metric is the project's goal. What should the project manager do?
Agreeing on shared success measures, anchored in the business case, creates one direction both groups can support. Escalating may get a decision, but it skips the chance to build alignment at the working level first.
An agile team is building a patient portal for a healthcare provider. During a sprint review, a tester notes that a new feature writes patient identifiers to unencrypted application logs. The feature is scheduled for release in two days. What should the project manager do FIRST?
Exposing patient data is a regulatory breach, not a normal defect, so the right owners must know now and the release should not ship with it. Releasing and fixing later sounds agile, but it knowingly puts protected data at risk.
For two sprints, a functional manager has been pulling a key agile team member away for about half of each day to support production issues. No one told the project manager, and team velocity has dropped by 30 percent. What should the project manager do FIRST?
In a matrix setting, the project manager should first work directly with the functional manager. Showing the impact and agreeing a realistic capacity commitment keeps resource calendars and forecasts accurate. Escalation is the next step only if this does not work.
On a hybrid project, a vendor is building a key component. During a review, the client states acceptance criteria that differ noticeably from what the vendor says it agreed to deliver. Both sides are frustrated. What should the project manager do FIRST?
Checking the agreement and requirements gives an objective basis for aligning both parties. Telling the vendor to comply without checking may trigger claims and cost the project money it did not plan for.
On a hybrid project, the team learns that a new automated testing tool could cut three weeks from the schedule if an expert configures it. The organization has one certified specialist, who is currently assigned to a low-priority internal task. The project manager wants to make sure this benefit is fully realized. Which response is BEST?
When the goal is to make sure an opportunity definitely happens, the response is to exploit it. Securing the only qualified expert removes the uncertainty. Training others would only enhance the probability, and accepting does nothing to capture the benefit.
A predictive project has these activities: A (3 days) starts the project; B (5 days) and C (4 days) both follow A; D (6 days) follows B; E (2 days) follows C; F (3 days) follows both D and E. What is the total float of activity C?
Path A-B-D-F is 3+5+6+3 = 17 days and is critical. Path A-C-E-F is 3+4+2+3 = 12 days. The difference of 17 - 12 = 5 days is the float available on C and E.
A team ran a suitability assessment for a new customer portal. The results show high requirements uncertainty, but the team has little agile experience and the business can offer a customer representative for only a few hours a month. What is the BEST approach?
The assessment points toward agility, but the gaps in experience and customer access need to be addressed, which a tailored hybrid plan can do. Pure agile ignores the real weaknesses the assessment revealed, while predictive ignores the high uncertainty.
Three new members join an agile team in the middle of a release. The existing team has a clear product vision, roadmap, and team charter, but the new members are eager to start coding right away. What is the BEST way to bring the new members into the team's shared vision?
Reviewing the vision together and pairing with existing members helps newcomers understand both the goal and how the team works. Sending documents alone gives information but does not build real understanding or connection with the team.
Midway through a predictive project to build a manufacturing plant, the government announces a new emissions regulation that will apply before the plant opens. The site supervisor wants to change the design immediately. What should the project manager do FIRST?
Compliance is mandatory, but the change still needs impact analysis and a decision through integrated change control. Changing the design at once feels responsible, yet it skips the analysis of cost, schedule and risk that the change control board needs.
On a predictive building project, a supplier has been delivering steel weeks before the erection activities start. The site has little storage, and some steel has been damaged by weather and handling. What is the BEST way to prevent this from happening again?
Physical resource management aims to have materials arrive when they are needed. Linking deliveries to the schedule removes the storage and damage problem at its root. Extra storage or extra stock only treats the symptom and adds cost.
At the start of an agile product effort, stakeholders describe the product in very different ways: one sees a mobile app, another a partner portal, and a third an internal reporting tool. What should the project manager do to BEST align them?
A chartering or vision workshop creates shared understanding of purpose and outcomes before work begins. Merging everyone's requirements into one document hides the conflict instead of resolving it.
A project manager leads one of six agile teams in a large program. During planning, the team identifies a risk that a planned change to the company's single sign-on platform could break login for every product in the portfolio, not only theirs. The team has no authority over the platform. What should the project manager do?
When a risk is outside the project's scope or the project manager's authority, the right response is to escalate it to the level that can own it. Program or portfolio leaders can coordinate across all affected teams. Accepting it or working around it alone leaves the wider threat unmanaged.
A predictive data center project is three weeks behind on its critical path. The sponsor has approved extra funds, but the quality lead warns that overlapping design and build would create serious rework risk. What should the project manager do?
Crashing adds resources to critical path activities and suits a situation with available budget and low tolerance for rework. Choosing the cheapest cost per day saved keeps the added cost low. Fast tracking would raise the rework risk the quality lead warned about.
During a sprint, a developer adds an export-to-PDF feature that was not in any backlog item, believing users will love it. The product owner did not ask for it. The project manager learns about it at the daily standup. What should the project manager do?
Building unrequested work is gold plating; the product owner decides what gets built based on value. Keeping the feature seems harmless, but it uses team capacity on work nobody prioritized and may add testing and support costs.
During a daily standup, two developers start a heated debate about which database design to use. The standup is running well past its timebox and the rest of the team looks frustrated. What should the project manager do FIRST?
Moving the discussion out of the standup protects the timebox while still giving the disagreement a proper place to be resolved by the team. Deciding on the spot ends the meeting but takes ownership away from the people who will build and support the design.
A financial services company uses Scrum teams, and an external regulatory audit is due in six months. The team currently gathers compliance evidence only in a final hardening sprint before release. What is the BEST approach going forward?
Building compliance into the definition of done creates evidence continuously and avoids a risky last-minute scramble. Extending the hardening sprint keeps the same pattern of late discovery, just with more time spent on it.
A buyer needs a pump station built. The engineering firm has finished detailed drawings and specifications, material prices are stable, and the buyer's main goal is to know the final cost before work starts. Which contract type is BEST for the buyer?
When scope is fully defined and prices are stable, a firm fixed price contract gives the buyer cost certainty and puts cost risk on the seller. Cost-reimbursable and T&M contracts leave the buyer exposed to overruns.
In an agile team, a senior marketing manager keeps going directly to developers mid-sprint to request small changes. The developers feel pressured, and the sprint goal is now at risk. What should the project manager do?
A servant leader protects the team while guiding the stakeholder to the right channel, the product owner and backlog. Going to the sponsor first escalates before trying a direct, respectful conversation.
Over the last four retrospectives, an agile team has listed the same problems: unclear acceptance criteria and late code reviews. Each retrospective ends with a long list of ideas, but nothing changes in the following sprints. What should the project manager do to make the retrospectives more effective?
Retrospectives only work when a small number of improvements are actually acted on. Picking one or two actions, assigning owners, and treating them as sprint work makes change visible. Logging or escalating does not fix the problem for this team now.
An agile team has 240 story points left in the release backlog. Its last three sprints delivered 28, 32, and 30 points, and sprints are two weeks long. The team composition will stay the same. About how many weeks should the project manager forecast to finish the backlog?
Average velocity is (28 + 32 + 30) / 3 = 30 points per sprint. 240 / 30 = 8 sprints, and 8 sprints x 2 weeks = 16 weeks. This should be shared as a forecast that may shift if velocity changes.
On a predictive data center project, the WBS has one work package called Testing, estimated at 600 hours over four months. The project manager finds it hard to measure progress or assign clear ownership for it. What is the BEST action?
A work package should be small enough to estimate, assign, and monitor reliably, so further decomposition is the fix. Reporting percent complete on a huge package hides real progress and makes problems visible only when it is too late.
On a predictive project, a functional manager tells you he is moving a key engineer to another project next week. You were not consulted, and the engineer's work is on the critical path. What should the project manager do FIRST?
Knowing what was agreed in the resource plan and understanding the manager's reasons lets you look for a solution that works for both projects. Going straight to the sponsor skips a direct conversation that may solve the problem and damages the working relationship.
An internal audit of a hybrid project finds that change records for several approved features are incomplete and lack approval dates. The team lead says the features were clearly approved in meetings and wants to dispute the finding. What should the project manager do NEXT?
The records do not meet the standard, so the right response is to correct the gap and fix the process that caused it. Disputing the finding sounds reasonable, but the audit is about traceable evidence, and meeting memories are not that.
A cost plus incentive fee contract has a target cost of $200,000, a target fee of $20,000 and a buyer/seller share ratio of 70/30. The seller completes the work for an actual cost of $180,000. What is the total amount the buyer pays?
The underrun is $200,000 - $180,000 = $20,000, and the seller keeps 30 percent, or $6,000. Fee = $20,000 + $6,000 = $26,000. Total paid = $180,000 + $26,000 = $206,000.
At a milestone review on a predictive project, the customer says a deliverable is unacceptable, even though it meets every documented specification. The customer seems genuinely surprised by what was built. What should the project manager do NEXT?
Understanding the gap comes first; if new needs appear, they go through change control. Starting rework immediately bypasses change control and may fix the wrong thing.
A predictive project has four phases over two years. The organization's policy is to capture lessons learned at project closure. At the end of phase one, the project manager notices that procurement approvals took twice as long as planned. What is the BEST approach?
Lessons learned should be captured throughout the project so they can improve the remaining work. Reviewing the delay now lets the team fix the approval process before the next phase. Waiting until closure helps only future projects.
On a predictive building project, wall framing cannot start until poured concrete has cured for three days after the pour is finished. The scheduler wants to model this correctly. Which relationship should be used?
Framing can only start after the pour finishes, which is a finish-to-start relationship. The required waiting time is a lag, which delays the successor. A lead would let framing start early, which is the opposite of what is needed.
At a sprint review, the product owner rejects a story even though it meets the team's definition of done. The product owner says the story does not apply a discount rule that matters to the business. The team is frustrated and says the rule was never written down. What should the project manager do?
The definition of done covers quality standards for all work, while acceptance criteria define what one story must do. Adding a business rule to the definition of done mixes the two and would clutter a checklist meant for every item.
A tester and a developer on your hybrid team have been arguing about whether a defect is really a bug or a missing requirement. Each has emailed you separately asking you to rule in their favor. What is the BEST response?
Bringing both people together, with the product owner who owns requirements, addresses the real issue and builds their ability to solve problems together. Deciding for them may be faster, but it creates a winner and a loser and teaches them to send every disagreement to you.
A project manager on a predictive government contract has identified dozens of compliance requirements from laws, the contract, industry standards and internal policies. The sponsor asks how the team will decide where to focus its limited assurance effort. What is the BEST approach?
Grouping requirements by source and by the consequence of non-compliance, such as fines, shutdown or reputation damage, lets the team focus where risk is greatest. Focusing only on laws sounds efficient but ignores contractual penalties that can be just as severe.
A buyer wants an outside agile team to start building a customer portal within two weeks. The features will change a lot as users give feedback, and the buyer cannot define the full scope yet. The CFO is worried about losing control of costs. Which approach BEST balances flexibility and cost control?
T&M fits evolving scope and fast starts, but the buyer carries cost risk. A not-to-exceed cap plus sprint-level reviews of delivered value give the CFO control while keeping flexibility. A fixed price on unknown scope leads to constant change requests and disputes.
On a hybrid project, the release burnup shows that a feature promised to a key stakeholder will probably not make the next release. The release is six weeks away. What is the BEST action?
Early, transparent communication with data lets the stakeholder take part in trade-off decisions. Overtime is not a sustainable pace and hides the real capacity problem.
A hybrid project team builds and tests hardware units every week. A technician suggests a small change to the order of test steps that she believes could reduce rework. The change would cost little and could easily be reversed. What should the project manager do?
This is the spirit of kaizen: small, frequent improvements tested quickly. A short plan-do-check-act trial gives evidence before wider adoption. A low-risk process tweak does not need a formal board review.
During sprint planning, the product owner pushes the team to commit to 45 points because a trade show is coming up. The team's velocity has been steady at about 32 points. The developers look uneasy but say nothing. What should the project manager do?
Sprint plans should rest on the team's real capacity and past velocity, not pressure. The project manager, as a servant leader, protects the team and helps the product owner pick the highest-value items for the trade show. Overcommitting usually leads to poor quality and burnout.
On a predictive project, the customer's operations manager phones a developer and asks for an extra monthly report, calling it a tiny change. The developer tells the project manager before starting any work. What should the project manager do FIRST?
Every change request, even a small one, should be assessed for impact and handled through the agreed change process. Rejecting it outright skips the evaluation, and the request may in fact be worth approving once its impact is understood.
Your agile team is split between two continents. Members in one location complain that recurring team meetings are always set during their late evening, while the other location never has to adjust. What should the project manager do?
Letting the team revise its own working agreement shares the burden fairly and keeps everyone engaged. Simply moving all meetings shifts the problem onto the other location and creates a new grievance.
A marketing director on an agile e-commerce project asks the team to copy real customer records into the test environment so testers can find defects faster. The company's privacy policy restricts use of personal data outside production. What should the project manager do?
Privacy rules apply regardless of the business benefit, and masked or synthetic data meets the testing need without breaking policy. A small sample still violates the policy, so limiting the volume does not make it compliant.
A company is deciding whether to build an internal reporting tool or buy a SaaS product. Building costs $120,000 up front plus $2,000 per month to maintain. The SaaS product costs $5,000 per month with no setup fee. The tool will be used for 36 months. What is the BEST decision?
Monthly saving from building = $5,000 - $2,000 = $3,000. Break-even = $120,000 / $3,000 = 40 months. Since the tool is only needed for 36 months, buying is cheaper ($180,000 vs $192,000 to build).
Stakeholder attendance at sprint reviews on an agile project has dropped from ten people to two, and feedback now arrives weeks late by email. The product owner is worried the team is building the wrong things. What should the project manager do?
Understanding the cause and making reviews valuable restores real feedback. Mandating attendance gets bodies in the room but not engaged input.
During retrospectives, an agile team says little, and the same two people do most of the talking. The project manager learns that the team's functional manager has been attending to 'keep an eye on progress.' Team members privately say they do not feel safe raising problems. What should the project manager do FIRST?
Retrospectives depend on psychological safety. Removing the source of pressure and using methods such as silent writing or round-robin helps everyone contribute. Forcing input or passing notes to the manager would not create a safe space.
A hybrid project's release burnup chart shows the team completing work at a steady rate, but the total scope line has risen in each of the last four sprints. The release date now looks likely to slip. What is the BEST next step?
The burnup shows the problem is scope growth, not team speed. The project manager should make this visible to the product owner and stakeholders so they can trade scope, priority, or date. Pushing the team harder or hiding the data does not solve it.
A team estimates the story "As a customer, I want to manage my account" at 40 points, which is more than it can finish in one sprint. The product owner wants it done soon. What is the BEST way to handle the story?
Vertical slices each deliver working, testable value to the user and can be prioritized separately. Splitting by technical layer is tempting, but none of those pieces gives users anything usable on its own.
Two senior engineers on a predictive project disagree strongly about a design approach, and the dispute is delaying a critical milestone. You have met with them together twice and tried several resolution techniques, but they remain deadlocked. What should the project manager do NEXT?
Escalation is appropriate once genuine attempts to resolve the conflict at the team level have failed and the issue is hurting the project. Forcing a choice yourself may break the deadlock, but on a technical design matter outside your authority it risks a poor decision and lasting resentment.
During a predictive software project, the project manager learns that a developer added a reporting feature after the client asked for it directly. The feature works well and the client is pleased. What should the project manager do FIRST?
Unapproved work is scope creep even when the client likes it, so its impact must be analyzed and formally processed. Removing it at once overreacts before anyone knows its cost, value or effect on the baseline.
A hybrid project needs an external partner to modernize a legacy billing platform. An earlier request for information confirmed that several capable vendors exist. The buyer knows the business outcomes it needs but wants vendors to propose their own technical approach and delivery method. Which document should the project manager issue NEXT?
A request for proposal is used when the buyer wants sellers to propose how they would solve a problem, not just quote a price. An RFQ or IFB fits well-defined items where price is the main factor. The RFI step is already done.
On a predictive project, an influential department head asks the project manager to add a reporting feature. He says the sponsor already approved it verbally in a hallway conversation. What should the project manager do NEXT?
Every change, even one said to be sponsor-backed, goes through integrated change control so its impact is understood. Confirming with the sponsor and starting work still skips impact analysis and formal approval.
On a hybrid software project, defects found in user acceptance testing have doubled over the last three releases. A senior developer wants to add a second round of manual testing to every release right away. What should the project manager do FIRST?
Adding more testing treats the symptom without knowing the cause. A root cause analysis, such as five whys or a fishbone diagram, helps the team find what changed and fix it at the source. Improvement actions should be based on evidence.
A predictive project reports earned value of $400,000, planned value of $500,000, and actual cost of $450,000. The sponsor asks for a one-line summary of performance. Which statement is accurate?
SPI = EV / PV = 400 / 500 = 0.80, so the project is behind schedule. CPI = EV / AC = 400 / 450 = 0.89, so it is over budget. Both indexes are below 1.
A Scrum team's sprint planning sessions regularly run over four hours because the team keeps discussing unclear stories, missing details, and estimates for the first time. The team is losing focus and energy. What should the project manager suggest?
Ongoing refinement makes the top backlog items ready, which keeps sprint planning short and focused. Full written specifications move away from collaboration and still would not replace the conversation the team needs.
A release is scheduled for tomorrow morning. Two team members get into a minor argument over who should update a shared configuration file, and both look to you to resolve it. What is the BEST approach?
With a release imminent and a low-stakes issue, a quick temporary fix keeps work moving, and the retrospective gives the issue a proper place to be addressed. A full session now uses scarce time on a minor matter right before a release.
Halfway through a two-week sprint, a senior stakeholder asks a Scrum team to add a new dashboard feature that a key customer has requested. The team's sprint goal does not include the dashboard. What is the BEST response?
In agile, new requests go to the product owner, who orders them in the product backlog while the sprint goal stays protected. Adding it now feels customer-focused, but it disrupts the sprint and bypasses the product owner's role.
Three vendors passed the screening criteria. The weighted scoring model gives technical approach 60 percent and price 40 percent. Vendor A scored 80 technical and 60 price. Vendor B scored 70 technical and 90 price. Vendor C scored 90 technical and 50 price. Based on the model, which vendor should be selected?
A = 0.6x80 + 0.4x60 = 48 + 24 = 72. B = 0.6x70 + 0.4x90 = 42 + 36 = 78. C = 0.6x90 + 0.4x50 = 54 + 20 = 74. Vendor B has the highest weighted score.
A stakeholder satisfaction survey on a predictive project shows a very low score from the finance department, with comments saying they are 'not being heard.' The project is on schedule and within budget. What should the project manager do FIRST?
Checking how finance was meant to be engaged, and how that went, prepares the project manager to address the real concern. Adding them to every meeting may waste their time and still not answer what they feel is missing.
A predictive project will replace the billing system used by 400 staff across three departments. The design is complete and go-live is six months away. The sponsor assumes staff will simply switch over once the system is ready. What should the project manager do NEXT to support the change?
Adoption starts with understanding who is affected and how ready they are. A readiness and impact assessment shows where training, communication, and support are needed. Training or directives without this insight often miss the real barriers.
A kanban team's cumulative flow diagram shows the 'In Test' band getting wider every week, while the 'Done' band rises only slowly. Developers keep pulling new items into development. What should the project manager do?
A widening band on a cumulative flow diagram signals a bottleneck at that stage. WIP limits stop new work from piling up and let the team swarm on testing to restore flow. Starting more items makes the bottleneck worse.
During scope validation on a predictive project, a stakeholder says a deliverable is missing a feature she asked for in a requirements workshop. The project manager checks and finds the feature is not in the approved requirements documentation or the scope baseline. What should the project manager do NEXT?
The deliverable matches the approved baseline, so any addition must go through change control. Adding the feature directly because it was mentioned once would bypass the baseline and invite uncontrolled scope growth.
During a retrospective, you notice team members giving short answers and avoiding eye contact. Later, two members tell you privately that there is tension in the team, but they are afraid to speak openly. What should the project manager do?
The team needs psychological safety before it can deal with the conflict, and anonymous input with ground rules helps create it. Calling out the tension publicly may sound direct, but it can make people feel exposed and close up even more.
A hybrid medical device project uses agile for software and a predictive, fixed-price contract for the hardware. A proposed change to the device interface affects both the hardware design and several software stories. What should the project manager do?
Each part follows its own change path: the contractual hardware baseline needs formal change control, while the software side is handled through backlog ordering. Freezing all software work is overly heavy and wastes the agile team's flexibility.
A seller on a hybrid infrastructure project submits a claim saying the buyer's late design approvals caused a six-week delay and $90,000 in extra cost. The buyer's team believes most of the delay was the seller's fault. What should the project manager do FIRST?
Claims should be handled through the claims administration process defined in the contract. Negotiation is the preferred first step, with alternative dispute resolution if needed. Rejecting, paying or going straight to court skips the agreed process.
On an agile project, the product owner has been telling stakeholders that a large set of features will be ready by the end of the quarter. The team's velocity data shows only about half of that work is realistic. What should the project manager do?
Supporting the product owner privately with empirical data protects trust and resets expectations correctly. Contradicting the product owner in front of stakeholders damages the relationship and team credibility.
During the transition period of a predictive project, the warehouse team in one region still keeps stock records in spreadsheets and enters data into the new inventory system only at month end. Other regions use the system daily. What should the project manager do FIRST?
Resistance usually has a reason, such as missing features, weak training, or extra workload. Listening to the team first reveals the real cause so the right fix can be applied. Enforcement or repeated training without knowing the cause can make resistance worse.
Executives on a hybrid program say the weekly dashboard is useless. It shows more than 40 metrics, and they cannot tell whether the program is on track. What should the project manager do?
A useful dashboard shows a small set of KPIs that link to the outcomes stakeholders care about. Working with the executives makes sure the measures fit their decisions. More detail or less frequent updates do not fix the relevance problem.
A vendor delivers software under a fixed-price contract with an agreed list of features. The customer works in an agile way and now wants to replace several features that have not been started with new ideas of similar size. What is the BEST approach?
A swap mechanism keeps the price fair while giving the customer the flexibility agile delivery needs. Rejecting all changes protects the contract but delivers less value, while renegotiating every swap adds heavy overhead.
A contractor on your predictive project claims that recent work falls outside the agreed scope and demands extra payment. Your team lead believes the work was always included. What should the project manager do FIRST?
Checking the contract documents first gives you facts to negotiate from rather than opinions. Sending it straight to legal escalates a disagreement that can often be settled through direct, well-informed negotiation.
On a predictive project, the change control board has just approved a change that adds two weeks and modest cost. The team is eager to begin the work today. What should the project manager do NEXT?
After approval, the PM updates baselines and documents and communicates the decision so that work is measured against the right plan. Starting work immediately feels efficient but leaves performance tracked against an outdated baseline.
A buyer and seller are negotiating a contract for an agile product build. The buyer expects to reprioritize features often as it learns from users but wants a predictable price per delivery cycle. Which contract structure BEST supports these needs?
A fixed price per iteration gives cost predictability, and a 'change for free' clause lets the buyer swap equal-sized backlog items without renegotiating. This matches agile contracting guidance. A single fixed price with change control works against frequent reprioritization.
On an agile team, the only developer who understands a complex legacy integration will leave the company in six weeks. Much of what he knows is based on years of experience rather than documents. What is the BEST approach?
Tacit knowledge transfers best through working side by side, such as pairing. Documentation helps with explicit facts but rarely captures the judgment and experience that matter most here.
An agile team has released four increments of a customer self-service portal. Analytics show that fewer than 10% of customers use the new features, and call center volume has not dropped. The product owner wants to keep building the remaining features on the roadmap. What should the project manager recommend?
Value comes from people using the product, not just from releasing it. Learning why customers are not using the features lets the product owner remove the real barriers before investing in more work. Promotion alone will not help if the features miss user needs.
A predictive project has a budget at completion of $800,000. Halfway through, the CPI is 0.80, and the project manager expects this cost performance to continue. What is the estimate at completion?
When current cost performance is expected to continue, EAC = BAC / CPI. 800,000 / 0.80 = $1,000,000. The project should expect a $200,000 overrun unless something changes.
On a predictive project, the quality team has inspected a set of deliverables and confirmed that they meet the specifications. A meeting with the customer is scheduled for next week. What should the project manager do NEXT?
Quality control confirms correctness, but the customer must still formally accept the deliverables through scope validation. Handing them to operations first skips the acceptance step and can leave disputes unresolved later.
At sprint planning, a newly formed agile team waits for you to assign tasks. One member says, "Just tell us who does what and we will get it done." What is the BEST response?
Coaching the team to plan and pull work themselves builds self-organization from the start, which is the servant leader's role. Assigning tasks for just one sprint seems harmless, but it sets a habit of depending on the project manager.
During a status meeting on a predictive project, the sponsor tells the team to add a security module that is not in the approved scope. The sponsor says there is no time for paperwork because the project is already late. What should the project manager do FIRST?
Even sponsor requests go through integrated change control, and the PM can help by writing the change request and running the impact analysis. Starting immediately feels respectful of authority but skips the analysis needed to protect the baseline.
A predictive project has a BAC of $500,000. At the latest status date, PV is $200,000, EV is $180,000 and AC is $225,000. The cost performance to date is expected to continue for the rest of the project. What is the EAC?
CPI = EV / AC = 180,000 / 225,000 = 0.80. If current cost performance continues, EAC = BAC / CPI = 500,000 / 0.80 = $625,000.
A project manager starts planning a predictive project very similar to one that failed two years ago. The old lessons learned are well documented, but the new team says they have 'no time to read old files.' What should the project manager do?
Lessons only add value when they shape current plans, so the project manager should bring them into planning and risk work. Simply emailing them is unlikely to change behavior.
A predictive project is closing after delivering a new process expected to cut order processing time by 30% over the next year. The project team will be released next week. The sponsor asks how the organization will make sure the benefit is actually achieved. What is the BEST response?
Benefits are often realized after the project ends, so ownership must move to the business. The benefits management plan should name an operational owner, the measures, and when they will be reviewed. Recording the benefit or auditing later does not sustain it.
For two months, a vendor-managed workstream on a hybrid project has reported green status. In informal conversations, several team members say the workstream is weeks behind and the testing environment still is not ready. What should the project manager do FIRST?
The project manager should first verify the facts by checking real progress data with the vendor lead and team. That allows honest and accurate reporting. Changing the status or escalating before checking the data could be unfair or wrong.
A startup team is building a budgeting app in a crowded market where user behavior is unknown. The founders want all 20 planned features ready before launch. The project manager is worried about spending the budget before learning whether people want the app. What should the project manager recommend?
An MVP tests the riskiest assumption early with the least investment, so the team can learn before spending everything. More research delays real feedback, and paper studies rarely predict actual user behavior as well as a working product does.
Your hybrid team wants to use a generative AI tool to write test cases faster. One member suggests feeding real customer records into the tool to make the test cases more realistic. What should the project manager do FIRST?
Using AI responsibly means checking policy and protecting customer data before use, while keeping people accountable for the output. Banning the tool outright avoids the risk but throws away a useful productivity gain.
A product owner wants to swap a story into the current sprint in exchange for one of similar size that has not been started. The developers confirm the swap does not affect the sprint goal. What should the project manager do?
Scrum allows the product owner and developers to renegotiate sprint scope as long as the sprint goal is not endangered. Locking the sprint backlog sounds disciplined, but it is a misreading of the framework and adds needless rigidity.
A project has a BAC of $400,000. To date, EV is $150,000 and AC is $200,000. Management will not increase the budget. Which statement BEST describes the project's cost situation?
TCPI = (BAC - EV) / (BAC - AC) = 250,000 / 200,000 = 1.25. CPI = 150,000 / 200,000 = 0.75. The team must jump from 0.75 to 1.25 efficiency, which is a large improvement and a warning sign.
Two weeks before a hybrid project hands a new customer portal to the operations team, the operations manager says her team is not ready to support it. What should the project manager do FIRST?
Identifying specific readiness gaps against the transition plan lets the project manager address them with targeted action. Delaying without knowing the gaps may cost time without fixing the problem.
An organization is moving from project-based teams to long-lived agile product teams. Middle managers have started delaying decisions and questioning the change in meetings. Privately, several say they are unsure what their role will be afterwards. What should the project manager do?
The resistance comes from uncertainty about personal impact. Involving managers in shaping their future roles addresses that fear and turns likely blockers into supporters. Training alone does not answer what happens to them.
A sponsor on a hybrid program asks the project manager for the 'percent complete' of the agile workstream so it can be combined with the predictive workstreams. The agile team tracks work in story points against a changing backlog. What is the BEST approach?
A burnup chart shows completed work against total scope, including scope changes, and supports a realistic forecast range. That gives the sponsor a clear picture without forcing false precision. Hours spent and sprint counts measure effort, not value delivered.
A team is delivering a timeboxed release with a fixed regulatory date. Effort is split as Must 60%, Should 25%, and Could 15%. Midway, the team forecasts it is about 20% short of capacity. What should the project manager do with the product owner?
MoSCoW protects the Must items in a fixed timebox by giving up Could and then Should items first. Adding contractors mid-release often slows the team down at first and does not reliably close a gap this size in time.
A remote team member who used to be active in discussions has gone quiet over the past two weeks. She keeps her camera off and her recent work has been late. What should the project manager do FIRST?
A private, caring conversation is the emotionally intelligent first step and may reveal causes the project manager can help with. Reporting to her manager skips understanding the situation and can damage trust.
For the third sprint in a row, an agile team has been blocked for several days waiting for the security department to approve new third-party libraries. The team keeps reporting the delay at daily standups. What is the BEST action for the project manager?
A servant leader removes recurring impediments by fixing the cause, such as agreeing a faster approval path with the blocking group. Logging and reporting the delays keeps records but does nothing to unblock the team.
During execution, a new government regulation that was not in the risk register requires $30,000 of extra work. The project still has $50,000 of unused contingency reserve for identified risks. What should the project manager do?
Contingency reserve covers identified risks; this regulation was an unknown-unknown. Management reserve is for such events and sits outside the cost baseline, so using it requires approval through change control. Using contingency would leave identified risks unfunded.
An agile team holds retrospectives every sprint and lists good improvement ideas, but the same problems come back sprint after sprint. What should the project manager do?
Visible, owned actions reviewed regularly turn lessons into real change, with the team holding itself accountable. Assigning items personally takes ownership away from a self-managing team.
An agile team is midway through building a mobile banking app. A new data privacy regulation has been published and takes effect in six months, before the planned launch. It requires explicit consent screens and a way for users to delete their data. What should the project manager do?
In agile, changes in the external environment flow into the product backlog. The product owner, guided by compliance, adds and prioritizes the new requirements so the product launches legally. Pausing work or deferring compliance would put the launch at risk.
A client has been using a new warehouse system in production for three weeks, but has not signed the acceptance document. The project team is ready to move on to other work. What should the project manager do NEXT?
Formal acceptance against the agreed criteria is needed before the project can be closed. Using the product is not the same as signing off. Without it, later disputes about scope or payment become more likely.
A predictive CRM project is about to close on time and on budget. The business case expects a 10% rise in sales within a year, long after the project team disbands. What should the project manager do?
Benefits often arrive after closure, so the benefits plan should name an owner who will measure and sustain them. Keeping the project open just to wait for benefits wastes resources and confuses project and operational work.
An agile team's velocity has dropped for three sprints in a row. A senior manager asks you to push the team to work harder and restore the earlier numbers. What should the project manager do?
The servant leader looks for causes with the team and removes obstacles rather than adding pressure. Setting a velocity target treats velocity as a performance goal, which tends to inflate estimates instead of improving delivery.
At a daily standup, a developer casually mentions that the shared test database has been down for two days and that work has been stalled. No one had raised it before. What should the project manager do NEXT?
Removing impediments quickly is a core servant leader duty, and the PM should also coach the team to surface blockers early. Logging it as a risk is wrong because the problem has already happened and is costing time now.
A newly formed agile team has no historical velocity. The sponsor wants to know when the first release, a backlog of about 300 story points, will be ready. What is the BEST approach for the project manager?
Agile forecasting relies on the team's own measured velocity. After a few sprints, the remaining points divided by a velocity range gives an honest forecast range. Hour-level estimates and borrowed velocities create false precision.
A project manager takes over a predictive project midway because the previous project manager was moved to another assignment. The previous project manager is still available within the company. What should the new project manager do FIRST?
Reviewing the existing plan, logs and registers and speaking with the previous manager captures both explicit and tacit knowledge. Resetting direction or rewriting the plan without that context risks repeating mistakes.
A predictive project imports specialized steel for a bridge. The government unexpectedly announces a 15% tariff on steel imports starting next month. This risk was not in the risk register, and the remaining steel purchases would push costs above the cost baseline. What should the project manager do FIRST?
The first step is to understand the size of the impact on cost, schedule, and the business case. Because this was an unidentified risk, contingency reserve does not cover it, and any baseline change needs approval. Acting before analysis could waste money or breach the contract.
A seller has delivered all items under a fixed-price contract for a predictive project. The buyer's team says everything looks fine and wants to stop work on the contract today. What should the project manager do NEXT?
Closing a procurement means verifying that all terms are met, settling open claims, and giving formal written notice of completion. Paying and closing the file without these checks can leave unresolved obligations. Keeping it open for no reason delays closure.
A product owner uses weighted shortest job first (cost of delay divided by job size). Feature A has a cost of delay of 20 and size 5. Feature B: 30 and 10. Feature C: 12 and 2. Feature D: 24 and 8. Which feature should be done first?
The scores are A 4, B 3, C 6, and D 3, so Feature C delivers the most value per unit of effort. Feature B looks attractive because of its large cost of delay, but its big size makes it a poorer first choice.
On a predictive project, one high performer is publicly praised at nearly every status meeting. Other team members have started to seem less motivated, and one says the recognition feels unfair. What is the BEST action for the project manager?
Balanced, team-wide recognition that fits the culture motivates everyone without punishing the high performer. A competition may sound fair, but it can increase rivalry and work against collaboration.
On a predictive project, an issue assigned to a functional manager has been open for two weeks past its target date. The issue is now starting to threaten a milestone. What should the project manager do NEXT?
The PM should first engage the issue owner directly and then escalate through the agreed path if it stays unresolved. Reassigning the issue bypasses the owner and may not even be within the PM's authority.
For a critical activity, the team gives an optimistic estimate of 4 days, a most likely estimate of 7 days and a pessimistic estimate of 16 days. Using the beta (PERT) distribution, what are the expected duration and the standard deviation?
PERT expected = (O + 4M + P) / 6 = (4 + 28 + 16) / 6 = 48 / 6 = 8 days. Standard deviation = (P - O) / 6 = (16 - 4) / 6 = 2 days.
A hybrid program has teams in two offices. The second office keeps building solutions to problems the first office already solved, because neither knows what the other is doing. What is the BEST way to address this?
Communities of practice and shared demos help both tacit and explicit knowledge flow between sites. Formal reports filed with the PMO are often never read by the people who need them.
An agile team is six months into building a scheduling product, with a full release planned in four months. A competitor has just launched a similar product, and the sales team fears the market window is closing. The sponsor asks the project manager for advice. What is the BEST approach?
When market conditions change, agile teams adapt by delivering the highest-value features sooner. A smaller marketable release gets the product to customers while the window is open. Adding people late often slows a team down.
Halfway through a predictive project, the sponsor cancels it because the market has changed. The team is already being asked to join other projects. What should the project manager do?
A cancelled project still needs to be closed properly. Recording what was completed, why the project ended, and the lessons learned protects the organization and helps future projects. Skipping closure loses that knowledge.
A data warehouse project uses a predictive plan with all reports delivered in month 12. Midway, the sponsor says the sales team needs useful reporting much sooner to support a new pricing strategy. What is the BEST approach?
Incremental delivery lets the sales team get real value early while later areas follow. Crashing brings the whole release in only slightly sooner at higher cost, and the sales team still waits for everything.
A new member of your hybrid team is struggling with the test automation tool the team uses. A key deliverable is due in three weeks, and the member is worried about slowing the team down. What is the BEST approach?
Pairing builds skill while work continues, and planning time for learning keeps the commitment realistic. Reassigning the work is quicker in the short term but leaves the skill gap in place and can damage the member's confidence.
On a hybrid project, a risk that a key vendor might miss a component delivery was identified and given a contingency plan. The vendor has now confirmed the component will be four weeks late. What should the project manager do NEXT?
The risk has occurred and become an issue, so the PM carries out the planned response and tracks it in the issue log. Raising a change request first ignores the contingency plan that was prepared for exactly this event.
An agile team has 8 members at a blended rate of $100 per hour. They work 40-hour weeks in two-week sprints. The remaining release backlog is 360 story points, and the team's stable velocity is 40 points per sprint. What is the estimated cost to finish the remaining backlog?
Burn rate per sprint = 8 x $100 x 80 hours = $64,000. Sprints left = 360 / 40 = 9. Cost = 9 x $64,000 = $576,000.
On an agile team, a tester found a reliable workaround for a test environment failure that blocks the team almost every week. Others keep losing time because only she knows the steps. What should the project manager encourage?
Sharing the steps with the team and recording them makes the knowledge explicit and available to everyone. Relying on her for every incident keeps a single point of failure and interrupts her work.
A predictive project is building a new retail distribution center, justified by forecast sales growth of 20% per year. Halfway through, a sharp economic downturn leads the company to cut its forecast to almost no growth for the next three years. The project is on time and on budget. What should the project manager do?
Projects exist to deliver business value, not just to meet baselines. A major shift in the economic outlook may make the business case invalid, so the sponsor must decide whether to continue, change, or stop. The project manager should not cut scope alone.
A hybrid project is about to hand a new billing platform to the operations team. During a walkthrough, the operations lead admits the support staff have not been trained and do not have runbooks. Go-live is scheduled for next week. What is the BEST course of action?
A smooth transition needs operations to be ready to support the product. Agreeing on a plan with training and runbooks fixes the gap directly. An open-ended delay or ad hoc support from the project team creates new risks.
An agile team has hit its velocity target for six straight sprints and every story meets the definition of done. However, customer satisfaction is falling and usage data shows many new features are rarely used. What should the project manager do?
Velocity measures output, not value, so the team needs outcome measures and user feedback to guide what it builds. Raising velocity would just produce more unused features faster.
A critical defect is found just before a demo. In the team meeting that follows, you feel your frustration rising and notice the team becoming defensive as you speak. What should the project manager do?
Self-regulation is a core part of emotional intelligence, and focusing on facts and learning keeps the team engaged in solving the problem. Showing frustration may signal urgency, but it increases defensiveness and harms trust.
An agile team reports that intermittent failures in its automated test suite are slowing every build. The team has the skills to fix the problem but keeps asking the project manager to sort it out. What is the BEST approach for the project manager?
A servant leader builds self-organization, so when the team can solve a problem, the PM coaches them to own it and stands ready to help. Fixing it personally removes the blocker but makes the team more dependent on the PM.
Work package cost estimates for a project total $800,000. The project also has a contingency reserve of $80,000 for identified risks and a management reserve of $60,000. What is the cost baseline?
The cost baseline includes the work package estimates plus contingency reserve: $800,000 + $80,000 = $880,000. Management reserve is added only to reach the total project budget of $940,000.
A hybrid team has members in three time zones. The daily stand-up is always held late at night for one location, and those members have become quiet and disengaged. What should the project manager do?
Letting the team design a fair arrangement respects everyone and keeps all locations engaged. Excusing one location from the stand-up creates a two-tier team and weakens collaboration.
A project manager is leading a three-year hybrid project to launch a medical device. On a previous project, a late change in import rules caught the team by surprise and delayed launch by six months. The project manager wants to avoid a repeat. What is the BEST approach?
Regular environmental scanning, such as a PESTLE review, helps the team spot external changes early. Building it into ongoing risk reviews means changes are caught while there is still time to respond. Buffers and frozen scope do not prevent the impact.
An agile team has delivered its final release, and the customer is pleased. Team members want to disband right away because they have been assigned to new projects starting Monday. What should the project manager do?
A final retrospective captures lessons from the whole project, not just one sprint. Adding them to the organization's knowledge base helps future teams. Sprint retrospectives alone may miss project-wide insights.
Midway through a predictive project to build a retail kiosk, a competitor launches a cheaper product and the expected revenue drops sharply. The original business case may no longer justify the remaining spend. What should the project manager do?
The project manager keeps the business case current and gives the sponsor the facts needed to decide whether to continue. Cancelling is not the project manager's decision to make alone, even if the numbers look poor.
A key business stakeholder regularly misses sprint reviews but later rejects increments, saying they do not meet her department's needs. The team is frustrated by the late rework. What should the project manager do?
Understanding what keeps her from attending lets you design engagement that works for her and brings feedback earlier. Escalating first damages the relationship before you have tried to solve the problem directly.
On a predictive project, a cost overrun has pushed the forecast beyond the budget tolerance that the project manager is allowed to manage. The team has identified three recovery options with different trade-offs. What should the project manager do?
Once a variance exceeds the PM's tolerance, the decision belongs to the sponsor, and the PM should bring clear options and analysis. Picking the cheapest option feels proactive but makes a decision the PM is not authorized to make.
A hybrid project reports a CPI of 1.10 and an SPI of 0.85. A key milestone on the critical path is at risk, and the customer has stressed that the delivery date matters more than cost. What should the project manager do NEXT?
The project is under budget but behind schedule. Since the date matters most, the cost headroom can fund schedule compression on the critical path after the cause is analyzed. Reporting it as healthy ignores the variance, and cutting scope is not the first option.
On a predictive project, a senior stakeholder complains that she receives too many project emails and most of them are not relevant to her role. What should the project manager do FIRST?
The communications plan should match each stakeholder's needs, so reviewing and updating it fixes the cause. Removing her completely may leave her without information she does need.
During contract closure on a predictive project, the seller claims extra payment for work it says was out of scope. The buyer's team disagrees. The contract includes a dispute resolution clause. What is the preferred way to settle the claim?
Negotiation is the preferred way to settle claims and disputes. Arbitration or litigation should only follow if negotiation fails. Refusing the claim and closing the contract does not resolve the dispute.
Two vice presidents each demand that their feature be built in the next sprint, and each says theirs is most important. The team can only deliver one. The product owner asks the project manager for help. What is the BEST approach?
Transparent value-based criteria, such as cost of delay, let the product owner make and explain the call. Splitting the team leaves both features half done and delivers no value at the sprint's end.
Late in planning a predictive project, you learn that a regional regulatory agency must approve one of the main deliverables. The agency is not in the stakeholder register. What should the project manager do FIRST?
The agency must first be identified and analyzed so you understand its requirements and how to engage it. Meeting the agency right away seems proactive, but without analysis you may not know what it needs or who should be involved.
A sponsor wants to approve one fixed annual budget for a new digital product, with every feature defined up front. The market is uncertain, and early user feedback is expected to change priorities a lot. What is the BEST approach for the project manager?
When value and priorities are uncertain, incremental funding lets the sponsor decide on more investment based on evidence from each release. An MVP tests assumptions early. A fixed annual budget with frozen scope works against learning.
Managers on a co-located agile project keep stopping by the team area to ask developers about status, interrupting their focus several times a day. What is the BEST way to address this?
Information radiators provide current, visible status as pull communication, without interrupting the team. A weekly report adds overhead and is out of date almost as soon as it is written.
A senior stakeholder on your hybrid project demands a detailed written report every week. Preparing it takes the team almost a full day each week, and much of the content repeats what is shown in sprint reviews. What should the project manager do?
Understanding what the stakeholder actually needs often reveals a simpler format, like a dashboard, that serves them and frees the team. Stopping the report without discussion ignores a legitimate stakeholder need and risks the relationship.
On a global agile team, a developer from a culture that discourages disagreeing with senior people never raises concerns in meetings. Later, issues he knew about appear in testing. What should the project manager do?
Respecting cultural differences while building psychological safety and offering other channels helps him contribute. Putting him on the spot in public is likely to increase discomfort rather than openness.
A project will automate several warehouse processes. The workers' union representative has publicly stated that the project threatens jobs and is encouraging staff not to cooperate with requirements interviews. What is the BEST approach?
Engaging a resistant stakeholder early and involving them turns opposition into input and reduces resistance. A leadership directive may force short-term cooperation but often deepens distrust.
On a predictive project, a supplier delay will push a contractual milestone back by three weeks. The contract requires formal notice of any milestone change. The client contact is friendly and usually prefers phone calls. What should the project manager do?
Contractual matters need formal written communication, and a follow-up call keeps the relationship strong. A call alone does not meet the contract and leaves no formal record.
An agile project's sponsor asks you to commit to a fixed date for delivering the entire backlog. The backlog is still changing, and the team has only completed three sprints. What is the BEST response?
A forecast range is honest about uncertainty, and joint prioritization lets the sponsor see what value will arrive by when. A single fixed date sounds responsive but hides the real uncertainty and sets up broken expectations.
On a hybrid project, the weekly status meeting takes ninety minutes, and most of it is team members reading out updates one by one. People say the meeting wastes their time. What is the BEST change?
Push routine updates into a pull format and keep interactive time for issues that need discussion. Shortening each update keeps the same low-value format and still wastes the group's time.
Your stakeholder engagement assessment matrix shows that a department head whose staff will use the new system is currently unaware of the project. You need him to be supportive before user testing starts in two months. What should the project manager do?
The matrix shows a gap between current and desired engagement, so targeted actions that you monitor are needed to close it. A status report raises awareness at best and will not build real support.
A remote agile team relies heavily on chat. Recently, short messages have been read as rude, and two members are now in conflict over tone. What should the project manager do?
A team-created working agreement sets shared expectations, and richer channels reduce misreading. Monitoring chat personally is controlling and does not build the team's own norms.
A stakeholder on your hybrid project goes directly to a developer and asks for a new feature, saying it will only take a day. The developer is unsure whether to start. What should the project manager do?
Routing requests through the product owner protects priorities while respecting the stakeholder, and coaching helps the developer handle it next time. Building it quietly may please one stakeholder but undermines the backlog and the product owner's role.
The real PMP exam at a glance
Score 75% or more on two different sets before you book the real exam. Need a plan for your weak topics? See how No Pass, No Pay works.
PMP exam questions, answered
Straight answers for candidates booking the new PMP exam.
Exam facts checked November 2026. Fees and rules change, so confirm on pmi.org before you book.
How many questions are on the PMP exam in 2026?
The PMP exam has 180 questions in 240 minutes, with two 10-minute breaks. That is the format of the new exam PMI introduced on July 9, 2026. This practice exam uses the same question count and the same 4-hour timer, so you can check your pace before test day.
What changed in the PMP exam in July 2026?
PMI moved to a new exam content outline aligned with the PMBOK Guide, 8th Edition. The domain weights are now People 33%, Process 41% and Business Environment 26%. Business Environment was 8% before, so strategy, value delivery and governance now carry far more weight.
How much does the PMP exam cost in the US?
The PMP exam fee is $425 for PMI members and $675 for non-members (2026 pricing). PMI membership costs about $160 a year plus a $10 joining fee, so joining first usually works out cheaper.
What is the passing score for the PMP exam?
PMI does not publish a passing score. You get a pass or fail result, plus a rating for each domain: Above Target, Target, Below Target or Needs Improvement. A practical benchmark is to score 75% or more on two different full-length sets here before you book.
Who is eligible to take the PMP exam?
You need 35 hours of project management education plus experience leading projects: 36 months with a four-year degree, or 60 months with a high school diploma. A current CAPM certification covers the 35 hours. Our live PMP certification training gives you the 35 hours.
Is this PMP practice exam free?
Yes. Both sets, including PMP practice exam Set 2, are free with no signup. Your progress is saved on your device, and you can email yourself a score report with a study plan for your weak domains.
More free Project Management & Agile practice tests
Original practice questions written by CertOcean in the style of the PMP exam. They are not real exam questions. PMP and PMI are trademarks of their owners. Real exam format: 180 questions · 240 minutes · based on the PMP Examination Content Outline effective July 9, 2026.