
Clean one-question-per-page HTML exam with corrected option formatting, improved exhibits, answer review, and EVOLVE branding.
Select a question number to navigate directly.

| Situation | Best Response |
|---|---|
| 1. Business case assumptions are no longer valid | A. Review project justification and expected benefits |
| 2. Team lacks authority to use resources | B. Obtain formal project authorization |
| 3. Stakeholders cannot see the big picture | C. Use a visual planning tool to align objectives, risks, deliverables, and roles |
| 4. Internal capability is weak and outsourcing may be needed | D. Perform make-or-buy and sourcing analysis |
| Activity | Duration | Predecessor |
|---|---|---|
| A. Define reporting requirements | 4 days | None |
| B. Design data model | 6 days | A |
| C. Configure reporting tool | 5 days | A |
| D. Build data interfaces | 7 days | B |
| E. Develop report templates | 6 days | B and C |
| F. Perform system testing | 4 days | D and E |
| G. Obtain compliance approval | 3 days | F |
| Activity | Duration | Dependency |
|---|---|---|
| A. Complete UX design | 6 days | Starts at project start |
| B. Develop front-end pages | 8 days | Starts 2 days after A starts |
| C. Prepare user documentation | 5 days | Starts 3 days before B finishes |
| D. Conduct final review | 4 days | Starts after both B and C are finished |
| E. Launch approval milestone | 0 days | Occurs after D is finished |
| Option | Implementation Cost | Outcome | Probability | Financial Benefit |
|---|---|---|---|---|
| Option A: Build internally | $120,000 | High adoption | 60% | $350,000 |
| Option A: Build internally | $120,000 | Low adoption | 40% | $100,000 |
| Option B: Buy vendor solution | $180,000 | High adoption | 70% | $420,000 |
| Option B: Buy vendor solution | $180,000 | Low adoption | 30% | $150,000 |
| Path | Activities | Duration |
|---|---|---|
| Path 1 | A → B → D → G | 18 days |
| Path 2 | A → C → E → G | 22 days |
| Path 3 | A → C → F → G | 20 days |
| Situation | Best Response |
|---|---|
| 1. Activity H has ES = 10, LS = 14, and the team wants to delay it by 3 days. | A. Use PERT expected duration because it considers uncertainty. |
| 2. Activity E is on the longest path in the network and a stakeholder wants to delay it. | B. Accept the delay because the activity has 4 days of total float, but monitor the remaining flexibility. |
| 3. A noncritical path is delayed and may become longer than the original critical path. | C. Do not delay without analysis because it is on the critical path. |
| 4. The sponsor wants to use only the optimistic estimate for a task with uncertainty. | D. Recalculate the schedule because the critical path can change. |
| Path | Duration |
|---|---|
| A → B → D → H | 30 days |
| A → C → E → H | 27 days |
| A → C → F → H | 25 days |
| Contract Element | Value |
|---|---|
| Target Cost | $500,000 |
| Target Fee | $50,000 |
| Buyer/Seller Share Ratio | 80/20 |
| Actual Cost | $450,000 |
| WBS ID | Work Package / Deliverable | Status | Acceptance Criteria | Customer Validation | Change Request Status |
|---|---|---|---|---|---|
| 1.1 | Requirements workshops | Completed | Stakeholder needs documented and approved | Accepted | N/A |
| 1.2 | Process redesign | Completed | Future-state workflow approved by operations | Accepted | N/A |
| 1.3 | Reporting dashboard | Completed | Displays approved operational KPIs | Rejected | CR-014 submitted |
| 1.4 | Mobile access feature | In progress | Secure access for approved user groups | Not yet validated | N/A |
| 1.5 | AI recommendation engine | Not in baseline scope | No approved acceptance criteria | Not validated | No approved CR |
| Work Package | Estimated Cost |
|---|---|
| Requirements analysis | $8,000 |
| Design | $12,000 |
| Development | $40,000 |
| Testing | $18,000 |
| Deployment support | $7,000 |
| Decision | Risk Event | Probability | Impact if Risk Occurs |
|---|---|---|---|
| Implement control | Security incident | 10% | -$500,000 |
| Do not implement control | Security incident | 35% | -$500,000 |
| Reporting Period | CPI | SPI |
|---|---|---|
| Month 1 | 1.05 | 1.02 |
| Month 2 | 0.96 | 1.04 |
| Month 3 | 0.89 | 0.92 |
| Month 4 | 1.03 | 0.88 |
| Situation | Best Response |
|---|---|
| 1. A bank project requires formal approvals, regulatory reporting, and documented sign-offs. | A. Use agile feedback loops while tailoring documentation and governance to meet compliance needs. |
| 2. An adaptive product team can reprioritize work but the organization still needs visibility and early warning signs. | B. Use a structured decision and approval process suitable for the regulatory risk. |
| 3. A regulated project wants agile practices, but the regulatory manager requires traceability and controlled decision-making. | C. Use lightweight governance with objectives, decision boundaries, progress indicators, and feedback loops. |
| 4. Two agile subteams make conflicting decisions and claim self-governance means no approval is needed. | D. Establish shared objectives, decision boundaries, and alignment mechanisms. |
| Situation | Best Response |
|---|---|
| 1. Users say the new workflow does not support urgent claims, although the team is on schedule. | A. Define benefit measures and clarify ownership for maintaining content after launch. |
| 2. A project has no clear benefits measurement approach, but the sponsor says benefits are “obvious.” | B. Use existing lessons learned and create new knowledge during the project. |
| 3. A knowledge platform is being built, but benefits measurement and content ownership are unclear. | C. Review the concerns against the business case, expected benefits, and value delivery. |
| 4. The team is repeating mistakes from a previous project because lessons learned are not being used. | D. Clarify expected benefits, benefit measures, ownership, and timing before finalizing the plan. |
| Activity | On Path | Maximum Crash | Crash Cost per Day |
|---|---|---|---|
| B | Critical Path | 2 days | $4,000/day |
| D | Critical Path | 3 days | $6,000/day |
| E | Non-critical Path | 2 days | $3,000/day |
| F | Non-critical Path | 1 day | $2,000/day |
| Path | Activities | Duration |
|---|---|---|
| Path 1 | A → B → D → G | 28 days |
| Path 2 | A → C → E → G | 25 days |
| Path 3 | A → C → F → G | 24 days |
| Threat | Situation |
|---|---|
| Threat 1 | The selected site is located in a flood-prone area. The team can choose a different approved site, but it will require an early design adjustment. |
| Threat 2 | There is a risk that equipment delivery may be delayed because of customs inspection. The team can order critical equipment earlier and add buffer time to the logistics plan. |
| Threat 3 | Specialized cooling equipment may fail during the warranty period. The project can purchase an extended warranty and maintenance contract from the supplier. |
| Threat 4 | Minor weather delays may occur during outdoor installation. The impact is small, and the team decides to monitor the situation without taking active action now. |
| Threat 5 | A new national cybersecurity regulation may require major design changes. This decision is beyond the project manager’s authority and must be handled by executive leadership. |
| Opportunity | Situation |
|---|---|
| Opportunity 1 | A new government grant may fully fund the battery-storage component if the project submits the application within two weeks. |
| Opportunity 2 | A new panel supplier may improve energy output by 15%, but the team needs to adjust the design to increase the chance of gaining that benefit. |
| Opportunity 3 | A technology partner has specialized expertise in energy analytics and is willing to co-develop the monitoring dashboard in exchange for shared benefits. |
| Opportunity 4 | There is a small chance that energy prices will rise, which would increase the financial value of the project, but no practical action is needed. |
| Concept | Description |
|---|---|
| 1. Project | A. Ongoing, repetitive work that sustains the business |
| 2. Program | B. A temporary effort that creates a unique product, service, or result |
| 3. Portfolio | C. Related projects managed together to achieve benefits not available from managing them separately |
| 4. Operations | D. Projects, programs, and other work grouped to achieve strategic objectives |
| Activity | Duration | Total Float | Resource Needed |
|---|---|---|---|
| A | 4 days | 0 days | Data Architect |
| B | 8 days | 0 days | Senior Data Engineer |
| C | 6 days | 4 days | Senior Data Engineer |
| D | 10 days | 0 days | Senior Data Engineer |
| E | 5 days | 4 days | Senior Data Engineer |
| F | 3 days | 0 days | Data Architect |
| Problem | Current Response | Result |
|---|---|---|
| Defects found late | More final testing | Schedule pressure increases |
| Changing priorities | Larger status reports | Stakeholders still dissatisfied |
| Blocked stories | Team starts more work | WIP increases |
| Product owner unavailable | Team guesses priorities | Rework increases |
| Change Benefit | Change Impact |
|---|---|
| Higher user satisfaction | +6 weeks schedule delay |
| Better usability | Additional supplier cost |
| Stronger adoption potential | Regulatory milestone risk |
| Stakeholder support | Requires training redesign |
| Stakeholder | Power | Interest | Urgency | Legitimacy |
|---|---|---|---|---|
| City mayor | High | Medium | Medium | High |
| Daily commuters | Low | High | High | High |
| Regulatory authority | High | Low | High | High |
| Local media | Medium | High | Medium | Low |
| Resource Issue | Current Situation |
|---|---|
| Database specialists | Over-allocated across two projects |
| Testing team | Waiting for database support |
| Training team | Scheduled to start next week, but training materials are not ready |
| External consultant | Completed assigned work and is no longer needed |
| Operations team | Needs handover support before go-live |
| Tool | Best Use |
|---|---|
| Focus group | Explore expectations and attitudes through moderated discussion |
| Brainwriting | Generate ideas individually before discussion |
| Five Whys | Explore possible root causes |
| SWOT | Analyze strengths, weaknesses, opportunities, and threats |
| Project canvas | Visualize key project elements on one page |
| Stakeholder | Current Engagement | Desired Engagement |
|---|---|---|
| Procurement director | Supportive | Leading |
| Finance manager | Neutral | Supportive |
| End users | Resistant | Supportive |
| IT security lead | Unaware | Neutral |
| Situation | Description |
|---|---|
| 1 | A supplier may delay delivery of a critical component. The team decides to order the component earlier and add schedule buffer. |
| 2 | A project site is located in a flood-prone area. The sponsor approves moving the project to a different approved location. |
| 3 | A specialized machine may fail during installation. The team purchases an extended warranty and support contract. |
| 4 | Minor weather delays may occur, but the impact is small. The team decides to monitor the risk without taking immediate action. |
| Diagnostic Factor | Project Situation |
|---|---|
| Requirements clarity | Core reporting needs are known, but dashboard details will evolve after user feedback |
| Compliance risk | Moderate; financial data must be controlled and reviewed |
| Stakeholder involvement | Business users are available weekly for demonstrations |
| Delivery expectation | Sponsor wants usable reporting modules every month |
| Team experience | Team has experience with both predictive and agile practices |
| Organizational governance | Formal approval is required for budget, scope baseline, and release decisions |
| Situation | Description |
|---|---|
| 1 | The payment gateway is currently down, and testing cannot continue. |
| 2 | A key vendor may delay delivery of encryption certificates next month. |
| 3 | A business analyst has already resigned, and requirements workshops are affected. |
| 4 | New regulatory guidance may be released before deployment, requiring design changes. |

