What Task 1.1 asks you to sort
The outline gives Task 1.1 seven enablers. Five of them live on this page: project versus program versus portfolio, project versus operations, predictive versus adaptive approaches, reviewing a scope, and the idea of a project as a vehicle for change. The other two have their own pages: issues, risks, assumptions and constraints sit under risks and planned responses, and the Code of Ethics sits under roles, leadership and ethics.
Life-cycle judgment does not stay in one corner of the exam. The 2023 outline says predictive, adaptive and business-analysis approaches are not isolated to any particular domain or task, and that the mix of items per approach may vary by form. PMI publishes no predictive or agile share for the CAPM (2023 CAPM Examination Content Outline, checked October 30, 2026). Each side is worked through on its own page: predictive processes and plans and agile fit and frameworks.
The outline lists the PMBOK® Guide Seventh Edition among its seven references and notes there are noticeable differences between the two. The Eighth Edition came out in November 2025; the 2023 CAPM outline still names the Seventh (PMI PMBOK Guide page, checked October 30, 2026). Vocabulary from the Seventh, such as its performance domains, can turn up in a stem.
Terms that look alike on purpose
- Project
- Temporary work with a defined start and finish that produces a unique product, service or result. Moving a help desk onto a new phone system is one; so is opening a second warehouse.
- Operations
- Ongoing, repeating work that keeps the organization running, such as month-end close in accounting. It has targets and budgets, and it does not end when a result is delivered.
- Program
- Related projects, and sometimes operational work, managed as a set because their benefits depend on each other. An airline opening a new route by securing gate slots, training crews and launching a fare campaign as linked projects is running a program.
- Portfolio
- Everything an organization chooses to invest in to meet its strategy: projects, programs and operations, related or not. Portfolio management selects, ranks and funds; it does not schedule the work.
- Predictive life cycle
- Scope, schedule and cost are worked out early and the phases run in sequence. Everyday usage calls it waterfall; the plan-based side of the exam is covered on predictive processes and plans.
- Iterative
- Repeated cycles that refine the same product as feedback comes in. The design improves; delivery may still come at the end.
- Incremental
- Delivery in usable slices, each adding to the last. A finished first floor of a parking garage that opens before the second floor exists is an increment.
- Adaptive (agile)
- Iterative and incremental at once, in short timeboxes, with the backlog reordered as the team learns. The same reordering shows up later in roadmaps and releases.
- Hybrid
- A tailored mix of approaches, applied by component or by phase. It is a design decision, so a stem usually gives a reason for each part.
- Phase gate
- A review at the end of a phase where someone with authority decides to continue, change course or stop.
Sort these situations
Each card describes a piece of work or a decision about how to run it. Pick the label or the move the outline points to, then read why the other options miss. The practice test filtered to life cycles and portfolios shuffles the same topic with fresh cards.
Practice cards here are written for study, not taken from PMI. The real CAPM mixes multiple choice with drag-and-drop, hot spot, comic-strip and video items.
Card 01 of 18 · 0 done · 0 right
To do 18
Doing
Card 01 of 18
A pharmaceutical firm is developing a new compound. Early studies are inconclusive, the regulatory pathway is uncertain, and the target product profile may shift as trial data emerge. Senior leadership has approved a fixed total budget of three million dollars. Which development approach is most suitable?
Note on A
A waterfall approach needs stable requirements up front, which this compound does not have.
Note on B
Phased gates still assume a predictable plan for each phase, which conflicts with a target that shifts as trial data come in.
Note on C
Correct: High uncertainty and evolving requirements call for an adaptive approach, which can work within a fixed budget by adjusting scope as learning occurs.
Note on D
Fixed stages bring back rigidity in an environment where the target profile is expected to keep changing.
Card 02 of 18
A project manager in Program Alpha learns that a scarce systems architect allocated to their project will be moved to a program that supports a different strategic objective. Both programs draw from the same portfolio funding pool, and the trade-off affects which strategic priority is funded this quarter. The project manager believes the move will delay an approved deliverable. What should the project manager do?
Note on A
Correct: The trade-off is between programs serving different strategic objectives from one funding pool, so the impact belongs before the portfolio governance board that sets those priorities.
Note on B
Asking for more funding is a possible outcome of a governance review, not a way to settle a cross-program priority decision.
Note on C
The functional manager handles line reporting, but the question is which strategic priority gets funded, which is a portfolio decision.
Note on D
Reassigning tasks and rebaselining quietly absorbs a governance decision the project manager has no authority to make.
Card 03 of 18
A program manager insists that every component of a large program, including a heavily regulated compliance module with fixed requirements and an innovative customer-facing application, must use the same agile methodology so that status reporting stays consistent. Why is this position a mistake?
Note on A
Hybrid approaches do not always slow delivery; tailoring is meant to fit each component’s needs.
Note on B
Reporting preferences are a minor concern and not the reason a single method is a poor fit.
Note on C
Correct: Development approaches should be tailored to each component’s uncertainty and complexity, so a fixed-requirement compliance module and an innovative app may need different approaches.
Note on D
Agile methods are used well beyond software, so this is not why the position is wrong.
Card 04 of 18
A team maintains an existing payroll system and also develops a new payroll module with a defined start and end. Which classification applies to developing the new payroll module?
Note on A
Ongoing operations are repetitive and continuous, while this module has a defined start and end.
Note on B
Correct: Building a new module with a defined start and end that creates a unique result is a project.
Note on C
Production support sustains existing systems, whereas the new module is a temporary effort to create something new.
Note on D
Routine maintenance keeps the current payroll system running, which is the team’s other, operational work.
Card 05 of 18
A program’s customer requirements change rapidly, so the team wants to adopt adaptive delivery and re-plan continuously. However, the program must also submit detailed regulatory reports on a fixed annual schedule, and auditors require documented baselines. Which governance approach best balances these conditions?
Note on A
Correct: Adaptive delivery handles fast-changing customer needs, while predictive controls for compliance meet the fixed reporting schedule and the auditors’ need for baselines.
Note on B
Fully adaptive governance does not provide the documented baselines that auditors require.
Note on C
Making the whole program predictive would stifle the continuous re-planning that fast-changing requirements need.
Note on D
This reverses the fit: delivery needs to be adaptive, and compliance governance needs to be predictive.
Card 06 of 18
A project team concentrates on meeting requirements, scope and quality expectations so that its deliverables produce the business outcomes the project was set up for. Which PMBOK Guide 7th edition performance domain covers this work?
Note on A
The Project Work domain covers establishing processes, managing physical resources, and fostering learning, not meeting requirements and quality for outcomes.
Note on B
The Planning domain organizes and coordinates the work rather than focusing on delivering scope and quality.
Note on C
The Measurement domain assesses performance; it does not cover meeting requirements and quality.
Note on D
Correct: The Delivery performance domain is about meeting requirements, scope, and quality so deliverables produce the intended outcomes.
Card 07 of 18
A project team must deliver a product by a fixed regulatory deadline. The scope and quality requirements are clearly defined and unlikely to change. Which development approach is MOST appropriate?
Note on A
Correct: Clearly defined, stable scope and quality requirements with a fixed deadline fit a predictive approach.
Note on B
Incremental delivery helps when value can be released in pieces, but the scenario stresses fixed, fully known requirements rather than early partial value.
Note on C
Adaptive approaches suit uncertain or changing requirements, which is not the case here.
Note on D
A hybrid adds complexity without benefit when all requirements are stable.
Card 08 of 18
Two projects need the same scarce testing laboratory during the same week. The project manager owns the laboratory schedule and has published allocation criteria based on contractual delivery dates and regulatory deadlines. A senior stakeholder whose project ranks lower under those criteria calls and asks to be moved to the front of the queue. What should the project manager do?
Note on A
Moving a project up because of a stakeholder’s seniority breaks the published criteria and undermines fairness.
Note on B
Correct: Applying the published allocation criteria impartially is fair, transparent, and consistent with the project manager’s responsibility for the schedule.
Note on C
Splitting the lab time equally ignores criteria based on contractual and regulatory deadlines.
Note on D
The project manager owns the lab schedule and already has criteria, so sending the decision to informal negotiation abandons that responsibility.
Card 09 of 18
An organization has established a new program to streamline its manufacturing supply chain. The program manager is trying to schedule the execution order of three highly interdependent internal projects to ensure the operational transition goes smoothly. The Chief Strategy Officer intervenes, insisting that the program manager must prioritize the projects using the corporate scoring model—a tool designed to allocate enterprise funding across competing business units based on long-term market ROI. What fundamental concept is the executive misunderstanding in this scenario?
Note on A
The scenario is about which management level a tool belongs to, not about risk analysis versus schedule network techniques.
Note on B
No PMO or functional manager is involved; the confusion is between portfolio and program management.
Note on C
Correct: A scoring model that allocates enterprise funding by ROI is a portfolio tool, while sequencing interdependent projects for a smooth transition is a program-level decision.
Note on D
The work is a program of projects, not routine operations, so this misreads the situation.
Card 10 of 18
A company is managing several related projects to deploy a new customer service platform, coordinating them to realize benefits that would not be achieved separately. This group is best described as what?
Note on A
A portfolio groups work to achieve strategic objectives and its parts may be unrelated, whereas these projects are related and coordinated for shared benefits.
Note on B
Correct: Related projects coordinated to obtain benefits not available by managing them separately make up a program.
Note on C
Strategic business initiative is a general term, not the standard name for coordinated related projects.
Note on D
A single project has one unique result, while this effort coordinates several projects.
Card 11 of 18
A large healthcare organization is undertaking a strategic initiative to digitize patient records, upgrade hospital network infrastructure, and train medical staff on new software. A director is assigned to oversee these efforts. The director explains that managing these components together provides synergistic benefits. Which term best categorizes this structured oversight?
Note on A
These are separate but related efforts, not phases of one project.
Note on B
Correct: Coordinating related components so they produce combined benefits is program management.
Note on C
Portfolio management selects and balances investments against strategy rather than coordinating related components for shared benefits.
Note on D
A PMO standardizes governance and supports projects; it is not a director overseeing related efforts for combined benefits.
Card 12 of 18
A global logistics firm has been running a multi-year IT infrastructure upgrade using a traditional, highly predictive methodology. Recently, extreme volatility in international trade regulations has rendered the project’s original 12-month requirements document largely obsolete. The project sponsor demands a new strategy to ensure the project continues to deliver relevant business value despite the constant regulatory shifts. Which methodology adjustment should the project manager recommend?
Note on A
Correct: With requirements constantly changing, short iterations and a prioritized backlog let the project adjust frequently and keep delivering value.
Note on B
A rewritten requirements document would likely be outdated again before execution resumes.
Note on C
Testing against obsolete requirements wastes effort and does nothing to keep the project relevant.
Note on D
More contingency reserve cannot fix a plan whose requirements keep becoming outdated.
Card 13 of 18
A project manager selects Scrum for a construction project simply because Scrum is the most widely discussed methodology in industry forums. The project has fixed regulatory milestones, stable requirements, and a rigid inspection calendar. Why is this selection approach flawed?
Note on A
Standards bodies recognize many widely used methods; recognition is not the problem.
Note on B
Correct: The approach should be chosen from project attributes such as requirement stability, regulation, and inspection schedules, not popularity.
Note on C
The amount of documentation depends on tailoring, not on how popular a method is.
Note on D
Widely used methods can be tailored; that is not why this selection is flawed.
Card 14 of 18
Project stakeholders enthusiastically request an agile approach for a new system deployment. However, the system requires massive, highly coupled integration with fragile legacy mainframes. How should the project manager determine the most appropriate life cycle approach?
Note on A
Continuous integration is an engineering practice, not a life cycle choice, and tightly coupled legacy systems cannot be deployed as if they were uncoupled.
Note on B
Applying an adaptive life cycle to fragile, tightly coupled connections ignores the dependency risk.
Note on C
Correct: The life cycle should fit the work, and heavy, tightly coupled dependencies on fragile legacy systems favor upfront planning and a predictive approach.
Note on D
Extreme programming is a set of team practices; it does not resolve the dependency and integration constraints that drive the life cycle choice.
Card 15 of 18
A support team handles daily tickets and has a quarterly target to reduce unresolved tickets by 10%. What is this work?
Note on A
Handling daily tickets is ongoing work, and a quarterly target does not make it a temporary project.
Note on B
A portfolio is a collection of projects, programs, and operations managed for strategy, not a single team’s routine work.
Note on C
A performance metric alone does not make work a project, since there is no unique deliverable or defined end.
Note on D
Correct: Handling tickets every day while working toward an improvement target is ongoing operational work.
Card 16 of 18
An organization has fully transitioned its software delivery to an agile framework. A dedicated team is now assigned to monitor and maintain the continuous integration and continuous deployment (CI/CD) pipelines, ensuring daily code merges occur without system failures. How should the organization classify this set of activities?
Note on A
Pipeline stages describe how code moves through deployment, not phases of a temporary project.
Note on B
Delivering features through the pipeline does not make its upkeep a program of related projects.
Note on C
Correct: Monitoring and maintaining the pipeline every day is ongoing, repetitive work that sustains the business, so it is operations.
Note on D
Unpredictable defects arise in operations too, and this work is ongoing with no defined end.
Card 17 of 18
A medical device program must satisfy strict regulatory documentation and formal stage-gate approvals. At the same time, the user-facing software features are expected to evolve based on clinician feedback gathered during development. Which approach is most appropriate?
Note on A
A fully baselined scope would resist the feature changes expected from clinician feedback.
Note on B
Quarterly releases address delivery cadence but not the need to combine formal stage gates with evolving features.
Note on C
Correct: A hybrid approach combines predictive controls for regulatory documentation and stage gates with adaptive development for features that evolve from clinician feedback.
Note on D
A purely adaptive approach does not provide the formal stage-gate approvals the regulations require.
Card 18 of 18
An enterprise is undergoing a major digital transformation. The executive board is currently evaluating multiple proposed initiatives to determine which ones best align with the company’s long-term strategic objectives and risk tolerance. Meanwhile, a separate management team is coordinating a specific group of related software deployments to ensure they collectively deliver a unified customer experience that individual deployments could not achieve alone. Which statement most accurately distinguishes the roles in this scenario?
Note on A
This reverses the roles: choosing initiatives against strategy is portfolio work, and coordinating related deployments is program work.
Note on B
Only the management team coordinates related components, while the board is selecting initiatives against strategy.
Note on C
Correct: The board selects initiatives against strategy and risk tolerance, which is portfolio management, and the team coordinates related deployments for a combined benefit, which is program management.
Note on D
Evaluating strategic initiatives is not routine operations, and coordinating related deployments is not portfolio prioritization.
Done 0
Loose ends
Are the PMBOK performance domains the same as the CAPM domains?
No. The CAPM’s four domains come from the 2023 Examination Content Outline: 36%, 17%, 20% and 27% (2023 CAPM Examination Content Outline, checked October 30, 2026). The PMBOK® Guide performance domains are a separate framework that the outline lists as one of its references.
Does the CAPM lean predictive or agile?
PMI does not say. The 2023 outline weights Domain II, Predictive, Plan-Based Methodologies, at 17% and Domain III, Agile Frameworks/Methodologies, at 20%, but it also states that approaches appear across every domain and that the mix may vary by form (2023 CAPM Examination Content Outline, checked October 30, 2026).
Is waterfall the same thing as predictive?
For exam purposes, yes. PMI’s material says predictive or plan-based; waterfall is the industry nickname for the same sequential approach.
Which page continues the planning side of Domain I?
Baselines, registers, milestones and closure are on plans and registers, the next topic in the outline’s order.