| Measure | Value |
|---|---|
| Earned Value (EV) | $600,000 |
| Actual Cost (AC) | $750,000 |
| Budget at Completion (BAC) | $1,000,000 |
| Activity | Description |
|---|---|
| Activity 1 | Reviews whether the team is following approved development, testing, documentation, and compliance processes |
| Activity 2 | Inspects completed device components to confirm they meet technical specifications and acceptance criteria |
| Item | Current Status |
|---|---|
| Product delivered | Yes |
| Schedule baseline | Met |
| Budget baseline | Met |
| User adoption | Low |
| Expected cost reduction | Not achieved |
| Customer satisfaction | No improvement |
| Sponsor report | “Project completed successfully” |
| Diagnostic Area | Project Situation |
|---|---|
| Requirements | Core features are known, but user experience details will evolve through feedback |
| Compliance | Customer data privacy controls are mandatory |
| Stakeholders | Business users want demonstrations every two weeks |
| Team | Experienced with agile delivery |
| Sponsor expectation | Early usable releases are preferred |
| Governance | Budget and release approvals must remain formal |
| Measure | Value |
|---|---|
| Planned Value (PV) | $450,000 |
| Earned Value (EV) | $400,000 |
| Actual Cost (AC) | $520,000 |
| Reporting Period | CPI | SPI |
|---|---|---|
| Month 1 | 1.02 | 0.98 |
| Month 2 | 0.96 | 0.95 |
| Month 3 | 0.91 | 0.93 |
| Month 4 | 0.84 | 0.86 |
| Situation | Governance Risk |
|---|---|
| Too many approvals for a low-risk internal tool | Delay and wasted effort |
| No clear decision authority for a strategic project | Conflicting decisions |
| No escalation path for vendor delays | Slow response to issues |
| No benefit measures | Output delivered without proving value |
Click the button below to calculate your score and show the answers and explanations for all questions.