CAPM Practice Test

Certified Associate in Project Management (CAPM)®

CAPM overview

  • 200 practice questions
  • 32 flashcards
  • 4 study guide topics
  • 40 key terms

What you'll study

  • Project Management Fundamentals and Core Concepts36%
  • Predictive, Plan-Based Methodologies17%
  • Agile Frameworks/Methodologies20%
  • Business Analysis Frameworks27%

The Certified Associate in Project Management (CAPM)® is the Project Management Institute's foundational project management credential, and PMI describes it as requiring no experience: it is aimed at people who want to show they hold the knowledge and skills project teams demand, across predictive project management, agile principles and business analysis. It suits students, career changers and early-career practitioners - PMI lists roles such as project coordinator, project analyst, project administrator and assistant project manager as common paths - and anyone building a base before a more advanced certification.

The exam has 150 questions in 180 minutes; 15 are unscored pretest questions and 135 are scored. Content is weighted across four domains: Project Management Fundamentals and Core Concepts (36%), Predictive, Plan-Based Methodologies (17%), Agile Frameworks/Methodologies (20%) and Business Analysis Frameworks (27%). To apply you need a secondary degree, to be at least 18 years old, and at least 23 hours of project management education completed before the exam. The exam fee is $300, or $225 for PMI members.

Because core concepts and business analysis together make up 63% of the exam, weight your study time accordingly. Preparation usually combines the PMBOK® Guide, a structured course that also satisfies the 23-hour requirement, and repeated practice questions with review of every miss. This page is independent study material and is not affiliated with or endorsed by PMI.

Common mistakes

Classifying every piece of work in a scenario as a 'project' - labelling ongoing production support, a recurring service, or a coordinated group of related projects as a single project - and then selecting project life-cycle answers for it.

Candidates skim for the word 'deliverable' or 'team' and default to project vocabulary, because in their own organization everything is called a project regardless of whether it is temporary or produces a unique result.

What to do instead

Before reading the options, apply a two-question test to the scenario: is the work temporary (has a defined end), and does it produce a unique product, service, or result? If either answer is no, it is operations; if it is a group of related projects managed together, it is a program; if it is the whole collection aligned to strategy, it is a portfolio. Only then read the answers.

Selecting an answer in which the project manager personally approves the project charter, authorizes the budget, accepts a high risk on the organization's behalf, or unilaterally reorders product features.

In small organizations the project manager often does all of these in practice, so the option feels natural and authoritative; candidates also gravitate to the answer where the PM takes decisive action.

What to do instead

Memorize the decision-authority boundary as a short list: charter and funding belong to the sponsor, product priority and backlog order belong to the product owner (or customer), team task assignment belongs to the team. When an option has the PM doing one of these things, eliminate it before comparing the survivors.

On questions that ask what the project manager should do FIRST or NEXT, choosing the most complete, most senior-sounding, or most resolution-oriented option (escalate, update the register, hold a meeting) rather than the earliest action in the sequence.

The distractor options are usually valid actions taken at some point, so they feel 'correct'; candidates respond to the problem described in the stem instead of to the ordering word in the question.

What to do instead

Circle the ordering word before evaluating options. Then rank all four options chronologically: which must logically happen before the others (understand/assess/verify before act; document before communicate; analyze before escalate)? Choose the earliest valid step, not the most decisive one.

Implementing a requested change, or approving it informally, in the scenario instead of routing it through Perform Integrated Change Control - and failing to recognize that an approved change must also update the affected baselines and plan components.

Candidates study the change-control process as a list of ITTOs and never build the causal chain (request → assess impact → decide → update plan/baselines → implement → verify), so 'do the work' reads as a reasonable next step.

What to do instead

Drill the chain aloud until it is automatic, and treat any scenario containing the words 'change', 'request', or 'new requirement' as a cue to look for the answer that assesses impact and obtains a decision, not the one that executes the work. When two change answers remain, prefer the one that also mentions updating the plan or baselines.

Guessing on quantitative items - earned value, schedule variance, PERT/three-point estimates, expected monetary value, communication channels, or number of iterations - instead of computing them on scratch paper.

Under time pressure, estimate and EVM questions look long, and candidates convince themselves they can 'eyeball' whether cost performance is good or bad; formulas memorized as symbols are also easily inverted under stress.

What to do instead

Write the formula and the known values before looking at any option, and keep a one-line cheat list in the last ten minutes of study (EV = BAC × % complete, CV = EV − AC, SV = EV − PV, EAC = BAC/CPI, channels = n(n−1)/2, PERT = (O + 4M + P)/6). Because options are designed around sign errors and inverted ratios, the arithmetic must be explicit, not estimated.

Treating the project management plan, the baselines, and the project documents as interchangeable - choosing 'update the project management plan' when the scenario describes a change to a log or register, or the reverse.

The two categories are taught as parallel ITTO lists rather than as a hierarchy, so candidates never learn that plans and baselines are formally controlled while logs, registers, and reports are working documents updated routinely.

What to do instead

Build a two-column sort of the standard artifacts and learn the rule that generates it: anything that is baselined or approved by a governance process lives in the plan; anything the team keeps current day to day (issue log, risk register, assumption log, stakeholder register, lessons learned register) is a project document. Apply the sort to the artifact named in the stem before choosing.

Answering an adaptive or hybrid scenario with predictive reflexes: creating a detailed upfront plan and baseline, sending a change through a change control board, having the project manager decompose work and assign tasks, or producing documentation 'for approval' before any delivery.

Most candidates' first exposure is predictive, so when an adaptive question appears without obvious Agile vocabulary they unconsciously map it onto the waterfall sequence they know best.

What to do instead

Scan the stem for adaptive signals (iterations, sprint, backlog, incremental delivery, empowered team, changing requirements) and, if present, eliminate every option containing baseline, change control board, detailed plan, assign tasks, or documentation-first. Then choose among the remaining options the one that shortens feedback or moves a decision to the team or customer.

Assigning responsibilities to the wrong Agile accountability - the product owner estimating or assigning daily tasks, the Scrum Master prioritizing the backlog or accepting the increment, the team committing the team to scope on the sponsor's behalf - or choosing an option where the project manager directs the team's daily work.

Scrum accountabilities are learned as three names on a slide rather than as distinct decision rights, so under pressure any option with the right vocabulary sounds plausible.

What to do instead

Memorize one line per accountability: product owner owns value and ordering; Scrum Master owns the process and impediment removal (servant leader, no delivery authority); developers own estimation, self-organization, and the increment. Test each option by asking which of those three owns the decision in the stem, and eliminate options that cross the boundary.

Selecting the option that builds, buys, or configures something (a prototype, a feature, a report) in response to a stated business problem, without any prior needs assessment, elicitation, or analysis step.

The stem typically names a stakeholder request or a visible symptom, and the solution-shaped option is the most concrete and satisfying of the four; the analysis options read as delays.

What to do instead

Read the stem for whether the need itself has been established: if the request is unvalidated, the stakeholder set is incomplete, or the problem statement is missing, the correct answer must be an elicitation, analysis, or needs-assessment action. Reserve solution-shaped answers for stems where the need, stakeholders, and acceptance criteria are already documented.

Mixing up verification and validation, or treating elicitation as analysis - for example answering 'confirm the requirement is well-formed and testable' when the question asks whether the solution meets the business need, or recording a single stakeholder's statement as the requirement without reconciling conflicting inputs.

The two pairs are defined in nearly identical language, and both sound like 'checking the work', so candidates match on the word 'confirm' or 'review' rather than on the object being confirmed.

What to do instead

Anchor both distinctions to their objects: verification asks 'did we build the requirement correctly' (requirement quality, traceability, testability); validation asks 'did we build the right thing for the business need' (value, fitness for use). Elicitation collects raw input; analysis models, prioritizes, and reconciles it across stakeholders. Identify the object in the stem first, then choose the matching activity.

Exam requirements can change. Confirm current details with the exam provider.

CAPM practice

200 questions. Each one lists the choices, the correct answer, and an explanation. With JavaScript, this list opens one question at a time. The checker at the top of this page saves progress in this browser when it is available.

  1. Question 1Project Management Fundamentals and Core Concepts

    Which statement defines a project as described in project management fundamentals?

    1. A recurring set of routine activities governed by written standard operating procedures
    2. An ongoing effort that sustains the organization's core business processes indefinitely
    3. A permanent organizational unit responsible for a specialized functional capability
    4. A temporary endeavor undertaken to create a unique product, service, or result Correct answer.

    Explanation

    A project is temporary, has a definite beginning and end, and produces a unique product, service, or result. Repetitive, continuing work is classified as operations rather than as a project.

  2. Question 2Project Management Fundamentals and Core Concepts

    Which statement best distinguishes a program from a portfolio?

    1. A portfolio is run by one project manager, while a program is always run by the project management office
    2. A program groups related projects for shared benefits; a portfolio groups projects, programs, and operations to meet strategic goals Correct answer.
    3. A program is always shorter in total duration than each of the individual projects it contains
    4. A program is a collection of unrelated projects managed independently, while a portfolio is a single large project with a dedicated sponsor

    Explanation

    Programs are groups of related projects and subsidiary activities managed together to obtain benefits not available from managing them individually. Portfolios are collections of projects, programs, and operations selected to meet strategic objectives.

  3. Question 3Project Management Fundamentals and Core Concepts

    What is the primary purpose of the project charter?

    1. It documents the detailed scope, cost, and schedule baselines approved for execution
    2. It lists each work package and names the team members assigned to perform it
    3. It records the lessons learned from a similar past project so the team can reuse them
    4. It formally authorizes the project and gives the project manager authority to apply organizational resources Correct answer.

    Explanation

    The charter is the document that formally authorizes the existence of a project and empowers the project manager to apply organizational resources to its activities. Detailed baselines, work packages, and lessons learned are documented elsewhere.

  4. Question 4Project Management Fundamentals and Core Concepts

    Which statement best describes a project stakeholder?

    1. Only the members of the project team who perform the work on a daily basis
    2. An individual or group that may affect, be affected by, or perceive itself affected by the project Correct answer.
    3. Any person, group, or organization that holds shares or equity in the performing organization or its parent company
    4. Only the sponsor and the customer who provide funding and approve the final product

    Explanation

    A stakeholder is anyone who can influence, be influenced by, or perceive themselves to be influenced by the project, including parties without any equity interest. The definition is deliberately broad so that support and resistance are both identified.

  5. Question 5Project Management Fundamentals and Core Concepts

    Which statement best reflects the relationship among scope, schedule, and cost?

    1. They are independent, so added scope never affects schedule or cost
    2. They are interdependent, so changing one usually requires adjusting another Correct answer.
    3. Schedule always outranks scope and cost when trade-offs are needed
    4. Cost is frozen at charter approval and cannot be revised later

    Explanation

    Scope, schedule, cost, quality, and resources are competing constraints that are linked, so a change in one normally requires a compensating change in at least one other. The relative importance of each is agreed with the sponsor for each project.

  6. Question 6Project Management Fundamentals and Core Concepts

    Which statement correctly distinguishes a deliverable from a milestone?

    1. A milestone produces the project documents, whereas a deliverable marks the end of a phase
    2. A deliverable is a point in time, while a milestone is a tangible output that consumes resources
    3. A deliverable is a tangible output; a milestone is a significant point in time with zero duration Correct answer.
    4. The two terms are identical concepts and can be used interchangeably on a schedule

    Explanation

    A deliverable is any unique and verifiable product, result, or capability to perform a service. A milestone is a significant point or event in the project with no duration and consumes no resources.

  7. Question 7Project Management Fundamentals and Core Concepts

    Which set lists the four values of the PMI Code of Ethics and Professional Conduct?

    1. Transparency, agility, quality, and speed of delivery
    2. Compliance, confidentiality, seniority, and formal authority
    3. Responsibility, respect, fairness, and honesty Correct answer.
    4. Efficiency, competitiveness, loyalty, and personal discipline

    Explanation

    The code is built on responsibility, respect, fairness, and honesty, and it applies to practitioners regardless of the organization or country in which they work. These values translate into mandatory and aspirational standards of conduct.

  8. Question 8Project Management Fundamentals and Core Concepts

    The PMI Talent Triangle describes the three skill areas a project manager should develop. Which are they?

    1. Leadership, negotiation, and status reporting
    2. Planning, executing, and closing processes
    3. Technical, financial, and legal expertise
    4. Ways of working, power skills, and business acumen Correct answer.

    Explanation

    The Talent Triangle identifies ways of working, power skills, and business acumen as the three complementary skill areas that effective project professionals develop. Balancing all three is what makes a practitioner effective across delivery approaches.

  9. Question 9Project Management Fundamentals and Core Concepts

    A project has well-understood requirements, a fixed scope, and a customer who wants a single delivery at the end. Which life cycle is most appropriate?

    1. A hybrid life cycle that blends predictive planning with agile delivery teams
    2. A predictive life cycle with defined sequential phases Correct answer.
    3. An iterative life cycle that refines an unclear scope in repeated cycles
    4. An agile life cycle that releases small increments to the customer frequently

    Explanation

    When scope is well understood and the customer wants one delivery at the end, a predictive approach lets the team plan the work in detail and manage against baselines. Iterative, agile, and hybrid approaches pay off when requirements are uncertain or frequent deliveries are required.

  10. Question 10Project Management Fundamentals and Core Concepts

    What is the primary purpose of a phase gate review?

    1. To replace the project charter with a more detailed execution schedule
    2. To calculate the final cost and schedule variance of the completed project at closure
    3. To assign individual work packages to the team members who will perform them
    4. To decide whether the project should continue into the next phase based on predefined criteria Correct answer.

    Explanation

    A phase gate, or stage gate, is a review at the end of a phase where key stakeholders compare results and performance against pre-agreed criteria. The outcome determines whether the project proceeds, is revised, or is halted.

  11. Question 11Project Management Fundamentals and Core Concepts

    Which document justifies the investment in a project by comparing expected benefits with costs and risks?

    1. The project charter
    2. The business case Correct answer.
    3. The stakeholder engagement plan
    4. The benefits management plan

    Explanation

    The business case provides the rationale for the project and records the estimated costs, benefits, and risks used to justify the investment. It is used by the sponsor and governance body to decide whether to authorize the work through the charter.

  12. Question 12Project Management Fundamentals and Core Concepts

    In a strongly functional organization, who typically controls the project budget and the resources assigned to the work?

    1. A dedicated project coordinator who releases resources between projects
    2. The project management office director in every situation
    3. The project manager, who holds full authority over the team and the budget
    4. The functional managers, with the project manager acting in a coordinating role Correct answer.

    Explanation

    In a functional organization the project work is carried out inside departments, so functional managers control budgets and staff assignments. Any project manager or coordinator has limited authority and mainly facilitates communication.

  13. Question 13Project Management Fundamentals and Core Concepts

    Which statement best characterizes a strong matrix organization?

    1. Authority is shared equally between project and functional managers on every decision
    2. The functional manager controls the budget while the project manager only coordinates
    3. No project manager is assigned and coordination occurs informally among departments
    4. The project manager has considerable authority and often controls the project budget Correct answer.

    Explanation

    In a strong matrix the project manager has greater authority, commonly including budget control and resource negotiation, while functional managers still supply and develop the staff. This shifts the balance of power toward the project.

  14. Question 14Project Management Fundamentals and Core Concepts

    Which type of PMO provides templates, best practices, and training while exercising a low level of control over projects?

    1. A project governance board
    2. A controlling PMO
    3. A supportive PMO Correct answer.
    4. A directive PMO

    Explanation

    A supportive PMO supplies templates, methodologies, training, and access to information on request, with a low degree of control over project work. Controlling and directive PMOs exercise progressively greater oversight.

  15. Question 15Project Management Fundamentals and Core Concepts

    What does tailoring mean in project management?

    1. Removing every process that is not explicitly required by a regulator
    2. Rewriting the organizational strategy so that it aligns with the project goals
    3. Changing the project scope so it matches the personal preferences of the sponsor
    4. Adapting the selected processes and methods to suit the project's context Correct answer.

    Explanation

    Tailoring is the deliberate adaptation of processes, tools, and methods to the size, complexity, risk, and environment of a specific project. It is a judgment-based activity performed within governance constraints, not a free hand to drop controls.

  16. Question 16Project Management Fundamentals and Core Concepts

    Requirements are only broadly known at project start and are refined as more information becomes available. Which concept does this describe?

    1. Fast tracking
    2. Gold plating
    3. Progressive elaboration Correct answer.
    4. Scope creep

    Explanation

    Progressive elaboration means that project details are developed and refined over time as understanding improves. It is expected on most projects and is managed through iterative planning and formal change control.

  17. Question 17Project Management Fundamentals and Core Concepts

    A project manager learns that a newly purchased enterprise project management system is mandatory for all projects in the company. This is best classified as which type of input?

    1. An enterprise environmental factor Correct answer.
    2. An assumption recorded in the business case
    3. An organizational process asset
    4. A component of the project management plan

    Explanation

    Enterprise environmental factors are conditions outside the project team's direct control, such as organizational culture, governance, infrastructure, and company-wide information systems. These influence how the project must be planned and executed.

  18. Question 18Project Management Fundamentals and Core Concepts

    A project leader focuses on removing obstacles for the team and deliberately shifts decision authority to team members. Which leadership style is being demonstrated?

    1. Transactional leadership
    2. Autocratic leadership
    3. Laissez-faire leadership
    4. Servant leadership Correct answer.

    Explanation

    Servant leadership puts the team's needs first, emphasizing growth, removal of impediments, and shared decision authority. It is closely associated with agile delivery but is applicable in any environment.

  19. Question 19Project Management Fundamentals and Core Concepts

    When should lessons learned be captured during a project?

    1. Only after a significant failure has occurred
    2. Only at the very end, during the closing process
    3. Only during the phase gate reviews run by the PMO
    4. Continuously throughout the project, not just at closure Correct answer.

    Explanation

    Lessons learned should be identified and recorded as work proceeds so that the team can adjust current performance and benefit later phases. The lessons learned register is reviewed, updated, and archived as part of closing.

  20. Question 20Project Management Fundamentals and Core Concepts

    How does organizational culture most directly affect a project?

    1. It fixes the project's cost baseline at the time of charter approval
    2. It removes the need for a stakeholder engagement plan
    3. It shapes how teams communicate, make decisions, and respond to risk Correct answer.
    4. It determines the legal requirements that the project must satisfy

    Explanation

    Culture is an enterprise environmental factor that influences communication norms, decision-making, tolerance for risk, and how conflict is handled. Because it is embedded in behavior rather than written down, it often affects project execution more than formal procedures do.

  21. Question 21Project Management Fundamentals and Core Concepts

    How does a directive PMO differ from a supportive PMO?

    1. It directly manages the projects and the project managers report to it Correct answer.
    2. It supplies templates and training on request without controlling projects
    3. It audits projects after they close and publishes the results
    4. It provides occasional informal coaching to project managers only

    Explanation

    A directive PMO takes ownership of the projects it oversees, and project managers assigned to those projects report into the PMO. A supportive PMO instead offers templates, training, and advice with little direct control.

  22. Question 22Project Management Fundamentals and Core Concepts

    Which statement about a benefits management plan is correct?

    1. It is produced during project closure to record the benefits that were actually realized by the customer
    2. It defines when and how benefits are measured and is typically owned outside the project Correct answer.
    3. It replaces the business case once the project charter has been approved by the sponsor
    4. It records only the financial costs that the project will incur over its life cycle

    Explanation

    The benefits management plan specifies the target benefits, the metrics, and the timing for realizing and sustaining them, and it is usually owned by the business rather than the project team. It complements the business case, which establishes the rationale for the investment.

  23. Question 23Project Management Fundamentals and Core Concepts

    A project manager converts raw cost and schedule measurements into a comparison of actual performance against the baseline. What is this output called?

    1. Work performance information Correct answer.
    2. Work performance reports
    3. Work performance data
    4. An approved change request

    Explanation

    Work performance data are the raw observations gathered during execution, and once they are analyzed and contextualized against the baseline they become work performance information. That information is then packaged for stakeholders as work performance reports.

  24. Question 24Project Management Fundamentals and Core Concepts

    Project governance primarily provides which of the following?

    1. The detailed technical design standards that the deliverables must meet
    2. Decision-making authority, policies, and oversight for the project Correct answer.
    3. A substitute authorizing document used when a project charter is unavailable
    4. The daily supervision of the tasks assigned to individual team members

    Explanation

    Governance is the framework within which authority is exercised: it defines decision rights, policies, escalation paths, and oversight of project performance. It aligns the project with organizational strategy without replacing the project manager's day-to-day role.

  25. Question 25Project Management Fundamentals and Core Concepts

    Which statement best reflects how project success should be judged?

    1. Exclusively by whether the project finished on time and within the approved budget baseline
    2. By the achievement of business objectives and stakeholder satisfaction Correct answer.
    3. Only by counting the number of change requests approved by the change control board
    4. By the number of team members who remained assigned until the project was formally closed

    Explanation

    Success is measured by whether the project delivered the intended product and business benefits and met stakeholder expectations, not by cost and schedule performance alone. A project can meet its triple constraint and still fail if the outcome delivers no value.

  26. Question 26Project Management Fundamentals and Core Concepts

    Which characteristic best distinguishes a project from ongoing operations?

    1. It continues indefinitely until the organization changes its strategy.
    2. It is staffed entirely by people from one functional department.
    3. It is temporary and produces a unique product, service, or result. Correct answer.
    4. It repeats the same work every month using an established process.

    Explanation

    A project is a temporary endeavor undertaken to create a unique product, service, or result, and it ends when its objectives are met or it is terminated. Operations are ongoing and repetitive, sustaining the business over time. Staffing patterns and duration of use do not by themselves define a project.

  27. Question 27Project Management Fundamentals and Core Concepts

    A group of related projects and subsidiary programs managed together to obtain benefits that would not be available from managing them separately is called a:

    1. Program Correct answer.
    2. Portfolio
    3. Project management office
    4. Subproject

    Explanation

    A program is a group of related projects, subsidiary programs, and program activities managed in a coordinated manner to obtain benefits not obtainable from managing them individually. A portfolio is a collection of projects, programs, and operations selected to meet strategic objectives. Coordination toward shared benefits is the defining feature of a program.

  28. Question 28Project Management Fundamentals and Core Concepts

    Which statement best describes the sponsor's role on a project?

    1. The sponsor defines detailed task assignments for individual team members.
    2. The sponsor performs the technical work packages assigned to the team.
    3. The sponsor authorizes the project, secures funding, and champions it at the executive level. Correct answer.
    4. The sponsor chairs the change control board on every project without exception.

    Explanation

    The sponsor is the person or group that provides resources and support for the project and is accountable for enabling success. This includes authorizing the project, securing funding, and advocating for it with senior management. Detailed technical and task-level work belongs to the project manager and team.

  29. Question 29Project Management Fundamentals and Core Concepts

    Who should be treated as a stakeholder on a project?

    1. Only end users who will operate the finished product
    2. Only the team members assigned to the work packages
    3. Anyone who can affect or be affected by the project Correct answer.
    4. Only the customer who signs off on the deliverables

    Explanation

    Stakeholders include anyone who can affect, be affected by, or perceive themselves to be affected by a decision, activity, or outcome of the project. This can include internal groups, regulators, suppliers, and community members, not just the customer or users. Narrow definitions cause important interests to be overlooked.

  30. Question 30Project Management Fundamentals and Core Concepts

    Late in a project with a fixed budget and a fixed completion date, a customer requests a significant amount of additional scope. According to the competing-constraints model, what should the project manager do first?

    1. Refuse the request because scope may not change once the project has started.
    2. Record the request and implement it after the project has been closed.
    3. Accept the additional scope and absorb the work within the existing resources.
    4. Evaluate the impact and negotiate a trade-off among scope, schedule, cost, and quality. Correct answer.

    Explanation

    Scope, schedule, cost, and quality are competing constraints, so changing one affects the others. The project manager analyzes the impact and negotiates an acceptable balance with the customer and sponsor before committing. Absorbing extra work without adjusting constraints usually damages quality or morale.

  31. Question 31Project Management Fundamentals and Core Concepts

    How does the project life cycle relate to the product life cycle?

    1. The project life cycle covers the creation of the product, while the product life cycle extends further. Correct answer.
    2. The project life cycle continues for as long as the product generates revenue.
    3. The product life cycle begins only after the project life cycle has ended.
    4. The two cycles cover exactly the same period and contain the same phases.

    Explanation

    The project life cycle consists of the phases from project start to project closure. The product life cycle is usually longer and may include conception, growth, maturity, and decline, potentially spanning many projects. Confusing the two leads to incorrect assumptions about when the project ends.

  32. Question 32Project Management Fundamentals and Core Concepts

    In a work breakdown structure, what is a work package?

    1. The highest WBS level, representing the entire project scope
    2. The lowest WBS level, where cost and duration are estimated Correct answer.
    3. A summary level that aggregates several control accounts
    4. A milestone marking the end of a project phase

    Explanation

    A work package is the lowest level of the WBS, the point at which the work can be estimated, scheduled, monitored, and assigned. Control accounts sit above work packages and aggregate their performance. Milestones are schedule markers, not units of decomposed work.

  33. Question 33Project Management Fundamentals and Core Concepts

    Which of the following is an example of an organizational process asset?

    1. Templates, checklists, and historical cost data from earlier projects Correct answer.
    2. The economic conditions in the region where the project is performed
    3. Government health and safety regulations that apply to the industry
    4. The time-zone difference between the project team and the customer

    Explanation

    Organizational process assets are the internal plans, processes, policies, procedures, and knowledge bases of the performing organization, such as templates and historical data. They are generally under the organization's control and can be updated by it. Regulations, economic conditions, and time zones are external constraints the project manager cannot revise.

  34. Question 34Project Management Fundamentals and Core Concepts

    In a projectized organization, what is the project manager's typical position?

    1. The project manager coordinates work while functional managers control the budget.
    2. The project manager has high to absolute authority over the team and project funds. Correct answer.
    3. The project manager shares authority equally with a functional department head.
    4. The project manager has little authority because staff report to their departments.

    Explanation

    In a projectized structure, staff are assigned to the project and report to the project manager, who has high to absolute authority over resources and the budget. When the project ends, team members are released and seek new assignments. Weak and balanced matrix structures distribute authority differently.

  35. Question 35Project Management Fundamentals and Core Concepts

    Which activity belongs to the Closing process for a project or phase?

    1. Establishing the project charter and confirming the business case
    2. Obtaining formal acceptance of deliverables and releasing project resources Correct answer.
    3. Developing the work breakdown structure and scope baseline
    4. Identifying stakeholders and analyzing their influence

    Explanation

    Closing includes confirming that all work is complete, obtaining formal acceptance of deliverables, archiving project information, and releasing team and other resources. The charter and business case belong to initiation, baselines to planning, and stakeholder identification to initiation and ongoing engagement.

  36. Question 36Project Management Fundamentals and Core Concepts

    Which statement correctly distinguishes an assumption log from an issue log?

    1. The assumption log records problems already occurring, while the issue log records conditions taken as true.
    2. The assumption log records conditions taken as true without proof, while the issue log records problems already affecting the project. Correct answer.
    3. The assumption log is used only for risks that have been formally accepted.
    4. Both documents are optional and are completed only at project closure.

    Explanation

    An assumption log captures assumptions and constraints accepted as true for planning purposes, which must later be validated. An issue log tracks problems or concerns that are currently affecting or may soon affect the project and require resolution. Keeping them separate prevents unvalidated assumptions from being confused with active problems.

  37. Question 37Project Management Fundamentals and Core Concepts

    A project manager needs a practical way to prioritize stakeholders for engagement. Which approach is most appropriate?

    1. Engage only the stakeholders who have signed the project charter.
    2. Plot stakeholders on a power and interest grid and plan engagement accordingly. Correct answer.
    3. Engage every stakeholder with exactly the same information and frequency.
    4. Deal only with stakeholders who raise issues during team meetings.

    Explanation

    Stakeholder analysis commonly classifies stakeholders by power, interest, influence, or impact so that engagement effort matches their needs and potential effect on the project. This allows differentiated communication strategies. A one-size-fits-all approach or reacting only to those who speak up leaves key stakeholders unmanaged.

  38. Question 38Project Management Fundamentals and Core Concepts

    Who typically reviews and decides on changes to project baselines?

    1. The project manager acting alone, without consulting anyone
    2. A change control board with defined decision authority Correct answer.
    3. The functional managers who supply the team members
    4. The customer's legal department in all cases

    Explanation

    Integrated change control routes change requests to the body with defined authority, commonly a change control board whose membership may include the sponsor, project manager, and key stakeholders. The board approves, rejects, or defers changes and communicates decisions. The project manager implements the process but does not unilaterally override baselines.

  39. Question 39Project Management Fundamentals and Core Concepts

    Why is the project manager often described as an integrator?

    1. Because the project manager reports every issue to the sponsor for a decision.
    2. Because the project manager performs the technical work on every deliverable.
    3. Because the project manager coordinates processes and balances competing objectives into one coherent plan. Correct answer.
    4. Because the project manager controls every functional department's budget.

    Explanation

    Integration means unifying the various processes, plans, and competing demands of the project into a single coherent approach. The project manager consolidates information, makes trade-offs, and keeps the team aligned with the charter and stakeholder needs. Delegation of all decisions upward or hands-on technical work are not integration.

  40. Question 40Project Management Fundamentals and Core Concepts

    In a predictive (plan-and-deliver) life cycle, how is planning typically handled?

    1. Most planning is done up front, and the baselines guide execution. Correct answer.
    2. Planning is minimal at the start and occurs mainly at the end of each iteration.
    3. Planning is performed only after the product has been delivered.
    4. Planning is continuous and freely replaces baselines whenever the team prefers.

    Explanation

    Predictive approaches perform the bulk of planning before execution begins and then manage against approved baselines. Changes are handled through formal change control rather than by rewriting baselines at will. Iterative approaches, by contrast, plan in repeated cycles.

  41. Question 41Project Management Fundamentals and Core Concepts

    An issue arises that is beyond the project manager's authority and affects the project's funding. What is the appropriate action?

    1. Change the funding baseline without informing anyone.
    2. Cancel the project immediately to avoid further cost.
    3. Raise the issue through the established governance path to the sponsor or steering body. Correct answer.
    4. Ignore the issue because it is outside the project manager's control.

    Explanation

    Project governance defines the escalation paths and decision rights above the project manager's authority level. Issues beyond that authority should be escalated promptly to the sponsor or steering committee with impact information. Unilateral cancellation or silent baseline changes bypass governance.

  42. Question 42Project Management Fundamentals and Core Concepts

    Which statement is true of the project management plan once it has been baselined?

    1. Changes to baselines follow integrated change control and are approved before implementation. Correct answer.
    2. It is replaced by the project charter during project closure.
    3. It may be modified at any time by any team member who finds it convenient.
    4. It is discarded once execution begins because it is no longer needed.

    Explanation

    The project management plan is a living document, but once baselined, changes to its baselines go through integrated change control and require approval before being implemented. It remains the primary reference for executing, monitoring, and controlling the work. Uncontrolled edits destroy its value as a baseline.

  43. Question 43Project Management Fundamentals and Core Concepts

    A team has moved past its initial conflict and is now establishing norms and working cooperatively. Which stage of team development is this?

    1. Storming
    2. Forming
    3. Adjourning
    4. Norming Correct answer.

    Explanation

    In Tuckman's model, teams move through forming, storming, norming, performing, and adjourning. Norming is the stage in which agreement on roles and working methods emerges and cooperation increases. Conflict belongs to storming, and disbanding belongs to adjourning.

  44. Question 44Project Management Fundamentals and Core Concepts

    A project has a fixed regulatory submission date and a detailed scope that cannot change, but the customer wants demonstrations every few weeks to refine usability. Which development approach fits best?

    1. A purely predictive approach that delivers only once, at the end
    2. An approach in which planning is postponed until after the submission date
    3. A hybrid approach with predictive planning and iterative delivery of components Correct answer.
    4. A purely adaptive approach with no baselined scope

    Explanation

    When part of the work must follow a fixed, formally controlled path but other parts benefit from frequent feedback, a hybrid approach combines predictive planning with iterative delivery. Choosing a single extreme ignores either the regulatory constraint or the customer's need for early visibility. The approach should follow the nature of the work and its constraints.

  45. Question 45Project Management Fundamentals and Core Concepts

    A project manager on one continent leads a team distributed across three continents, and local labor laws limit working hours in two of the countries. How should these conditions be classified?

    1. As organizational process assets that the project manager may revise
    2. As enterprise environmental factors that constrain how the project is planned and executed Correct answer.
    3. As project assumptions that may be ignored if the schedule slips
    4. As lessons learned that apply only to future projects

    Explanation

    Enterprise environmental factors are conditions outside the immediate control of the project team, such as regulations, time zones, and market conditions, that influence how the project is managed. Labor laws cannot be revised by the project manager, so the plan must accommodate them. Process assets, in contrast, are internal and adjustable.

  46. Question 46Project Management Fundamentals and Core Concepts

    Organizational project management (OPM) is best described as:

    1. A single methodology mandatory for all projects in the organization
    2. A scheduling application used by the project management office
    3. A framework aligning portfolio, program, and project practices with strategy Correct answer.
    4. An individual credential held by a project manager

    Explanation

    OPM is a framework in which portfolio, program, and project management practices are integrated with organizational enablers to achieve strategic objectives and deliver value. It is broader than any tool, methodology, or personal certification. Its purpose is strategic alignment across levels of work.

  47. Question 47Project Management Fundamentals and Core Concepts

    A senior engineer's troubleshooting know-how exists only in her experience and is documented nowhere. Which action best supports knowledge management?

    1. Replace her with a documented procedure as soon as possible
    2. Store all project files in a shared folder and require weekly uploads
    3. Publish her job title and years of experience in the project wiki
    4. Pair her with junior staff and use coaching and communities of practice Correct answer.

    Explanation

    Knowledge management addresses tacit knowledge, which is experience-based and difficult to codify, through interaction such as coaching, mentoring, and communities of practice. Information management handles explicit knowledge stored in documents and repositories. Sharing through people-to-people interaction is what transfers undocumented know-how.

  48. Question 48Project Management Fundamentals and Core Concepts

    In the value delivery system, what is the primary role of projects?

    1. To maintain existing business operations at a steady state
    2. To convert organizational strategy into tangible outcomes and benefits for stakeholders Correct answer.
    3. To produce financial statements for external reporting
    4. To replace portfolio management by selecting which work is funded

    Explanation

    Organizations create value by aligning portfolios, programs, and projects with strategy, with projects producing the outputs that lead to outcomes and benefits. Project selection and prioritization remain portfolio responsibilities. Maintaining the steady state is the role of operations.

  49. Question 49Project Management Fundamentals and Core Concepts

    Which statement correctly distinguishes the focus of project, program, and portfolio managers?

    1. Project managers focus on benefits, program managers on outputs, and portfolio managers on team development.
    2. All three roles focus on delivering a single product on time and within budget.
    3. Portfolio managers supervise daily tasks, project managers set strategy, and program managers approve charters.
    4. Projects deliver outputs, programs realize benefits from related projects, and portfolios select and prioritize the right work. Correct answer.

    Explanation

    Project managers deliver specified outputs within constraints, program managers coordinate related projects to realize benefits, and portfolio managers select and prioritize the mix of work that best supports strategy. Each level has a distinct scope and success measure. Confusing the levels leads to mismatched accountability.

  50. Question 50Project Management Fundamentals and Core Concepts

    Which statement best describes a project?

    1. A temporary endeavor that creates a unique product, service, or result Correct answer.
    2. An ongoing effort that maintains consistent organizational operations
    3. A repeating cycle of production activities performed by a functional unit
    4. A permanent organizational unit formed to standardize recurring work

    Explanation

    A project is defined by two features: it is temporary, meaning it has a defined beginning and end, and it creates a unique product, service, or result. Work that continues indefinitely to sustain the business is operations, not a project.

  51. Question 51Project Management Fundamentals and Core Concepts

    According to the PMI talent triangle, which three skill areas should a project professional develop?

    1. Leadership, governance, and regulatory compliance oversight
    2. Scope management, schedule management, and cost management
    3. Ways of working, power skills, and business acumen Correct answer.
    4. Technical expertise, functional specialization, and operational mastery

    Explanation

    The PMI talent triangle groups professional development into ways of working (technical project management approaches), power skills (leadership and interpersonal abilities), and business acumen (understanding the organization and its environment). It is a development model rather than a list of project constraints or governance duties.

  52. Question 52Project Management Fundamentals and Core Concepts

    What is the primary function of the project charter?

    1. It records the detailed schedule baseline against which progress is measured.
    2. It lists every stakeholder's contact information for communication planning.
    3. It documents the approved scope, schedule, and cost baselines for the project team to follow.
    4. It formally authorizes the project and links it to the organization's strategic objectives. Correct answer.

    Explanation

    The charter formally authorizes the existence of the project and gives the project manager authority to apply organizational resources to project activities. It also connects the project to the organization's strategic objectives, but it does not contain baselines.

  53. Question 53Project Management Fundamentals and Core Concepts

    Which characteristic distinguishes a project from ongoing operations?

    1. It is planned and monitored using documented processes.
    2. It is temporary and produces a unique result. Correct answer.
    3. It produces value for the sponsoring organization.
    4. It is performed by people with specialized skills.

    Explanation

    Projects are temporary endeavors undertaken to create a unique product, service, or result, and they end when their objectives are achieved or the project is terminated. Operations are ongoing and repetitive, even though both may use skilled people, documented processes, and deliver value.

  54. Question 54Project Management Fundamentals and Core Concepts

    Which best describes the project sponsor's role?

    1. Manages the team's day-to-day activities and resolves task-level conflicts
    2. Provides resources and champions the project at senior levels Correct answer.
    3. Audits the project's financial records and certifies compliance with accounting rules
    4. Performs the technical work and reports task status to the project manager

    Explanation

    The sponsor is the person or group that authorizes the project, provides funding and resources, and advocates for it within the organization. Day-to-day execution and technical work belong to the project manager and the project team.

  55. Question 55Project Management Fundamentals and Core Concepts

    Who is a project stakeholder?

    1. Any individual, group, or organization that can affect or be affected by the project Correct answer.
    2. Only the customers who receive and formally accept the final product of the project
    3. Only the executives who approve funding and receive status reports from the project manager
    4. Only the team members who are assigned full-time work on the project's deliverables

    Explanation

    A stakeholder is any individual, group, or organization that can affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of the project. This broad definition includes internal and external parties, and even those who only perceive an impact.

  56. Question 56Project Management Fundamentals and Core Concepts

    What is a deliverable?

    1. A formal change request submitted to the change control board
    2. A documented approach for executing the work of the project
    3. An activity scheduled in the schedule baseline and assigned to a team member
    4. Any unique and verifiable product, result, or capability produced to complete a phase Correct answer.

    Explanation

    A deliverable is any unique and verifiable product, result, or capability that must be produced to complete a phase or the project. Deliverables are outputs of work, whereas activities are the work itself.

  57. Question 57Project Management Fundamentals and Core Concepts

    A PMO supplies templates and requires projects to use them, and it audits projects for compliance with the organization's methodology, but it does not manage the projects itself. Which PMO type does this describe?

    1. Supportive
    2. Controlling Correct answer.
    3. Directive
    4. Consulting

    Explanation

    A controlling PMO provides support and templates while also requiring compliance with adopted frameworks, methodologies, and templates, typically through audits. It stops short of directly managing the projects, which is what a directive PMO does.

  58. Question 58Project Management Fundamentals and Core Concepts

    In a weak matrix organization, what is the project manager's typical role?

    1. A senior leader who controls the project budget and assigns team members directly
    2. A coordinator or expeditor with limited authority over staff and budget Correct answer.
    3. A dedicated manager with full authority over resources drawn from other departments
    4. A functional supervisor who manages the team's technical work and performance reviews

    Explanation

    In a weak matrix, the functional manager retains most authority over resources and budget, and the project manager acts more as a coordinator or expeditor who tracks progress and communicates. Authority over staff and funding increases as the organization moves toward a strong matrix or projectized structure.

  59. Question 59Project Management Fundamentals and Core Concepts

    What is the primary purpose of project governance?

    1. To provide decision-making structures, authority, and oversight aligned to organizational objectives Correct answer.
    2. To document the detailed requirements the product must satisfy before release to customers
    3. To calculate earned value metrics and report cost variances to the finance department monthly
    4. To establish the technical standards and product specifications the development team must follow

    Explanation

    Project governance is the framework of rules, practices, and decision-making structures that determines who has authority, how decisions are escalated, and how the project stays aligned with organizational strategy. Technical standards, requirements, and metric reporting are tools used within that framework rather than the framework itself.

  60. Question 60Project Management Fundamentals and Core Concepts

    What is the purpose of a phase gate or kill point?

    1. To confirm that every stakeholder has signed the final product acceptance documentation
    2. To record the lessons learned by the team at the very end of the project
    3. To authorize the release of funds for the entire remaining project budget
    4. To review progress and decide whether to continue, revise, or terminate the project or phase Correct answer.

    Explanation

    A phase gate is a review at the end of a phase where stakeholders evaluate progress, performance, and the business case to decide whether to continue, change direction, or stop the work. This decision point is why phase-end reviews are also called kill points.

  61. Question 61Project Management Fundamentals and Core Concepts

    Which of the following is an example of an enterprise environmental factor?

    1. Marketplace conditions and the organization's existing information technology systems Correct answer.
    2. Historical cost and duration data from similar projects stored in the organization's archive
    3. A lessons learned database and estimating worksheets maintained by the project management office
    4. The organization's standard template for recording and rating project risks

    Explanation

    Enterprise environmental factors are conditions outside the project team's control that influence the project, such as market conditions, organizational culture, and existing infrastructure and systems. Templates, historical data, and lessons learned repositories are organizational process assets because they are internal knowledge the team can adapt.

  62. Question 62Project Management Fundamentals and Core Concepts

    Which statement correctly distinguishes work performance data from work performance information?

    1. Data are prepared for the sponsor, while information is used only by the project team internally
    2. Data describe the project's benefits, while information describes the status of deliverables
    3. Data are raw observations, while information is data analyzed in context against the plan Correct answer.
    4. Data are produced at project closure, while information is produced during planning stages only

    Explanation

    Work performance data are the raw observations and measurements gathered during execution, such as actual costs and completion status. When that data are analyzed and compared with the plan, they become work performance information that supports decision-making.

  63. Question 63Project Management Fundamentals and Core Concepts

    What is the most effective way to ensure knowledge gained on a project is available to future projects?

    1. Capture it in the lessons learned register only at the very end of the project
    2. Rely on individual team members to remember and share the knowledge informally later
    3. Record it in the cost baseline and schedule so it can be audited by the finance department
    4. Capture knowledge throughout the project and store it in an accessible organizational repository Correct answer.

    Explanation

    Knowledge management works best when insights are identified and recorded as they occur, then stored in an accessible organizational knowledge base such as a lessons learned repository. Capturing only at closure risks losing insights as team members leave the project.

  64. Question 64Project Management Fundamentals and Core Concepts

    Which of the following is a project document rather than a component of the project management plan?

    1. The scope baseline
    2. The stakeholder engagement plan
    3. The issue log Correct answer.
    4. The schedule baseline

    Explanation

    Project documents are created and maintained to support the project but are not part of the project management plan; the issue log is one example. Baselines and subsidiary plans, such as the stakeholder engagement plan, are components of the project management plan.

  65. Question 65Project Management Fundamentals and Core Concepts

    What does the benefits management plan primarily describe?

    1. The detailed technical specifications the product must meet before the customer will accept it
    2. The schedule of funding releases and payment milestones agreed with the finance department
    3. The roles and responsibilities assigned to each project team member during project execution
    4. How and when the project's benefits will be delivered and measured, and who owns them Correct answer.

    Explanation

    The benefits management plan defines the target benefits, the metrics and timing for realizing them, and the person accountable for each benefit. It is developed early, often alongside the business case, and guides benefit realization after the project delivers.

  66. Question 66Project Management Fundamentals and Core Concepts

    A project team is highly skilled and self-organizing. Which leadership approach is most appropriate?

    1. Directive leadership that assigns each task and reviews every decision the team makes
    2. Laissez-faire leadership that leaves the team without any agreed goals or boundaries
    3. Autocratic leadership that centralizes all technical decisions in the project manager
    4. Servant leadership that removes impediments and lets the team make decisions Correct answer.

    Explanation

    Self-organizing teams perform best with servant leadership, in which the project manager focuses on removing obstacles, providing resources, and enabling the team to decide how to do the work. Directive or autocratic styles suppress the team's autonomy, while abandoning all goals and boundaries is not leadership.

  67. Question 67Project Management Fundamentals and Core Concepts

    Which statement correctly distinguishes a project phase from a process group?

    1. A phase produces a deliverable, whereas process groups are management activities repeated within each phase Correct answer.
    2. A phase is a management activity performed by the sponsor, whereas process groups are product deliverables
    3. A phase is repeated in every process group, whereas process groups occur only once at project start
    4. A phase applies only to predictive projects, whereas process groups apply only to adaptive projects

    Explanation

    Phases are segments of the project life cycle that typically end with a deliverable and a review, while process groups are logical groupings of management activities that recur within each phase. The two concepts are different lenses on the same work and apply regardless of the development approach.

  68. Question 68Project Management Fundamentals and Core Concepts

    A project has unclear and evolving requirements, a need for frequent user feedback, and a low cost of change. Which development approach fits best?

    1. A predictive approach in which a detailed scope baseline is approved before work begins
    2. A plan-driven approach in which all changes must pass through a formal change control board
    3. An adaptive, iterative approach that delivers increments and incorporates feedback Correct answer.
    4. A phased approach that delivers the complete product in one release at the project's end

    Explanation

    When requirements are uncertain and change is inexpensive, an adaptive or iterative approach lets the team deliver increments, gather feedback, and adjust course. Predictive, plan-driven approaches suit stable, well-understood scope where change is costly.

  69. Question 69Project Management Fundamentals and Core Concepts

    Which statement correctly distinguishes product scope from project scope?

    1. Product scope covers the features and functions of the product; project scope covers the work to deliver it Correct answer.
    2. Product scope is approved by the sponsor; project scope is approved by the receiving customer
    3. Product scope applies only to physical goods; project scope applies only to services and results
    4. Product scope covers the work to deliver the product; project scope covers the product's features and functions

    Explanation

    Product scope defines the features and functions that characterize the product, service, or result, while project scope defines the work required to deliver that product. Completion of project scope is measured against the project management plan, whereas completion of product scope is measured against product requirements.

  70. Question 70Project Management Fundamentals and Core Concepts

    A project is completed on schedule, within budget, and with formally accepted deliverables, yet the sponsor considers it unsuccessful. Which explanation is most likely?

    1. The expected business benefits were not realized once the deliverables were in use Correct answer.
    2. The project's phase gates were reviewed by the project management office instead of the sponsor
    3. The project team members were released before the final performance report was distributed
    4. The project closure activities were completed before the lessons learned were documented

    Explanation

    Success is judged by whether the project achieved its intended business benefits and objectives, not only by conformance to schedule and budget. If the product is accepted but the expected outcomes fail to materialize, stakeholders reasonably view the project as unsuccessful.

  71. Question 71Project Management Fundamentals and Core Concepts

    A project manager plans to overlap phases instead of running them sequentially in order to shorten the schedule. What is the primary consequence of this choice?

    1. The project's total cost decreases because significantly fewer resources are needed overall
    2. Formal phase gate reviews become unnecessary because work now proceeds without interruption
    3. Lessons learned are captured earlier, which reduces the risk carried into subsequent phases
    4. Work on the next phase begins with incomplete information, increasing the risk of rework Correct answer.

    Explanation

    Overlapping phases, sometimes called fast tracking, compresses the schedule by starting later work before earlier work is fully complete. The trade-off is that downstream work relies on incomplete inputs, which raises the likelihood of rework and cost growth.

  72. Question 72Project Management Fundamentals and Core Concepts

    A team is building a new customer booking system. The charter contains only high-level product requirements, and detailed functionality is defined incrementally as prototypes are reviewed with users throughout the project. Which concept best accounts for this way of defining the product?

    1. Scope creep
    2. Progressive elaboration Correct answer.
    3. Gold plating
    4. Configuration management

    Explanation

    Progressive elaboration is the iterative process of developing details as more information and better estimates become available, which is expected when requirements begin at a high level and are refined over the life cycle. It is a planned, approved refinement rather than uncontrolled expansion of scope. Gold plating and scope creep both refer to unapproved additions, and configuration management controls versions of deliverables rather than developing requirements.

  73. Question 73Predictive, Plan-Based Methodologies

    When is a predictive, plan-based project approach most appropriate?

    1. When the scope is expected to change frequently throughout delivery
    2. When requirements are well understood and can be baselined early Correct answer.
    3. When the deliverable must be released incrementally in short iterations
    4. When the team is co-located and customer feedback is continuously available

    Explanation

    Predictive approaches rely on a detailed upfront definition of scope so that baselines for scope, schedule, and cost can be established and controlled. They work best when requirements are stable, the product is well understood, and change is expected to be limited. Highly volatile or emergent requirements are better served by adaptive approaches.

  74. Question 74Predictive, Plan-Based Methodologies

    A project charter is primarily used to:

    1. document the detailed technical design of the product being built
    2. define acceptance criteria for each individual work package
    3. formally authorize the project and empower the project manager to apply organizational resources Correct answer.
    4. record approved changes to the project baselines

    Explanation

    The charter is the document that formally recognizes the existence of a project and gives the project manager authority to commit organizational resources to it. It contains high-level information such as purpose, objectives, and key stakeholders, not detailed technical or work-package-level content.

  75. Question 75Predictive, Plan-Based Methodologies

    In a work breakdown structure, the lowest level of decomposition is called a:

    1. control account
    2. work package Correct answer.
    3. planning package
    4. milestone

    Explanation

    A WBS is decomposed until the deliverables at the bottom can be reliably estimated and managed; those bottom elements are work packages. Control accounts sit above work packages and are used for management and performance measurement. A planning package is a WBS element whose work is not yet decomposed in detail.

  76. Question 76Predictive, Plan-Based Methodologies

    Which set of documents makes up the scope baseline?

    1. Project scope statement, WBS, and WBS dictionary Correct answer.
    2. Scope management plan, activity list, and schedule baseline
    3. Project charter, requirements documentation, and requirements traceability matrix
    4. Requirements traceability matrix, WBS, and project scope statement

    Explanation

    The scope baseline is a component of the project management plan consisting of the approved project scope statement, the WBS, and the WBS dictionary. Together these define what is included and excluded and how the work is decomposed. The scope management plan describes how scope will be managed but is not part of the baseline itself.

  77. Question 77Predictive, Plan-Based Methodologies

    The critical path in a project schedule network diagram is best described as the:

    1. longest path through the network, which determines the shortest possible project duration Correct answer.
    2. path containing the greatest number of activities
    3. path with the highest total cost of its activities
    4. path that consumes the largest number of resources at any point in time

    Explanation

    The critical path is the sequence of activities with the longest total duration from start to finish, and therefore it sets the shortest time in which the project can be completed. Activities on the critical path have zero or negative total float, so any delay to them delays the project finish.

  78. Question 78Predictive, Plan-Based Methodologies

    Where are lessons learned captured during a predictive project stored so that future projects can benefit from them?

    1. In the issue log, so they can be closed at each phase gate
    2. In the risk register, so they can be tracked as threats
    3. In the project charter, so the sponsor can approve them
    4. In the organizational process assets, such as a lessons-learned repository Correct answer.

    Explanation

    Lessons learned are updates to organizational process assets and are meant to be archived in a repository that other projects and the performing organization can consult. They are gathered throughout the project, not only at closure, and are not a project-authorization or risk-tracking document.

  79. Question 79Predictive, Plan-Based Methodologies

    The primary purpose of a phase gate or stage gate review is to:

    1. rebaseline the schedule at the end of each reporting period
    2. reassign team members to a new project before release
    3. collect final customer acceptance signatures for the entire project
    4. confirm that the phase's deliverables meet exit criteria before authorizing the next phase Correct answer.

    Explanation

    A phase gate is a governance control point at the end of a phase where deliverables and performance are reviewed against exit criteria. Only when the criteria are met is the project authorized to proceed into the next phase. This limits risk by preventing work from advancing on an unsound foundation.

  80. Question 80Predictive, Plan-Based Methodologies

    In a RACI matrix, how many people should be accountable for a given activity?

    1. At least two, to avoid a single point of failure
    2. One for each deliverable the activity produces
    3. Exactly one Correct answer.
    4. As many as are consulted on the activity

    Explanation

    The accountable role owns the outcome and carries decision authority, so only one person should hold it for any activity. Multiple accountable parties create ambiguity about who decides and who answers for results. Responsible, consulted, and informed roles may be shared by several people.

  81. Question 81Predictive, Plan-Based Methodologies

    A team member suggests a small addition to a component that would improve usability. The project is on a tight schedule. What should the project manager do first?

    1. Log the request for a future release and inform the sponsor after implementation
    2. Evaluate the request's impact on scope, schedule, cost, quality, and risk before a decision is made Correct answer.
    3. Reject the request because the baselines may never be changed
    4. Approve the addition because it is small and improves the product

    Explanation

    Every change request follows the perform integrated change control process, which begins with assessing impact across all knowledge areas. Only after the impact is understood can the request be approved, deferred, or rejected by the appropriate authority. Approving without assessment undermines the baselines and the governance process.

  82. Question 82Predictive, Plan-Based Methodologies

    A project has an earned value of $80,000 and an actual cost of $100,000. What does the cost performance index tell the project manager?

    1. The project is performing exactly as planned on cost
    2. The project is under budget and should release contingency reserve
    3. The project is over budget, earning $0.80 of value for every dollar spent Correct answer.
    4. The project is ahead of schedule

    Explanation

    The cost performance index is earned value divided by actual cost, which here is 0.80. A CPI below 1.0 means the project is getting less value than planned for each dollar spent, so it is over budget. CPI measures cost efficiency only and says nothing about schedule performance.

  83. Question 83Predictive, Plan-Based Methodologies

    A project manager overlaps two sequential critical path activities so they run in parallel in order to shorten the schedule. This technique is known as:

    1. rolling wave planning
    2. crashing
    3. resource smoothing
    4. fast tracking Correct answer.

    Explanation

    Fast tracking compresses the schedule by performing activities in parallel that were originally planned in sequence. It usually adds risk because of increased coordination and rework potential. Crashing instead shortens duration by adding resources, which typically adds cost.

  84. Question 84Predictive, Plan-Based Methodologies

    An identified risk with a documented probability and impact has been accepted actively. If the risk occurs, which funds should pay for the response?

    1. The project funding requirement, which bundles all reserves together
    2. Management reserve, held by the sponsor for unknown unknowns
    3. The contingency reserve, which is set aside for identified risks Correct answer.
    4. The quality cost budget allocated for prevention activities

    Explanation

    Contingency reserves are included in the cost baseline to cover accepted, identified risks with known probability and impact. Management reserve sits above the cost baseline and is used for unanticipated work outside the approved scope baseline. Reserves are drawn from the matching category based on whether the risk was identified.

  85. Question 85Predictive, Plan-Based Methodologies

    An activity has an early start of day 6 and a duration of 4 days, giving an early finish of day 10. Its late finish is day 13. What is the activity's total float?

    1. 3 days Correct answer.
    2. 1 day
    3. 0 days
    4. 7 days

    Explanation

    Total float equals late finish minus early finish, which here is 13 minus 10, or 3 days. This means the activity can slip up to 3 days without delaying the project finish date. Float of zero would indicate a critical activity.

  86. Question 86Predictive, Plan-Based Methodologies

    A team must finish writing the user manual before the training materials can be developed. Which logical relationship does this represent?

    1. Start-to-finish
    2. Finish-to-finish
    3. Start-to-start
    4. Finish-to-start Correct answer.

    Explanation

    Finish-to-start is the relationship in which a successor activity cannot begin until the predecessor activity has finished. It is the most common dependency type in schedule networks. The other types allow the successor to start or finish relative to the predecessor's start or finish instead.

  87. Question 87Predictive, Plan-Based Methodologies

    Which of the following is an internal failure cost?

    1. Conducting a design review before coding begins
    2. Reworking defective components discovered during testing Correct answer.
    3. Training the team on the new quality standard
    4. Handling customer complaints after the product is released

    Explanation

    Cost of quality divides into prevention, appraisal, and failure costs, with failure split into internal and external. Internal failure costs arise when defects are found before delivery, such as rework or scrap during testing. External failure costs occur after delivery, such as warranty work and complaint handling.

  88. Question 88Predictive, Plan-Based Methodologies

    The scope of a procurement is well defined and the buyer wants price certainty. Which contract type is most suitable?

    1. Cost plus percentage of cost
    2. Cost plus incentive fee
    3. Firm fixed price Correct answer.
    4. Time and materials

    Explanation

    A firm fixed price contract sets a total price for the defined scope, placing cost risk on the seller and giving the buyer price certainty. It is appropriate only when requirements are clear enough to be priced. Cost-reimbursable and time-and-materials arrangements are used when scope is uncertain and cost risk must be shared.

  89. Question 89Predictive, Plan-Based Methodologies

    A construction project team purchases an insurance policy to cover potential storm damage at the site. Which risk response strategy is being used?

    1. Accept
    2. Avoid
    3. Transfer Correct answer.
    4. Mitigate

    Explanation

    Transfer shifts the financial consequences of a threat to a third party, typically through insurance, warranties, or fixed price contracts. The risk itself still exists; only the ownership of its impact moves. Avoidance would require changing the plan to eliminate the exposure entirely.

  90. Question 90Predictive, Plan-Based Methodologies

    On a power/interest grid, how should a stakeholder with high power and high interest be managed?

    1. Keep informed with routine status reports only
    2. Keep satisfied by meeting informational needs only
    3. Monitor with minimal effort
    4. Manage closely and engage actively in decisions Correct answer.

    Explanation

    Stakeholders who hold both high power and high interest can strongly influence the project and care deeply about outcomes, so they require close, ongoing engagement. Involving them in key decisions reduces the likelihood of late resistance. Low-power, low-interest stakeholders are the ones who are simply monitored.

  91. Question 91Predictive, Plan-Based Methodologies

    What primarily determines the appropriate communication methods and frequency for a project?

    1. The stakeholders' information needs and the project's organizational and technical environment Correct answer.
    2. The project manager's personal reporting preferences
    3. The organization's standard templates for meeting minutes
    4. The number of team members available at each site

    Explanation

    Communication planning analyzes who needs what information, when, in what format, and with what level of detail, then matches that to available technology and the organizational setting. The communication management plan is built from that analysis. Templates and personal preferences are implementation details, not the basis for requirements.

  92. Question 92Predictive, Plan-Based Methodologies

    Over several weeks, a sponsor verbally requests a series of small additions that are never documented or approved, and the baselines are not updated. This situation is best described as:

    1. value engineering
    2. configuration management
    3. scope creep Correct answer.
    4. progressive elaboration

    Explanation

    Scope creep is the uncontrolled expansion of scope without adjustment to time, cost, and resources, typically arriving through informal requests. Because the additions were never documented or approved, the baselines no longer reflect the work being performed. Progressive elaboration and configuration management are legitimate, controlled processes.

  93. Question 93Predictive, Plan-Based Methodologies

    A project has a budget at completion of $500,000, earned value of $200,000, and actual cost of $250,000. Assuming current cost performance continues, what is the estimate at completion?

    1. $700,000
    2. $500,000
    3. $625,000 Correct answer.
    4. $450,000

    Explanation

    The cost performance index is 200,000 divided by 250,000, or 0.80. When current performance is expected to continue, estimate at completion equals budget at completion divided by CPI, which is 500,000 divided by 0.80, or $625,000. The variance arises because the project is spending more than it is earning.

  94. Question 94Predictive, Plan-Based Methodologies

    A network contains three paths: A-B-C at 12 days, A-D-E at 15 days, and A-D-F at 11 days. What is the project duration and where is float available?

    1. 11 days, with float on all three paths
    2. 12 days, with float available on A-D-E
    3. 38 days, the sum of all path durations
    4. 15 days, with float available on A-B-C and A-D-F Correct answer.

    Explanation

    Project duration is set by the longest path, which is A-D-E at 15 days and is therefore critical with no float. Paths A-B-C and A-D-F are shorter and have float equal to their difference from the critical path, 3 days and 4 days respectively. Path durations are never summed, since the paths run in parallel.

  95. Question 95Predictive, Plan-Based Methodologies

    How does resource leveling differ from resource smoothing?

    1. Smoothing is performed only after the project has been formally closed
    2. Leveling may extend the schedule to resolve over-allocation, while smoothing adjusts activities within existing float Correct answer.
    3. Leveling applies only to material resources, while smoothing applies to people
    4. Leveling keeps the end date fixed, while smoothing may extend it

    Explanation

    Resource leveling is used when resource demand exceeds supply and may change the critical path or extend the completion date to balance demand. Resource smoothing adjusts activities within their available float so the end date is not affected. The choice depends on whether the schedule date or the resource limit is the binding constraint.

  96. Question 96Predictive, Plan-Based Methodologies

    On a control chart for a repetitive process, seven consecutive data points fall on the same side of the mean. What does this indicate?

    1. The specification limits have been set too wide
    2. The process is in statistical control and requires no action
    3. The measuring instrument is faulty, so the data should be discarded
    4. A non-random pattern exists, suggesting an assignable cause that should be investigated Correct answer.

    Explanation

    Control charts use rules such as the rule of seven to detect non-random variation from special or assignable causes. Seven consecutive points on one side of the mean signal that the process has shifted, even if every point lies inside the control limits. The process should be investigated and corrected rather than assumed stable.

  97. Question 97Predictive, Plan-Based Methodologies

    A regulated project has fixed, well-documented requirements and mandatory stage-gate approvals. The team proposes delivering in short iterative cycles instead. What is the most appropriate course of action?

    1. Eliminate the stage gates because they add no value in regulated environments
    2. Defer all delivery until every requirement is finalized and approved at the very end
    3. Retain the predictive approach with its mandated gates and tailor in iterative practices only where governance permits Correct answer.
    4. Adopt a fully adaptive approach because iterations deliver value sooner

    Explanation

    Tailoring means selecting and adapting methods to the project's environment, including regulatory constraints and required governance. Where gates are mandatory and requirements are stable, a predictive lifecycle remains appropriate, with iterative techniques adopted inside it only to the extent governance allows. Method choices must respect the constraints rather than ignore them.

  98. Question 98Predictive, Plan-Based Methodologies

    In a work breakdown structure, which component sits at the lowest level and is used to estimate cost and duration?

    1. A planning package
    2. A work package Correct answer.
    3. An activity
    4. A control account

    Explanation

    The work breakdown structure is decomposed until the lowest level, the work package, which is small enough to estimate cost and duration reliably and to assign to a single owner. Activities are then identified from within work packages during schedule development.

  99. Question 99Predictive, Plan-Based Methodologies

    Which document formally authorizes the existence of a project and gives the project manager authority to apply organizational resources to it?

    1. The stakeholder register
    2. The project charter Correct answer.
    3. The benefits management plan
    4. The project management plan

    Explanation

    The project charter is issued by the sponsor and formally initiates the project, names the project manager, and conveys authority to commit organizational resources. The project management plan is developed later to describe how the work will be executed and controlled.

  100. Question 100Predictive, Plan-Based Methodologies

    In which organizational structure does the project manager hold the greatest level of authority over project resources?

    1. Balanced matrix organization
    2. Functional organization
    3. Weak matrix organization
    4. Projectized organization Correct answer.

    Explanation

    In a projectized organization the project manager has full authority over the project team and resources, and team members usually report directly to the project manager. Authority decreases progressively through the balanced matrix, weak matrix, and functional structures.

  101. Question 101Predictive, Plan-Based Methodologies

    A project manager must produce a cost estimate quickly, only high-level scope is known, and several comparable projects exist in the organization's records. Which estimating technique fits best?

    1. Analogous estimating Correct answer.
    2. Three-point estimating
    3. Parametric estimating
    4. Bottom-up estimating

    Explanation

    Analogous estimating uses historical data from similar past projects to estimate the current project, so it is fast and inexpensive but generally less accurate. It is most useful when detailed information is scarce and comparable projects are available.

  102. Question 102Predictive, Plan-Based Methodologies

    Which tool links each product requirement to its source and to the deliverables and test cases that satisfy it?

    1. Requirements traceability matrix Correct answer.
    2. Stakeholder engagement assessment matrix
    3. Scope management plan
    4. Work breakdown structure

    Explanation

    The requirements traceability matrix records each requirement's origin and traces it forward to the deliverables and test activities that fulfill it, helping confirm that approved scope is delivered. This supports scope validation and change impact analysis.

  103. Question 103Predictive, Plan-Based Methodologies

    An 18-month predictive project has well-defined near-term deliverables but only high-level definition for the later phases. Which planning approach is most appropriate?

    1. Deferring all detailed planning until the design documentation is complete
    2. Rolling wave planning, detailing near-term work while keeping later work at a higher level Correct answer.
    3. Fully decomposing every deliverable into activities and resource assignments before baselining the schedule
    4. Adopting an adaptive lifecycle with a single delivery at the end of the project

    Explanation

    Rolling wave planning is progressive elaboration: work that will be performed soon is planned in detail, while work further out is kept at a higher level until more information is available. It keeps a predictive plan realistic without freezing detail that cannot yet be known.

  104. Question 104Predictive, Plan-Based Methodologies

    The quality team wants to determine whether the project is complying with approved processes and to surface inefficient policies being followed by the team. Which activity accomplishes this?

    1. Conducting a quality audit Correct answer.
    2. Performing quality control inspections on the deliverables
    3. Validating the scope with the customer
    4. Creating a cause-and-effect diagram of the defects

    Explanation

    A quality audit is a structured, usually independent review of quality processes to verify that approved policies and procedures are being followed and to identify inefficient or ineffective practices. It focuses on the process, whereas inspection focuses on the product.

  105. Question 105Predictive, Plan-Based Methodologies

    Which configuration management activity records and reports the status of all identified configuration items and of approved changes to them?

    1. Configuration identification
    2. Configuration status accounting Correct answer.
    3. Integrated change control
    4. Configuration verification and audit

    Explanation

    Configuration management comprises identification, control, status accounting, and verification and audit. Status accounting captures and reports information such as which version of a configuration item is approved and what change requests have been dispositioned.

  106. Question 106Predictive, Plan-Based Methodologies

    A six-month work package has three formally defined interim review checkpoints. Which approach gives the most reliable measure of earned progress for this work package?

    1. Percent complete reported verbally by the performing engineer
    2. Level of effort credited evenly in each reporting period
    3. The 0/100 rule applied only at the end of the six months
    4. Weighted milestones tied to each interim deliverable Correct answer.

    Explanation

    Weighted milestones attach objective, verifiable completion criteria to defined interim points, so progress is earned only when a measurable result is achieved. This produces a defensible and auditable measure for long work packages with defined checkpoints.

  107. Question 107Agile Frameworks/Methodologies

    On a Scrum team, which role is accountable for maximizing the value of the product resulting from the work of the Scrum Team?

    1. The Product Owner, who orders the product backlog Correct answer.
    2. The Scrum Master, who removes impediments for the team
    3. The developers, who choose work for each sprint
    4. The stakeholders, who approve the sprint goals

    Explanation

    The Product Owner is accountable for product value and for ordering the product backlog to reflect that value. The Scrum Master serves the process, while developers self-manage the sprint work but do not own product value. Stakeholders provide input rather than holding this accountability.

  108. Question 108Agile Frameworks/Methodologies

    Which Kanban practice makes bottlenecks and flow problems visible to the team?

    1. Displaying work on a board with workflow columns Correct answer.
    2. Estimating every item in story points before work begins
    3. Assigning each work item to a single specialist
    4. Holding a daily stand-up meeting limited to fifteen minutes

    Explanation

    Kanban makes work visible by showing items on a board with explicit workflow states and policies. This visibility helps the team see queues, bottlenecks, and flow problems. Estimation, stand-up meetings, and assignment choices do not by themselves visualize the workflow.

  109. Question 109Agile Frameworks/Methodologies

    What is the primary purpose of the Daily Scrum in Scrum?

    1. To inspect progress toward the Sprint Goal and adapt daily work Correct answer.
    2. To demonstrate the completed product increment to stakeholders
    3. To estimate the effort required for product backlog items
    4. To update the project schedule baseline for management reporting

    Explanation

    The Daily Scrum is a short event for developers to inspect progress toward the Sprint Goal and adjust the day's plan. It improves communication and identifies impediments. Demonstrating an increment belongs to the Sprint Review, and schedule baselines are not a Scrum artifact.

  110. Question 110Agile Frameworks/Methodologies

    Which Scrum event is used to inspect the increment and adapt the product backlog?

    1. Sprint Review Correct answer.
    2. Sprint Retrospective
    3. Daily Scrum
    4. Sprint Planning

    Explanation

    The Sprint Review inspects the increment and collaborates with stakeholders to adapt the product backlog. Sprint Planning sets the sprint goal and plan, while the Retrospective improves the team's process. The Daily Scrum inspects daily progress.

  111. Question 111Agile Frameworks/Methodologies

    According to the Agile Manifesto, which value is preferred over comprehensive documentation?

    1. Working software Correct answer.
    2. Following a plan
    3. Contract negotiation
    4. Process and tools

    Explanation

    The Agile Manifesto states that working software is valued over comprehensive documentation. Documentation still has value, but it should not substitute for delivering working software. The other items correspond to different pairs of values in the manifesto.

  112. Question 112Agile Frameworks/Methodologies

    Which Extreme Programming (XP) practice involves two developers working together at one workstation?

    1. Test-driven development
    2. Pair programming Correct answer.
    3. Collective code ownership
    4. Continuous integration

    Explanation

    Pair programming is an XP practice in which two developers collaborate closely on the same code at one workstation. It supports continuous review, shared understanding, and higher quality. The other options are separate XP practices with different purposes.

  113. Question 113Agile Frameworks/Methodologies

    Which Lean principle focuses on removing activities that do not add value from the customer's perspective?

    1. Creating flow
    2. Deferring commitment
    3. Building quality in
    4. Eliminating waste Correct answer.

    Explanation

    Lean defines waste as work that consumes resources without adding customer value, so eliminating waste is a core principle. Creating flow and building quality in are related Lean goals but address different concerns. Deferring commitment means delaying irreversible decisions until the last responsible moment.

  114. Question 114Agile Frameworks/Methodologies

    Which Scrum artifact is an ordered list of what is needed to improve the product?

    1. Definition of Done
    2. Product increment
    3. Product backlog Correct answer.
    4. Sprint backlog

    Explanation

    The product backlog is the emergent, ordered list of what the team needs to build to improve the product. The sprint backlog is the subset selected for a sprint, and the increment is the completed work. The Definition of Done is a quality standard, not a backlog.

  115. Question 115Agile Frameworks/Methodologies

    Which description best reflects the Scrum Master's role in a Scrum team?

    1. Owning the sprint backlog and assigning tasks to developers
    2. Coaching, facilitating, and removing impediments for the team Correct answer.
    3. Directing the developers on how to complete each backlog item
    4. Approving the product backlog order on behalf of the customers

    Explanation

    The Scrum Master is a servant-leader who coaches the team, facilitates Scrum events, and helps remove impediments. The role does not command developers or own product decisions. Backlog ordering belongs to the Product Owner, and the developers manage their own sprint work.

  116. Question 116Agile Frameworks/Methodologies

    A Scrum team wants to improve its process after a sprint. Which event is designed for that purpose?

    1. Sprint Planning
    2. Backlog refinement
    3. Sprint Review
    4. Sprint Retrospective Correct answer.

    Explanation

    The Sprint Retrospective is the regular event for inspecting how the team worked and identifying process improvements. Sprint Planning focuses on the upcoming sprint, and the Sprint Review focuses on the product increment. Backlog refinement prepares upcoming items but is not the team's process-improvement event.

  117. Question 117Agile Frameworks/Methodologies

    What is the main purpose of the Definition of Done in Scrum?

    1. To provide a shared quality standard that an increment must meet Correct answer.
    2. To record the acceptance criteria for each individual user story
    3. To document the project schedule and budget variances
    4. To list every task the developers will perform during the sprint

    Explanation

    The Definition of Done is a shared understanding of what it means for work to be complete and meet quality expectations. It applies to the increment as a whole. Task lists, individual story acceptance criteria, and financial reporting serve different purposes.

  118. Question 118Agile Frameworks/Methodologies

    In Kanban, what is the primary effect of setting work-in-progress (WIP) limits?

    1. It removes the need for a daily stand-up meeting
    2. It guarantees that every work item is delivered by its due date
    3. It increases the number of items started at the same time
    4. It limits concurrent work to improve flow and reveal bottlenecks Correct answer.

    Explanation

    WIP limits cap how much work can be in a given workflow state at one time. This constraint encourages finishing work, improves flow, and makes bottlenecks easier to see. WIP limits do not guarantee dates, eliminate coordination meetings, or increase the amount of work started.

  119. Question 119Agile Frameworks/Methodologies

    In SAFe, what is the main purpose of a Program Increment (PI) planning event?

    1. To replace the need for team-level sprint planning
    2. To align teams and plan the next program increment Correct answer.
    3. To estimate individual developer performance for annual reviews
    4. To finalize a fixed scope contract with the customer

    Explanation

    PI planning brings Agile Release Train teams together to align on a shared mission and plan the next program increment. It coordinates dependencies and commitments across teams. It does not replace team-level planning or serve as an individual performance or contracting mechanism.

  120. Question 120Agile Frameworks/Methodologies

    Why do agile teams use story points rather than only hours for estimating product backlog items?

    1. Story points measure the exact duration of each task
    2. Story points eliminate all uncertainty from estimates
    3. Story points are legally required for fixed-price contracts
    4. They express relative size and complexity, not exact time Correct answer.

    Explanation

    Story points support relative estimation of size, complexity, and uncertainty without implying false precision. Teams can compare items consistently and forecast using observed velocity. They are not a legal requirement, do not remove uncertainty, and are not exact duration measures.

  121. Question 121Agile Frameworks/Methodologies

    How is velocity most appropriately used by a Scrum team?

    1. As a fixed target that the team must increase every sprint
    2. As a forecasting aid based on work completed per sprint Correct answer.
    3. As a measure of individual productivity for performance appraisals
    4. As a substitute for the Definition of Done

    Explanation

    Velocity summarizes how much work a team completes per sprint and can support forecasting for future sprints. It is a planning aid, not an individual performance measure or a target to inflate. It also does not replace quality standards such as the Definition of Done.

  122. Question 122Agile Frameworks/Methodologies

    Which statement best describes an effective product vision in agile work?

    1. It assigns each backlog item to a specific developer
    2. It lists every feature that will be delivered in the next ten sprints
    3. It records the detailed acceptance criteria for the current sprint
    4. It describes the desired future state and guides the backlog Correct answer.

    Explanation

    A product vision communicates the desired future state and gives direction for ordering and refining the backlog. It is broader and longer-lived than a sprint plan or individual item details. Feature lists, task assignments, and sprint acceptance criteria operate at much more detailed levels.

  123. Question 123Agile Frameworks/Methodologies

    What is the main purpose of a Scrum of Scrums meeting when scaling Scrum?

    1. To replace the Daily Scrum for each individual team
    2. To approve changes to the product backlog for all teams
    3. To coordinate dependencies and integration across Scrum teams Correct answer.
    4. To conduct performance reviews for Scrum Masters

    Explanation

    A Scrum of Scrums is a scaling mechanism in which representatives coordinate work, dependencies, and integration across multiple Scrum teams. It complements, rather than replaces, each team's Daily Scrum. Backlog decisions and performance reviews are not its purpose.

  124. Question 124Agile Frameworks/Methodologies

    In test-driven development (TDD), what is the usual sequence of activities?

    1. Write all production code, then write tests, then refactor
    2. Design the database schema, then write tests for the user interface
    3. Write a failing test, make it pass, then refactor Correct answer.
    4. Write a test that passes immediately, then deploy without refactoring

    Explanation

    TDD follows a short red-green-refactor cycle: write a test that fails, write the minimum code to make it pass, then refactor while keeping tests green. This cycle drives design and confidence. Writing all code first or skipping refactoring does not follow TDD.

  125. Question 125Agile Frameworks/Methodologies

    Which prioritization technique groups requirements as Must have, Should have, Could have, and Will not have?

    1. Value stream mapping
    2. MoSCoW prioritization Correct answer.
    3. Planning poker
    4. Cumulative flow diagram

    Explanation

    MoSCoW prioritization classifies requirements into Must have, Should have, Could have, and Will not have categories. It helps stakeholders agree on what is essential within a timebox. Planning poker estimates size, value stream mapping analyzes flow, and cumulative flow diagrams track work status.

  126. Question 126Agile Frameworks/Methodologies

    Which characteristic best describes Feature-Driven Development (FDD)?

    1. It organizes work around timeboxed spikes with no defined features
    2. It organizes work around small, client-valued features Correct answer.
    3. It relies on a single continuous flow of unplanned work
    4. It prohibits any modeling or design activity

    Explanation

    FDD is an agile methodology that organizes delivery around small, client-valued features and short iterations. It includes lightweight modeling and planning activities rather than prohibiting design. It is not defined by unplanned continuous flow or featureless spikes.

  127. Question 127Agile Frameworks/Methodologies

    Under Scrum, who has the authority to cancel a sprint?

    1. The developers, when they cannot meet the sprint goal
    2. The Scrum Master, when the team is blocked
    3. The stakeholders, by majority vote at the sprint review
    4. The Product Owner, when the sprint goal is obsolete Correct answer.

    Explanation

    Only the Product Owner has the authority to cancel a sprint, and this may happen when the sprint goal becomes obsolete. The Scrum Master and developers may raise concerns but cannot cancel the sprint. Stakeholders do not hold this authority through voting.

  128. Question 128Agile Frameworks/Methodologies

    A Kanban team uses classes of service. Which class typically allows an item to bypass normal WIP limits to address an urgent production incident?

    1. Standard class
    2. Fixed date class
    3. Expedite class Correct answer.
    4. Intangible class

    Explanation

    The expedite class of service is used for urgent items that must move through the workflow immediately, often bypassing normal WIP limits. Standard and fixed-date items follow normal flow or deadline planning. Intangible class addresses the cost of delay rather than emergency handling.

  129. Question 129Agile Frameworks/Methodologies

    What is the main purpose of value stream mapping in Lean?

    1. To document the organizational chart and reporting lines
    2. To calculate the net present value of a project
    3. To assign story points to each team member's tasks
    4. To identify value-adding and non-value-adding steps Correct answer.

    Explanation

    Value stream mapping visualizes the steps, delays, and information flows needed to deliver value. It helps identify where waste and bottlenecks occur. It is not an estimation method, an organizational chart, or a financial valuation technique.

  130. Question 130Agile Frameworks/Methodologies

    In SAFe, what is an Agile Release Train (ART)?

    1. A tool used to automate continuous integration pipelines
    2. A temporary committee that approves funding for each sprint
    3. A long-lived team of agile teams delivering in a value stream Correct answer.
    4. A single team that owns all product backlog items for the enterprise

    Explanation

    An Agile Release Train is a long-lived group of agile teams that plans, commits, and delivers together around a value stream. It provides alignment and synchronization across teams in SAFe. It is not a single team, a funding committee, or an automation tool.

  131. Question 131Agile Frameworks/Methodologies

    Which agile contracting approach best fits a customer who requires a fixed delivery date but is willing to let scope vary?

    1. Fix date and scope while allowing cost to vary without limit
    2. Fix scope and cost while leaving the date open-ended
    3. Fix scope, date, and cost with formal change control for every adjustment
    4. Fix date and cost while allowing scope to vary by priority Correct answer.

    Explanation

    When the date is fixed but scope can vary, the team can hold date and cost steady and adjust scope according to priority. This preserves delivery predictability while allowing value trade-offs. Fixing all three constraints leaves no room for agile adaptation.

  132. Question 132Agile Frameworks/Methodologies

    Which Scrum role is accountable for maximizing the value of the product resulting from the work of the Scrum Team?

    1. The Scrum Master
    2. The key stakeholders
    3. The Product Owner Correct answer.
    4. The Developers

    Explanation

    Accountability for product value and for ordering the Product Backlog belongs to the Product Owner, who makes the economic trade-off decisions. The Scrum Master serves the team's process and the Developers create the increment. Stakeholders provide input but do not hold this accountability.

  133. Question 133Agile Frameworks/Methodologies

    In Extreme Programming, which practice calls for integrating and testing the code in the shared repository many times each day?

    1. Small releases
    2. On-site customer
    3. Continuous integration Correct answer.
    4. Coding standards

    Explanation

    Continuous integration is the XP practice of merging code into the shared codebase frequently, with automated builds and tests run on every merge. This keeps integration problems small and visible. On-site customer, coding standards, and small releases address different concerns.

  134. Question 134Agile Frameworks/Methodologies

    Which statement reflects a value expressed in the Agile Manifesto?

    1. Working software is valued over comprehensive documentation. Correct answer.
    2. Contract negotiation is valued over customer collaboration.
    3. Comprehensive documentation is more valuable than working software.
    4. Following a detailed plan is valued over responding to change.

    Explanation

    The Manifesto states that while documentation has value, working software is valued more highly. The same document values responding to change over following a plan and customer collaboration over contract negotiation. Only one option restates a Manifesto value in its actual direction.

  135. Question 135Agile Frameworks/Methodologies

    What is the recommended timebox for the Daily Scrum in Scrum?

    1. 1 hour
    2. 15 minutes Correct answer.
    3. 5 minutes
    4. 30 minutes

    Explanation

    The Daily Scrum is timeboxed to 15 minutes so it stays a short inspect-and-plan event for the Developers. Longer discussions are deferred to a separate conversation after the event. The timebox is fixed regardless of team size, which is why 30 or 60 minutes is incorrect.

  136. Question 136Agile Frameworks/Methodologies

    A Kanban team has an average of 12 items in progress and completes an average of 3 items per week. Using Little's Law, what is the approximate average cycle time?

    1. 36 weeks
    2. 9 weeks
    3. 0.25 weeks
    4. 4 weeks Correct answer.

    Explanation

    Little's Law states that average cycle time equals work in progress divided by throughput, so 12 divided by 3 gives 4 weeks. The rule is useful for predicting how long an item spends in the system at the current WIP level. Subtracting, multiplying, or inverting the two values does not follow the law.

  137. Question 137Agile Frameworks/Methodologies

    What is the primary purpose of the Sprint Review?

    1. To produce the detailed task plan for the coming sprint
    2. To agree process improvements for the next sprint
    3. To approve the release budget with the project sponsors
    4. To inspect the increment and get feedback Correct answer.

    Explanation

    The Sprint Review inspects the outcome of the sprint with stakeholders and adapts the Product Backlog based on what is learned. Process improvement is the work of the Retrospective, and task planning belongs to daily planning and Sprint Planning. Budget approval is outside the event's purpose.

  138. Question 138Agile Frameworks/Methodologies

    Which description best characterizes Scrumban?

    1. A Lean technique for mapping value-adding steps
    2. A scaling framework that synchronizes multiple Agile Release Trains
    3. Scrum roles and events plus Kanban flow and WIP limits Correct answer.
    4. Continuous flow with no defined roles or events

    Explanation

    Scrumban blends Scrum's roles and events with Kanban's visual workflow, WIP limits, and pull-based scheduling. Teams often adopt it when they want cadence and ownership together with flow control. It keeps structure rather than removing it.

  139. Question 139Agile Frameworks/Methodologies

    In DSDM, a team working inside a fixed timebox finds it cannot complete all planned work by the deadline. What does DSDM recommend?

    1. Add more people to the team to raise capacity
    2. Move the deadline and re-baseline the whole plan
    3. Lower the scope by dropping the lowest-priority items Correct answer.
    4. Extend the timebox until all planned work is complete

    Explanation

    DSDM fixes time and resources and negotiates scope, so the way to recover a timebox is to reduce content using prioritization such as MoSCoW, not to move the date. This protects the predictability that fixed timeboxes provide. Adding people late or extending the box undermines the principle.

  140. Question 140Agile Frameworks/Methodologies

    What is the main purpose of Product Backlog refinement?

    1. To close the sprint and calculate the remaining work
    2. To assign each backlog item to one specific developer
    3. To make backlog items clear and small enough for a sprint Correct answer.
    4. To record the team's velocity for the sprint that is running

    Explanation

    Refinement is the ongoing activity of clarifying, splitting, and re-estimating backlog items so that the top of the backlog is ready for Sprint Planning. It is not an assignment or reporting event. Ownership of items remains with the team as a whole.

  141. Question 141Agile Frameworks/Methodologies

    Which behaviour best illustrates servant leadership by a Scrum Master?

    1. Reviewing each developer's code to enforce standards personally
    2. Removing impediments and coaching the team to self-manage Correct answer.
    3. Assigning daily tasks to each developer to keep the team on schedule
    4. Escalating every team decision to senior management for approval

    Explanation

    Servant leadership means helping the team grow and removing obstacles so it can organize its own work. The Scrum Master leads by coaching and facilitating rather than directing tasks or controlling decisions. Directing work or hoarding approvals undermines self-management.

  142. Question 142Agile Frameworks/Methodologies

    How does planning poker help a team estimate backlog items?

    1. The Product Owner sets the estimate and the team accepts it
    2. Each member estimates privately and the Scrum Master averages the numbers
    3. Estimates are taken from a historical database and applied without discussion
    4. Members reveal estimates at the same time and discuss differences Correct answer.

    Explanation

    Planning poker has each member select a card and reveal it simultaneously, then discuss the outliers before re-voting. The discussion surfaces assumptions and risks that a silent average would hide. Estimates stay with the people doing the work rather than with one role.

  143. Question 143Agile Frameworks/Methodologies

    A cumulative flow diagram shows the band for work in progress widening steadily over several weeks while the band for completed work grows only slowly. What does this most likely indicate?

    1. Cycle time is decreasing and throughput is rising
    2. The team is completing work faster than new work arrives
    3. Arrivals exceed completions, so work is piling up Correct answer.
    4. The team has too few items in progress relative to its capacity

    Explanation

    In a cumulative flow diagram, a widening in-progress band means items are entering the system faster than they leave it, so queues and cycle time grow. A narrowing band would signal the opposite condition. Reading the vertical distance between bands gives the amount of work in each state.

  144. Question 144Agile Frameworks/Methodologies

    A team faces a backlog item with major technical uncertainty about which data storage design will meet performance needs. What is an appropriate agile response?

    1. Defer the item indefinitely until the architecture is fully specified
    2. Commit the item to the sprint and choose a design without investigation
    3. Split the item into smaller items that avoid the uncertainty
    4. Run a timeboxed spike to investigate before estimating Correct answer.

    Explanation

    A spike is a short, timeboxed investigation used to reduce technical or requirements uncertainty so the item can be estimated and built. It buys knowledge rather than functionality. Committing blindly, deferring indefinitely, or splitting to dodge the risk leaves the uncertainty unresolved.

  145. Question 145Agile Frameworks/Methodologies

    What is the main purpose of the Sprint Goal?

    1. To record the acceptance criteria for each product backlog item
    2. To list every task the team will perform during the sprint
    3. To give the sprint a single objective that guides the team Correct answer.
    4. To measure the team's velocity against the previous sprint

    Explanation

    The Sprint Goal is one objective for the sprint that provides focus and flexibility, so the team can adjust the scope of work while still meeting the goal. It is not a task list or a set of item-level criteria. Acceptance criteria are recorded on individual backlog items.

  146. Question 146Agile Frameworks/Methodologies

    What is the main characteristic of an information radiator used by an agile team?

    1. It shows key information prominently where passers-by can see it Correct answer.
    2. It replaces the need for any team conversation about progress
    3. It is a confidential report shared only with senior management
    4. It is updated once at the end of each project phase

    Explanation

    An information radiator is a highly visible, easy-to-read display such as a task board or burn-down chart that keeps status in front of the team and visitors without anyone asking. Its value depends on being current and open. It complements conversation rather than replacing it.

  147. Question 147Business Analysis Frameworks

    Which activity is primarily the responsibility of the business analyst rather than the project manager?

    1. Eliciting and documenting stakeholder requirements Correct answer.
    2. Accepting the final product on behalf of the sponsor
    3. Approving the project budget and releasing funds
    4. Assigning tasks to individual project team members

    Explanation

    Business analysts focus on identifying needs, eliciting requirements, and ensuring the solution delivers value, which is why requirement elicitation and documentation sit with them. Budget approval, task assignment, and formal product acceptance are management or sponsorship accountabilities.

  148. Question 148Business Analysis Frameworks

    A requirement states that the payment portal must complete each transaction in under two seconds. How is this requirement best classified?

    1. Transition requirement
    2. Functional requirement
    3. Non-functional requirement Correct answer.
    4. Business requirement

    Explanation

    Performance targets such as response time are quality attributes, which are classified as non-functional requirements. Functional requirements describe what the system does, while business requirements describe organizational goals.

  149. Question 149Business Analysis Frameworks

    Which statement best describes a business requirement?

    1. A high-level statement of organizational goals and needs Correct answer.
    2. A description of a software module's internal logic
    3. A step-by-step procedure for testing a feature
    4. A constraint on the technology stack used to build a product

    Explanation

    Business requirements explain why the work is being done by stating the goals, objectives, or needs of the organization. They sit above stakeholder and solution requirements, which describe who is affected and how the solution will behave.

  150. Question 150Business Analysis Frameworks

    A team wants to confirm that every approved requirement has been built and tested and that no unapproved scope has been added. Which tool best supports this?

    1. A traceability matrix Correct answer.
    2. A risk register with owners
    3. A resource histogram
    4. A burn-down chart for sprints

    Explanation

    A traceability matrix links each requirement to its design elements, build components, and test cases, which lets the team confirm coverage in both directions. Unlinked items reveal missing work or unapproved additions.

  151. Question 151Business Analysis Frameworks

    What is the primary purpose of a product roadmap?

    1. To communicate planned deliverables and outcomes over time Correct answer.
    2. To record the detailed acceptance criteria for each user story
    3. To list the daily tasks assigned to each developer
    4. To document the approved budget breakdown by phase

    Explanation

    A roadmap communicates the intended sequence of outcomes and major deliverables across a horizon, giving stakeholders a sense of direction. Detailed acceptance criteria belong in backlog items, and daily tasks belong in a schedule or task board.

  152. Question 152Business Analysis Frameworks

    A project has stable, well-understood requirements, a fixed regulatory deadline, and a need for formal sign-off at each stage. Which delivery approach fits best?

    1. An agile approach with two-week sprints and continuous reprioritization
    2. A hybrid approach that defers all documentation until release
    3. A predictive, plan-driven approach with phase gates Correct answer.
    4. An exploratory approach with no baseline scope

    Explanation

    Low uncertainty, fixed external deadlines, and formal stage approvals all favor a predictive lifecycle with defined phases and gate reviews. Adaptive approaches are chosen when requirements are expected to change frequently.

  153. Question 153Business Analysis Frameworks

    The primary purpose of a business case is to:

    1. define the technical architecture of the proposed solution
    2. justify the investment against expected costs and benefits Correct answer.
    3. assign accountability for each project deliverable
    4. record the lessons learned from previous similar projects

    Explanation

    A business case presents the rationale for the investment by weighing expected benefits against costs, risks, and alternatives. It supports the go/no-go decision and later becomes the reference for benefits realization.

  154. Question 154Business Analysis Frameworks

    Six months after a new ordering system goes live, the organization measures reduced order-processing time against the targets set in the business case. This activity is best described as:

    1. configuration management
    2. scope verification
    3. benefits realization Correct answer.
    4. requirements validation

    Explanation

    Benefits realization is the process of measuring actual outcomes against the benefits promised in the business case after the solution is in use. It confirms whether the investment delivered the intended value.

  155. Question 155Business Analysis Frameworks

    A stakeholder requests a new feature after the requirements baseline has been approved. What should happen first?

    1. The request is logged and evaluated through change control Correct answer.
    2. The request is rejected because the baseline is approved
    3. The product backlog is cleared and re-estimated from scratch
    4. The team builds the feature and documents it at the next status meeting

    Explanation

    Once a baseline exists, changes are handled through the integrated change control process, where impact on scope, schedule, cost, and quality is assessed before a decision. Building first or rejecting automatically bypasses that evaluation.

  156. Question 156Business Analysis Frameworks

    Configuration management on a project primarily ensures that:

    1. deliverable versions and changes are identified and controlled Correct answer.
    2. procurement contracts are awarded only to qualified vendors
    3. the project schedule is compressed to meet the agreed deadline
    4. stakeholders receive training on the new business processes

    Explanation

    Configuration management identifies configuration items, records their status, and controls changes to them so that everyone works from the correct version. It underpins traceability and auditability of deliverables.

  157. Question 157Business Analysis Frameworks

    A stakeholder analysis is performed primarily to:

    1. identify stakeholders and assess their needs and influence Correct answer.
    2. select the project management software tool for the team
    3. estimate the total cost of quality for the product
    4. calculate the earned value performance of the project

    Explanation

    Stakeholder analysis identifies who is affected or can affect the work and assesses their interest, influence, and needs so engagement can be planned. This directly shapes elicitation and communication strategies.

  158. Question 158Business Analysis Frameworks

    A business analyst needs to understand how clerks actually perform a task that involves many informal workarounds the staff find hard to describe. Which elicitation technique is most suitable?

    1. Document analysis of the procedure manual
    2. A survey distributed to all employees
    3. Direct observation of the clerks at work Correct answer.
    4. A focus group with senior managers

    Explanation

    Observation reveals what people actually do, including undocumented workarounds that interviews or manuals may miss. It is the preferred technique when tacit or habitual behavior is the subject of study.

  159. Question 159Business Analysis Frameworks

    A team ranks requirements using the categories must have, should have, could have, and will not have. This technique is known as:

    1. the Delphi technique
    2. multivoting
    3. MoSCoW prioritization Correct answer.
    4. the nominal group technique

    Explanation

    MoSCoW prioritization sorts items into must, should, could, and will-not-have categories to focus delivery on essential scope. The other techniques are group decision-making or consensus methods rather than fixed priority categories.

  160. Question 160Business Analysis Frameworks

    The purpose of a minimum viable product (MVP) is to:

    1. complete all non-functional requirements before any functional ones
    2. release the smallest increment that allows validated learning Correct answer.
    3. deliver every planned feature at the lowest possible cost
    4. produce a throwaway prototype with no user involvement

    Explanation

    An MVP delivers just enough functionality to test assumptions with real users and learn whether the product delivers value. It is a learning instrument, not a cost-cutting shortcut or a discardable mock-up.

  161. Question 161Business Analysis Frameworks

    A wireframe is best used to:

    1. document the business rules governing a core process
    2. record the formal sign-off of the project charter
    3. show a screen's layout and interaction before build Correct answer.
    4. estimate the effort required to build a new database

    Explanation

    A wireframe is a low-fidelity visual model of a screen's structure, content placement, and interaction, used to confirm understanding early. It deliberately avoids detailed visual design so feedback focuses on layout and flow.

  162. Question 162Business Analysis Frameworks

    Reviewing requirements to confirm that they are complete, consistent, and unambiguous is an example of:

    1. Benefits realization, because the review confirms delivered value
    2. Validation, because the review confirms the product suits user needs
    3. Verification, because the review confirms requirements are well formed Correct answer.
    4. Configuration auditing, because the review confirms approved versions

    Explanation

    Verification asks whether the requirements are written correctly and conform to quality standards such as completeness, consistency, and lack of ambiguity. Validation asks the different question of whether they describe the right solution for stakeholder needs.

  163. Question 163Business Analysis Frameworks

    A requirements baseline is established when:

    1. approved requirements are placed under change control Correct answer.
    2. the project sponsor has been formally identified and assigned
    3. all requirements have been tested and verified in production
    4. the first complete draft of requirements is circulated to all reviewers

    Explanation

    A baseline is the approved version of requirements that is then placed under formal change control. From that point, changes must be evaluated and approved rather than simply absorbed.

  164. Question 164Business Analysis Frameworks

    Which activity best describes backlog refinement?

    1. Archiving completed user stories at the end of the project
    2. Converting all user stories into formal requirement specifications
    3. Reviewing, clarifying, and re-estimating backlog items regularly Correct answer.
    4. Assigning each story to a specific developer in advance

    Explanation

    Backlog refinement is an ongoing activity in which the team reviews upcoming items, adds detail, splits large items, and re-estimates them. It keeps the top of the backlog ready for near-term planning.

  165. Question 165Business Analysis Frameworks

    If a business rule changes and the team needs to find every design element and test case affected, which traceability direction is used?

    1. Backward traceability, from test cases to requirements
    2. Horizontal traceability across projects in the portfolio
    3. Vertical traceability, from the sponsor to the team
    4. Forward traceability, to downstream artifacts Correct answer.

    Explanation

    Forward traceability follows a requirement or rule into downstream artifacts such as design, build, and tests, which is exactly what an impact analysis of a change requires. Backward traceability works in the opposite direction, from artifacts up to the source requirement.

  166. Question 166Business Analysis Frameworks

    Compared with predictive projects, agile projects typically handle requirements documentation by:

    1. producing a single comprehensive specification before work starts
    2. documenting only non-functional requirements
    3. progressively, with detail sufficient for the next increment Correct answer.
    4. avoiding written documentation entirely

    Explanation

    Agile approaches document progressively, elaborating requirements just in time and only to the level of detail needed for the upcoming increment. Documentation is still produced, but its timing and depth differ from a single upfront specification.

  167. Question 167Business Analysis Frameworks

    Feature A offers an annual benefit of $60,000 at a build cost of $20,000. Feature B offers an annual benefit of $25,000 at a build cost of $10,000. Using value-based prioritization, which feature should be delivered first?

    1. Feature A, because its net benefit and ratio are both higher Correct answer.
    2. Feature B, because cheaper features are always prioritized first
    3. Feature B, because it costs less to build than Feature A
    4. Neither, because priority is set only by sponsor preference

    Explanation

    Feature A returns a net benefit of $40,000 and a benefit-to-cost ratio of 3, both better than Feature B's $15,000 net benefit and ratio of 2.5. Value-based prioritization compares expected benefit against cost rather than cost alone.

  168. Question 168Business Analysis Frameworks

    Stakeholder sign-off on requirements is most valuable because it:

    1. establishes an agreed baseline for later changes Correct answer.
    2. transfers all of the project risk to the stakeholders
    3. eliminates the need for formal testing before release
    4. guarantees that the solution will need no further changes

    Explanation

    Sign-off confirms a shared understanding of the requirements and creates the approved baseline that later change requests are measured against. It does not prevent change, remove risk, or replace testing.

  169. Question 169Business Analysis Frameworks

    Before committing to a solution option, an organization checks whether it has the staff skills and technology needed to build and operate it. Which feasibility test is being performed?

    1. Legal feasibility, based on compliance with all regulations
    2. Economic feasibility, based on a full cost-benefit analysis
    3. Schedule feasibility, based on the committed delivery date
    4. Technical and operational feasibility Correct answer.

    Explanation

    Technical feasibility asks whether the organization has the capability and technology to build the solution, while operational feasibility asks whether it can be run and sustained in the target environment. Cost, timing, and regulatory compliance are separate feasibility dimensions.

  170. Question 170Business Analysis Frameworks

    A context diagram is used in business analysis primarily to:

    1. show the sequence of messages exchanged between systems
    2. display the schedule of deliverables for each release
    3. define the solution boundary and its external entities Correct answer.
    4. model the detailed data attributes of an entity

    Explanation

    A context diagram shows the solution as a single process surrounded by the external entities that interact with it, making the scope boundary explicit. It deliberately omits internal detail, which is modeled in later decomposition diagrams.

  171. Question 171Business Analysis Frameworks

    At the end of a project, the review that captures what went well, what did not, and what should be done differently is called:

    1. a feasibility study of the solution
    2. a configuration audit
    3. a requirements workshop
    4. a lessons learned review Correct answer.

    Explanation

    A lessons learned review captures experiences and recommendations so future work can benefit from them. It is typically performed at phase gates and at project or product closure.

  172. Question 172Business Analysis Frameworks

    Which of the following best describes the purpose of needs assessment in business analysis?

    1. To assign project resources and finalize the schedule
    2. To build and test the solution before release
    3. To approve the project budget and procurement plan
    4. To define the problem and the desired outcome Correct answer.

    Explanation

    Needs assessment identifies the business problem or opportunity, the current state, and the desired future state before solution work begins. It establishes the gap and value target that later requirements and solutions must address.

  173. Question 173Business Analysis Frameworks

    Which artifact expresses a requirement as a short narrative from the user's perspective?

    1. A data dictionary
    2. A process map
    3. A user story Correct answer.
    4. A business rule

    Explanation

    A user story states a need in a brief, user-centered narrative and is common on agile efforts. Business rules constrain behavior, a data dictionary defines data elements, and a process map shows workflow.

  174. Question 174Business Analysis Frameworks

    Which elicitation technique brings key stakeholders together in a structured session to clarify and agree on requirements?

    1. A facilitated workshop Correct answer.
    2. Document analysis
    3. A survey questionnaire
    4. A focus group

    Explanation

    A facilitated workshop assembles decision makers and subject matter experts to elicit, clarify, and resolve requirements in one structured session. Surveys and focus groups gather input but usually do not drive negotiated agreement on requirements.

  175. Question 175Business Analysis Frameworks

    Which requirements category states the behaviors and functions a solution must provide?

    1. Business rules
    2. Functional requirements Correct answer.
    3. Nonfunctional requirements
    4. Transition requirements

    Explanation

    Functional requirements describe what the solution must do, including the behaviors and functions it must support. Nonfunctional requirements describe qualities or constraints, and transition requirements address temporary needs during the move to the new solution.

  176. Question 176Business Analysis Frameworks

    Which model shows the sequence of steps, decisions, and handoffs in a process?

    1. A flowchart Correct answer.
    2. A context diagram
    3. A SWOT matrix
    4. A stakeholder map

    Explanation

    A flowchart models the sequence of activities, decision points, and handoffs that make up a process. Context diagrams show system boundaries, while SWOT and stakeholder maps support strategy and stakeholder analysis.

  177. Question 177Business Analysis Frameworks

    Which role is primarily responsible for identifying business needs and recommending solutions that deliver value?

    1. The quality auditor
    2. The project sponsor
    3. The business analyst Correct answer.
    4. The procurement lead

    Explanation

    The business analyst performs needs assessment, elicitation, requirements analysis, and solution evaluation to help the organization realize value. Sponsors authorize and fund work, while auditors and procurement leads have different responsibilities.

  178. Question 178Business Analysis Frameworks

    A team checks whether a proposed solution fits the organization's current technology stack and support capacity. Which analysis are they performing?

    1. Cost-benefit analysis
    2. Risk appetite analysis
    3. Technical feasibility Correct answer.
    4. Stakeholder impact analysis

    Explanation

    Technical feasibility examines whether the organization has or can obtain the technology, skills, and support needed for a solution. Cost-benefit analysis compares financial value, while risk appetite and stakeholder impact address different concerns.

  179. Question 179Business Analysis Frameworks

    Acceptance criteria are used primarily to:

    1. Estimate the total cost of the project
    2. Define conditions for accepting a work item Correct answer.
    3. Record decisions made by the steering committee
    4. Sequence work across the project team

    Explanation

    Acceptance criteria state the specific, testable conditions that a requirement or work item must meet to be considered complete and acceptable. They support verification and reduce ambiguity but are not cost estimates, schedules, or decision logs.

  180. Question 180Business Analysis Frameworks

    A team evaluates three vendor solutions against cost, risk, and fit, assigning each criterion a weight and a score. Which technique are they using?

    1. Root cause analysis
    2. Value stream mapping
    3. Force field analysis
    4. Weighted scoring Correct answer.

    Explanation

    Weighted scoring compares options by rating each one against criteria and multiplying by criterion weights. Root cause and force field analysis examine causes or driving and restraining forces, while value stream mapping analyzes flow and waste.

  181. Question 181Business Analysis Frameworks

    A defect keeps recurring, so the analyst asks why repeatedly until the underlying process cause is identified. This is an example of:

    1. A fishbone diagram
    2. A decision tree
    3. A Pareto chart
    4. The five whys Correct answer.

    Explanation

    The five whys technique drills into a problem by repeatedly asking why until the root cause is exposed. A fishbone diagram also explores causes but organizes them into categories rather than following a single why chain, and a Pareto chart ranks frequencies.

  182. Question 182Business Analysis Frameworks

    A stakeholder has high influence over the solution but low interest in day-to-day details. Which engagement approach is most appropriate?

    1. Monitor with little communication
    2. Involve in every design session
    3. Escalate all issues to them
    4. Consult on key decisions Correct answer.

    Explanation

    High-influence, low-interest stakeholders need enough engagement to protect their interests without overloading them, so consulting on key decisions and keeping them informed fits. Involving them in every session over-engages them, while minimal monitoring risks missed concerns.

  183. Question 183Business Analysis Frameworks

    After a solution is deployed, users adopt only part of the new workflow and expected benefits lag. Which action best fits solution evaluation?

    1. Close the project because the solution was delivered
    2. Add more features before measuring outcomes
    3. Measure actual outcomes against intended value Correct answer.
    4. Reassign the project manager to another effort

    Explanation

    Solution evaluation compares actual solution performance and outcomes with the intended business value and identifies barriers to value. Closing or adding features without measurement skips that evaluation step.

  184. Question 184Business Analysis Frameworks

    A business analyst reviews existing policies, manuals, and system logs before interviewing staff. Which technique is this?

    1. Document analysis Correct answer.
    2. Brainstorming
    3. Prototyping
    4. Direct observation

    Explanation

    Document analysis examines existing materials such as policies, manuals, reports, and system records to understand the current state and requirements. Observation watches work as it happens, prototyping builds representations, and brainstorming generates ideas.

  185. Question 185Business Analysis Frameworks

    A team creates a fictional representative user to guide design decisions. This artifact is a:

    1. A story map
    2. A data model
    3. A use case
    4. A persona Correct answer.

    Explanation

    A persona is a fictional but research-based representation of a user group, used to keep design focused on user needs. A use case describes interactions with a system, a story map orders user activities, and a data model defines data structures.

  186. Question 186Business Analysis Frameworks

    A requirement cannot be linked to any business objective in the traceability matrix. What does this most likely indicate?

    1. It is automatically approved
    2. It has been fully tested
    3. It has no assigned owner
    4. It may lack business justification Correct answer.

    Explanation

    Traceability links requirements to goals, stakeholders, and other work products, so a missing link to any business objective suggests the requirement may not be justified. It does not by itself prove testing status, ownership, or approval.

  187. Question 187Business Analysis Frameworks

    A user story is generally considered ready to be taken into a sprint when it:

    1. Is assigned to a named developer
    2. Has been approved by every stakeholder
    3. Meets the team's agreed readiness criteria Correct answer.
    4. Has a fixed cost estimate in dollars

    Explanation

    A definition of ready captures the team's agreement on what a backlog item needs before it can be taken into a sprint, such as clear acceptance criteria and an appropriate size. Cost estimates, individual assignment, and universal stakeholder approval are not standard readiness conditions.

  188. Question 188Business Analysis Frameworks

    The scope of a solution is best defined by:

    1. The complete list of features requested by users
    2. The project budget and resource calendar
    3. The organizational chart of the delivery team
    4. The boundary of what the solution will address Correct answer.

    Explanation

    Solution scope sets the boundary of what the solution will change or deliver, clarifying what is in and out. Feature lists, budgets, and organizational charts inform planning but do not define the boundary of the solution itself.

  189. Question 189Business Analysis Frameworks

    A business analysis plan primarily defines:

    1. The marketing plan for the product
    2. The technical architecture of the solution
    3. How business analysis work will be performed and managed Correct answer.
    4. The final acceptance test scripts

    Explanation

    The business analysis plan describes the approach, activities, deliverables, and governance for the business analysis work. It is not the solution architecture, the test scripts, or the product marketing plan.

  190. Question 190Business Analysis Frameworks

    An analyst needs input from 2,000 geographically dispersed customers about service satisfaction. Which technique is most practical?

    1. A survey Correct answer.
    2. A facilitated workshop
    3. Observation
    4. Focus groups

    Explanation

    Surveys can reach large, dispersed groups efficiently and support quantitative analysis. Focus groups and workshops are limited in size, and observation is time-intensive and not suited to measuring broad satisfaction.

  191. Question 191Business Analysis Frameworks

    Two departments state requirements that directly conflict. What should the business analyst do first?

    1. Remove both requirements from scope
    2. Choose the requirement from the louder department
    3. Escalate immediately to the project sponsor
    4. Analyze the conflict and facilitate resolution Correct answer.

    Explanation

    The analyst should first understand the conflict, its causes, and its impacts, then facilitate agreement among the parties. Escalation may be needed later, but removing requirements or choosing by volume bypasses analysis.

  192. Question 192Business Analysis Frameworks

    A feature is present but its absence would not upset users, while its presence delights them. In the Kano model this is a:

    1. Reverse quality
    2. Delighter Correct answer.
    3. Performance feature
    4. Must-be quality

    Explanation

    Kano distinguishes must-be qualities (expected, absence causes dissatisfaction), performance features (more is better), and delighters (unexpected, create satisfaction). A delighter's absence does not cause dissatisfaction, but its presence pleases users.

  193. Question 193Business Analysis Frameworks

    The current-state assessment shows a process takes five days, while the future state requires one day. The difference between them is best described as:

    1. A capability gap Correct answer.
    2. A transition requirement
    3. A business rule
    4. A project risk

    Explanation

    A capability gap is the difference between current and desired performance or capability that a solution must close. Risks, business rules, and transition requirements may relate to closing the gap but are not the gap itself.

  194. Question 194Business Analysis Frameworks

    A review confirms that requirements are written correctly and are testable, but does not confirm that they meet the business need. This review addresses:

    1. Solution validation
    2. Benefits realization
    3. Stakeholder engagement
    4. Requirements verification Correct answer.

    Explanation

    Verification checks that requirements are well-formed, complete, consistent, and testable, while validation checks that they describe the right solution for the business need. A review focused on the quality of the requirement statements is verification.

  195. Question 195Business Analysis Frameworks

    An organization is deciding whether to build, buy, or reuse a solution. Which consideration most directly affects that decision?

    1. The number of stakeholders on the project
    2. The length of the project charter
    3. The delivery team's preferred methodology
    4. Total cost of ownership and fit Correct answer.

    Explanation

    Build, buy, or reuse decisions compare total cost of ownership, strategic fit, risk, and capability against the alternatives. Team preferences, stakeholder counts, and charter length are not the primary decision criteria.

  196. Question 196Business Analysis Frameworks

    A proposed solution solves the stated problem but creates a new compliance risk. What should the analyst do?

    1. Approve the solution and document the risk
    2. Assess the risk against the expected value Correct answer.
    3. Reject the solution without further review
    4. Delegate the decision to the delivery team

    Explanation

    Solution evaluation should weigh expected benefits against new risks, constraints, and impacts before recommending a path. Approving blindly, rejecting without review, or delegating the business decision avoids that analysis.

  197. Question 197Business Analysis Frameworks

    The Business Analysis Core Concept Model defines six fundamental concepts that apply to all business analysis work. Which of the following is one of those six concepts?

    1. Contract
    2. Budget
    3. Schedule
    4. Change Correct answer.

    Explanation

    The six core concepts are change, need, solution, stakeholder, value, and context; they describe what business analysis work is fundamentally about, regardless of industry, methodology, or project type. Budget, schedule, and contract are project management constraints rather than elements of the model.

  198. Question 198Business Analysis Frameworks

    An organization states that it must cut the average time to resolve a customer complaint by 40 percent within the next twelve months. Under standard requirements classification, this statement is best described as a:

    1. transition requirement
    2. stakeholder requirement
    3. business requirement Correct answer.
    4. solution requirement

    Explanation

    Business requirements state enterprise-level goals, objectives, and intended outcomes, and they explain why the organization is undertaking the change. Requirements that describe what a particular group needs, what the solution itself must do or how well it must do it, and what is temporarily needed to move to the new state are classified separately.

  199. Question 199Business Analysis Frameworks

    During prioritization, a team marks a feature as valuable to users and painful to leave out, yet not mandatory for launch; it will be built only if capacity remains once mandatory items are covered. In MoSCoW terms this feature is:

    1. Should have Correct answer.
    2. Must have
    3. Could have
    4. Won't have

    Explanation

    Should-have items are important and deliver real value, but the product can launch without them, so they are scheduled only if time and effort allow. Must-haves are non-negotiable for launch, could-haves are lower-value optional items, and won't-haves are explicitly agreed to be out of scope for the current timeframe.

  200. Question 200Business Analysis Frameworks

    Which requirement classification covers temporary capabilities needed only while moving from the current state to the target state, and is typically the last to be fully defined?

    1. Non-functional requirements, because they set quality attributes of the solution
    2. Stakeholder requirements, because they capture the needs of affected groups
    3. Transition requirements, because they depend on how the solution is built Correct answer.
    4. Business requirements, because they set the enterprise-level goals for the change

    Explanation

    Transition requirements describe capabilities such as data conversion, user training, and parallel operation that are needed only during the changeover and cease to apply once the target state is reached. Because they depend on the chosen solution design and delivery approach, they usually cannot be finalized until the solution is developed.

CAPM flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Project
A temporary endeavor undertaken to create a unique product, service, or result, with a defined start and end, distinct from ongoing operations.
Project charter
Document issued by the sponsor that formally authorizes the project, names the project manager, and states high-level scope, objectives, budget, and risks.
Project management office
Organizational unit that standardizes project governance; types are supportive (low control), controlling (moderate control), and directive (manages projects directly with high control).
Functional organization
Structure grouped by specialty where the project manager has little authority, staff report to one functional manager, and coordination across departments happens through those managers.
Tuckman ladder
Model of team development with five stages - forming, storming, norming, performing, adjourning - where productivity peaks at performing and the team disbands at adjourning.
Stakeholder register
Document recording identified stakeholders with their roles, contact information, requirements, expectations, influence, and potential impact, used to plan how to engage each.
Triple constraint
Interrelated constraints of scope, schedule, and cost (with quality) that must be balanced; changing one typically requires adjusting at least one of the others.
Conflict resolution methods
Five approaches: collaborate/problem-solve and compromise yield win-win outcomes; force, avoid, and accommodate are win-lose; collaboration best supports lasting resolution.
Work breakdown structure
Deliverable-oriented hierarchical decomposition of the total project scope; the lowest level is a work package, and the 100 percent rule requires children fully represent the parent.
Critical path
Longest duration path through the project network with zero total float; it determines the shortest possible project duration, and any delay on it extends the finish date.
Total float
Time an activity can be delayed without delaying the project finish date; calculated as late start minus early start or late finish minus early finish.
Three-point estimating
Technique using optimistic, most likely, and pessimistic estimates; PERT beta formula (O+4M+P)/6; standard deviation is (P-O)/6; triangular average is (O+M+P)/3.
Cost performance index
Earned value ratio CPI = EV/AC; greater than 1.0 means work is costing less than planned, below 1.0 means cost overrun, equal to 1.0 means on budget.
Estimate at completion
Forecast of total project cost; when current cost performance continues, EAC = BAC/CPI; other forms apply when variances are atypical or expected to cease.
Contingency reserve
Time or money set aside for identified risks (known unknowns), owned and used by the project manager; management reserve covers unknown unknowns and typically needs sponsor approval.
Risk response strategies
For threats: avoid, transfer, mitigate, escalate, accept. For opportunities: exploit, share, enhance, escalate, accept. Selection depends on risk exposure and risk appetite.
Agile Manifesto values
Four values: individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; responding to change over following a plan.
Sprint
Timeboxed Scrum iteration of one to four weeks, commonly two, at the end of which a potentially releasable, Done product increment is produced.
Product owner
Scrum role accountable for maximizing product value by managing and ordering the product backlog, defining items clearly, and representing stakeholder needs to the development team.
Daily scrum
Fifteen-minute timeboxed event for the development team to inspect progress toward the sprint goal and adapt the plan for the next 24 hours.
Definition of Done
Shared, explicit checklist of quality criteria an increment must satisfy to be considered complete; it is distinct from the acceptance criteria of individual backlog items.
Kanban WIP limits
Caps on how many items may be in progress at each workflow stage; they expose bottlenecks, discourage multitasking, and support a pull-based flow of work.
Velocity
Amount of work, often measured in story points, a team completes per iteration; used to forecast future capacity and never to compare different teams.
Burndown chart
Graph of remaining work versus time for an iteration or release; a downward trend to zero shows progress, while a flat or rising line suggests scope or impediment problems.
Business analysis
Set of activities that identify business needs and recommend solutions delivering value to stakeholders, bridging business problems and the teams that build solutions.
BACCM core concepts
Business Analysis Core Concept Model's six concepts: change, need, solution, stakeholder, value, and context; every business analysis task is considered in relation to all six.
Requirements classification
Categories: business requirements (why the change), stakeholder requirements (who needs what), solution requirements (functional and non-functional), and transition requirements (temporary, needed only to implement).
Elicitation techniques
Methods for drawing out requirements, including interviews, workshops, focus groups, observation or job shadowing, surveys, document analysis, brainstorming, and prototyping.
Requirements traceability matrix
Grid linking each requirement to its source, business need, design components, and test cases, supporting impact analysis, coverage checks, and verification.
MoSCoW prioritization
Prioritization scheme with Must have, Should have, Could have, and Won't have this time; used to agree scope when time is fixed and trade-offs are needed.
INVEST criteria
Heuristic for good user stories: Independent, Negotiable, Valuable, Estimable, Small, and Testable; guides splitting large items into backlog-ready stories.
Kano model
Classifies product features as must-be, performance, delighter, indifferent, or reverse, based on how their presence affects customer satisfaction; guides prioritization of requirements.

CAPM study guide

Project Management Fundamentals and Core Concepts

Projects, Programs, Portfolios

A project is a temporary endeavor undertaken to create a unique product, service, or result. Temporary means a defined start and end; unique means it is not routine repetition. Ongoing repetitive work is operations. Programs group related projects for coordinated benefits; portfolios group projects, programs, and operations to meet strategic objectives. Many exam items simply ask you to classify a scenario.

Process Groups and Knowledge Areas

The traditional framework organizes work into five process groups - initiating, planning, executing, monitoring and controlling, and closing - across ten knowledge areas (scope, schedule, cost, quality, resource, communications, risk, procurement, stakeholder, plus integration). Initiating produces the project charter and stakeholder register; planning produces baselines; monitoring and controlling compares performance to plan and manages change; closing gains acceptance, transfers the product, and archives lessons learned. Common traps: believing lessons learned are only captured at the end (they are captured continuously and archived at close), and assuming a project manager in a weak matrix has authority to commit resources.

Structure, Tailoring, and Value

Organizational structure shapes authority. Functional and weak matrix structures leave the project manager as a coordinator; balanced matrix shares authority with functional managers; strong matrix and projectized structures give the project manager real authority over resources. Modern practice emphasizes principles and value delivery over rigid process compliance, and delivery approach - predictive, hybrid, or adaptive - is chosen based on requirement stability, uncertainty, risk, and stakeholder involvement.

Rule of thumb: ask “temporary and unique?” If yes, it is a project.

Worked example: A service desk answering tickets daily is operations. Launching a new ticketing system is a project. Managing that system's rollout alongside a data migration and a training program is a program.

Predictive, Plan-Based Methodologies

Baselines

The scope baseline has three components: the project scope statement, the work breakdown structure (WBS), and the WBS dictionary. The WBS decomposes deliverables into work packages that can be estimated, assigned, and controlled; it is deliverable-oriented, not an organizational chart. Schedule baselines come from network diagrams and critical path analysis; cost baselines come from estimating and budgeting.

Critical Path

The critical path is the longest path through the network and therefore determines the shortest possible project duration. Activities on it have zero total float, so any delay there delays the project. Crashing adds resources to critical-path activities and usually raises cost; fast tracking overlaps activities and usually raises risk. Trap: a path with many activities is not automatically critical - path length, not activity count, decides.

Earned Value

Earned value compares planned value (PV), earned value (EV), and actual cost (AC). SV = EV − PV; CV = EV − AC; SPI = EV ÷ PV; CPI = EV ÷ AC. Negative variances and indices below 1.0 are unfavorable. Rule of thumb: EV always sits in the numerator; the comparison term sits in the denominator.

Change Control and Risk

No change enters a baseline without integrated change control: request, assess impact, decide (approve, reject, defer), update plans and documents, then communicate. Risks are uncertain events logged in a risk register with probability, impact, and an owner; threat responses are avoid, transfer, mitigate, and accept, while opportunity responses are exploit, share, enhance, and accept. A risk that has occurred becomes an issue. Trap: contingency reserve covers known risks and is managed by the project manager; management reserve covers unknown unknowns and needs sponsor approval.

Worked example: PV = 100, EV = 90, AC = 120, so SV = −10 (behind schedule), CV = −30 (over budget), SPI = 0.90, CPI = 0.75.

Agile Frameworks and Methodologies

Mindset Before Mechanics

Agile rests on four values - individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan - plus twelve principles. The items on the right still matter; the items on the left are valued more. Agile delivery is iterative and incremental and relies on empirical process control: transparency, inspection, and adaptation. Predictive approaches fit stable, well-understood scope; agile fits high uncertainty and evolving requirements; hybrid blends both.

Scrum

Scrum has three accountabilities - Product Owner (maximizes value and orders the backlog), Scrum Master (coaches, facilitates, removes impediments), and Developers (self-managing, deliver the increment) - five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), and three artifacts (Product Backlog, Sprint Backlog, Increment) with commitments. Traps: the Scrum Master is not a project manager and does not assign work; the Product Owner, not the team or stakeholders, orders the backlog; scope changes mid-Sprint are negotiated with the Product Owner rather than imposed.

Kanban, XP, and Scaling

Kanban visualizes flow, limits work in progress, and manages queues; it requires no iterations. Extreme Programming emphasizes engineering practices such as test-driven development, pair programming, and continuous integration. Scaling frameworks such as SAFe coordinate many teams. Estimation is relative - story points, planning poker, t-shirt sizing - because people compare better than they estimate absolutely.

Rule of thumb: velocity is the average story points completed per Sprint against the Definition of Done. It is a planning tool, never a performance target.

Worked example: Velocity is 20 points per Sprint and 90 points remain. 90 ÷ 20 = 4.5, so plan for five Sprints and re-inspect.

Business Analysis Frameworks

The Business Analyst's Role

Business analysis identifies business needs and recommends solutions that deliver value. The analyst works across the life cycle: needs assessment (current state, future state, gap), business case and benefits, stakeholder identification, elicitation, requirements analysis, and solution evaluation. Requirements are classified as business requirements (why the organization acts), stakeholder requirements (needs of specific groups), solution requirements split into functional (what the solution does) and nonfunctional (quality attributes such as performance, security, usability), and transition requirements (temporary capabilities needed to move to the future state).

Elicitation and Documentation

Elicitation techniques include interviews, workshops, observation, surveys, document analysis, and prototyping; select based on stakeholder availability, geography, and how well the current process is understood. Requirements must be traced - a traceability matrix links requirements to business objectives, design, and test cases - and prioritized, for example with MoSCoW (must, should, could, won't) or value ordering in a backlog.

Verification versus Validation

Verification asks whether a requirement is documented correctly and consistently. Validation asks whether it represents what the stakeholder actually needs and will deliver value. A requirement can be verified yet still invalid. Traps: confusing a requirement (what is needed) with a design (how it will be built), and gold-plating - adding features nobody requested.

Agile Business Analysis

In adaptive environments a refined backlog and acceptance criteria replace a static requirements document, and analysis is continuous rather than phase-gated.

Rule of thumb: if a statement could be true of any competing solution, it is probably nonfunctional.

Worked example: “The portal must be available 99.9% of each month” is nonfunctional; “the portal must let a customer reset a password” is functional.

CAPM cheat sheet

Quick reference

Project Management Fundamentals and Core Concepts

  • A project is a temporary endeavor undertaken to create a unique product, service, or result; operations are ongoing and repetitive.

  • The PMBOK Guide 7th edition has 12 principles and 8 performance domains: stakeholders, team, development approach and life cycle, planning, project work, delivery, measurement, and uncertainty.

  • Distinguish three terms: project life cycle (phases from initiation to closure), development approach (predictive, hybrid, adaptive), and product life cycle (spans the product's whole life, often beyond the project).

  • Project manager authority increases along this continuum: functional organization < weak matrix < balanced matrix < strong matrix < project-oriented.

  • PMO types and control level: supportive (consulting and templates, low control), controlling (compliance with frameworks, moderate control), directive (PMs report to the PMO, high control).

  • The project charter formally authorizes the project and the project manager; the sponsor issues it before planning starts and it contains high-level scope, objectives, budget, and risks.

  • Tuckman team development stages: forming, storming, norming, performing, adjourning; a team can regress when membership changes.

  • Conflict approaches: collaborate/problem-solve is win-win and best for long-term resolution; compromise is partial; force, avoid, and accommodate produce a winner and a loser.

  • Scope creep is uncontrolled addition of work without change control; gold plating is adding unrequested extras that add no value.

Quick reference

Predictive, Plan-Based Methodologies

  • Predictive (waterfall) life cycle: scope, schedule, and cost are baselined early, and changes flow through Perform Integrated Change Control and the change control board.

  • WBS rules: deliverable-oriented decomposition; the 100 percent rule means child elements fully represent the parent; the lowest level is a work package; the 8-80 rule keeps work packages between 8 and 80 hours.

  • The critical path is the longest duration path through the network and has zero total float; it determines the shortest possible project duration, so any delay on it delays the finish date.

  • Float formulas: total float = LS - ES = LF - EF; free float = early start of successor - early finish of the activity.

  • Precedence Diagramming Method relationships: finish-to-start, start-to-start, finish-to-finish, start-to-finish; a lead overlaps activities, a lag inserts waiting time.

  • Three-point estimating: triangular = (O + M + P)/3; PERT beta = (O + 4M + P)/6; standard deviation = (P - O)/6.

  • Earned value: CV = EV - AC; SV = EV - PV; CPI = EV/AC; SPI = EV/PV; EAC = BAC/CPI when performance persists; ETC = EAC - AC; VAC = BAC - EAC; TCPI = (BAC - EV)/(BAC - AC).

  • Contingency reserve covers identified risks (known unknowns) and is controlled by the project manager; management reserve covers unknown unknowns and generally requires sponsor approval.

  • Risk response strategies: threats - escalate, avoid, transfer, mitigate, accept; opportunities - escalate, exploit, share, enhance, accept; EMV = probability x impact.

Quick reference

Agile Frameworks/Methodologies

  • Agile Manifesto (2001) four values: individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, responding to change over following a plan; items on the right still have value.

  • Agile principles include satisfying the customer through early and continuous delivery, welcoming changing requirements, delivering working software frequently, daily business-developer collaboration, self-organizing teams, sustainable pace, and simplicity.

  • Scrum roles: product owner (maximizes value and orders the backlog), scrum master (servant leader who removes impediments and coaches process), developers (build the increment).

  • Scrum events: sprint (1-4 weeks), sprint planning, daily scrum (15 minutes), sprint review, retrospective; artifacts: product backlog, sprint backlog, increment.

  • The sprint goal gives the sprint its focus; scope may be clarified with the product owner but is not changed arbitrarily once the sprint starts.

  • Kanban core practices: visualize the workflow, limit work in progress, manage flow, make policies explicit, implement feedback loops, improve collaboratively; it is pull-based and requires no fixed iterations.

  • Extreme Programming practices include pair programming, test-driven development, continuous integration, refactoring, small releases, simple design, and collective code ownership.

  • Lean targets waste: overproduction, waiting, transport, overprocessing, inventory, motion, and defects; tools include value stream mapping and kaizen (continuous improvement).

  • Metrics and scaling: velocity forecasts team capacity, burndown shows remaining work, burnup shows completed scope; scaling frameworks include SAFe, LeSS, Scrum@Scale, DSDM, FDD, and Crystal.

Quick reference

Business Analysis Frameworks

  • BABOK Guide knowledge areas (6): business analysis planning and monitoring, elicitation and collaboration, requirements life cycle management, strategy analysis, requirements analysis and design definition, and solution evaluation.

  • BACCM core concepts (6): change, need, solution, stakeholder, value, and context; every business analysis task is performed in relation to all six.

  • Requirement types: business requirements (why the change), stakeholder requirements (what stakeholders need), solution requirements (functional and non-functional), and transition requirements (temporary, for implementation only).

  • Elicitation techniques: interviews, workshops, focus groups, observation/job shadowing, surveys, document analysis, prototyping, brainstorming, and interface analysis.

  • A requirements traceability matrix links each requirement to its source, business need, design components, and test cases, enabling impact analysis and coverage verification.

  • Prioritization approaches: MoSCoW (Must, Should, Could, Won't this time), Kano (must-be, performance, delighter, indifferent, reverse), time-boxing, and voting.

  • User story format: 'As a , I want , so that '; INVEST criteria are Independent, Negotiable, Valuable, Estimable, Small, and Testable.

  • Process and scope models: SIPOC (Suppliers, Inputs, Process, Outputs, Customers), BPMN diagrams, use case diagrams, and context diagrams; compare as-is versus to-be states.

  • Solution evaluation measures delivered value against desired outcomes, assesses solution and enterprise limitations, and recommends actions; cost-benefit analysis and ROI support the business case.

CAPM key terms

Project

A temporary effort undertaken to create a unique product, service, or result. It has a defined beginning and end, and it closes when its objectives are achieved or the effort is terminated.

Related: Project Management, Program
Project Management

The application of knowledge, skills, tools, and techniques to project activities so the project meets its requirements. It coordinates competing demands such as scope, schedule, cost, quality, risk, and stakeholder expectations.

Related: Project, Triple Constraint, Tailoring
Program

A group of related projects and other work managed in a coordinated way to obtain benefits that would not be available if each component were managed separately.

Related: Portfolio, Project
Portfolio

A collection of projects, programs, and other work grouped to support strategic objectives. Components may be unrelated to each other but compete for the same resources and leadership attention.

Related: Program, PMO
PMO

An organizational unit that standardizes governance and shares resources, methods, tools, and techniques across projects. Its authority may be supportive, controlling, or directive depending on how the organization sets it up.

Related: Portfolio, Project Management
Stakeholder

Any person, group, or organization that can affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of the project.

Related: Project Charter, Stakeholder Analysis
Deliverable

Any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project.

Related: Milestone, Definition of Done
Triple Constraint

The interdependent balance among scope, schedule, and cost, often with quality included. Adjusting one usually forces changes in the others, so trade-offs must be made deliberately and documented.

Related: Project Management, Project Charter
Project Charter

A document issued by the sponsor that formally authorizes the existence of a project and gives the project manager authority to apply organizational resources to project activities.

Related: Project Sponsor, Project
Project Life Cycle

The set of phases a project passes through from initiation to closure. The number, names, and sequence of phases vary with the organization and the type of work being delivered.

Related: Project, Deliverable
Tailoring

Deliberately adapting processes, tools, templates, and governance so they fit the size, risk, and complexity of a particular project rather than applying every process uniformly.

Related: Project Management, Agile
Project Sponsor

The senior person who funds or champions the project, provides resources and political support, and approves the charter and major changes. The sponsor is accountable for enabling project success.

Related: Project Charter, Stakeholder
WBS

A hierarchical decomposition of the total scope of work to be carried out by the project team. The lowest levels, called work packages, can be estimated, assigned, and controlled.

Related: Scope Creep, Schedule Baseline
Critical Path Method

A schedule technique that identifies the longest sequence of dependent activities through the network. That path determines the shortest possible project duration, so any delay on it delays the project.

Related: Schedule Baseline, Milestone
Milestone

A significant point or event in the project with zero duration. It marks completion of a key deliverable or a decision point and is used to track high-level progress.

Related: Deliverable, Schedule Baseline
Schedule Baseline

The approved version of the project schedule, including start and finish dates for activities. It is used to compare actual progress against plan and to measure schedule performance.

Related: Critical Path Method, Earned Value Management
Integrated Change Control

The process of reviewing all change requests, approving or rejecting them, and managing changes to deliverables, documents, and the project management plan in a coordinated way.

Related: Scope Creep, Schedule Baseline
Earned Value Management

A technique that combines scope, schedule, and cost measures to assess project performance and forecast future results. It compares the value of work performed against the plan and actual spending.

Related: Schedule Baseline, Integrated Change Control
Risk Register

A document that records identified risks along with their analysis, owners, and planned responses. It is updated throughout the project as risks change or new ones emerge.

Related: Contingency Reserve, Stakeholder
Scope Creep

Uncontrolled expansion of project scope without corresponding adjustments to time, cost, or resources. It usually results from unmanaged change requests and erodes the approved baseline.

Related: Integrated Change Control, WBS
Rolling Wave Planning

An iterative planning approach in which near-term work is detailed while work further out is planned at a higher level and elaborated as more information becomes available.

Related: WBS, Agile
Contingency Reserve

Time or money set aside to cover known risks that have been identified and analyzed. It sits within the approved baseline and is typically released by the project manager as needed.

Related: Risk Register, Schedule Baseline
Agile

An iterative and incremental approach to delivering products that emphasizes collaboration, customer feedback, and the ability to respond to change rather than following a fixed plan.

Related: Sprint, Servant Leadership
Sprint

A fixed-length iteration, typically one to four weeks, during which a scrum team builds a usable and potentially releasable increment of the product.

Related: Product Backlog, Definition of Done
Product Owner

The scrum role responsible for maximizing product value by managing and ordering the product backlog, and by making sure the team understands what to build next.

Related: Product Backlog, Scrum Master
Scrum Master

The role that helps the team and organization apply scrum practices, removes impediments, and coaches the team toward self-management. This is a servant-leader role, not a command-and-control manager.

Related: Servant Leadership, Sprint
Product Backlog

An ordered, evolving list of everything that might be built into the product. The product owner maintains it, and the highest items are refined in detail before entering a sprint.

Related: Product Owner, Sprint Backlog
Sprint Backlog

The set of product backlog items selected for a sprint, together with the team's plan for delivering them. It is owned by the developers and updated as work progresses.

Related: Sprint, Product Backlog
Definition of Done

A shared checklist describing what it means for a product increment to be complete. It creates a common quality standard and prevents unfinished work from being counted as delivered.

Related: Sprint, Acceptance Criteria
Velocity

A measure of how much work a team completes per iteration, usually expressed in story points or backlog items. It supports forecasting only when the definition of done stays consistent.

Related: Sprint, Sprint Backlog
Kanban

A flow-based method that visualizes work on a board, limits how much work is in progress, and manages queues to improve throughput. It does not require fixed-length iterations.

Related: Agile, Sprint
Servant Leadership

A leadership style in which the leader puts the needs and growth of the team first, removes obstacles, and creates conditions that let others do their best work.

Related: Scrum Master, Agile
Business Analysis

The practice of identifying business needs and recommending solutions that deliver value to stakeholders. It covers eliciting requirements, analyzing them, and evaluating whether the solution works.

Related: Requirements Elicitation, Gap Analysis
Requirements Elicitation

The process of drawing out requirements from stakeholders and other sources using techniques such as interviews, workshops, observation, surveys, and document analysis.

Related: Stakeholder, Business Analysis
Functional Requirement

A statement describing what a solution must do, covering the behaviors, inputs, processing, and outputs it must provide in order to meet stakeholder needs.

Related: Nonfunctional Requirement, Acceptance Criteria
Nonfunctional Requirement

A description of how well a solution must perform its functions, covering qualities such as performance, security, usability, reliability, and maintainability.

Related: Functional Requirement, Acceptance Criteria
Requirements Traceability Matrix

A table that links each requirement back to its source and forward to design, build, and test artifacts. It helps confirm every requirement is delivered and nothing unapproved slips in.

Related: Requirements Elicitation, Scope Creep
Acceptance Criteria

The conditions a product increment must satisfy to be accepted by the customer or product owner. They are used to judge whether a requirement has actually been met.

Related: Definition of Done, Functional Requirement
Gap Analysis

A comparison of the current state with the desired future state to identify what is missing. The differences found help justify and shape the recommended solution.

Related: Business Analysis, Requirements Elicitation
Stakeholder Analysis

The process of identifying stakeholders, understanding their interests, influence, and attitudes, and planning how to engage each of them appropriately throughout the work.

Related: Stakeholder, Requirements Elicitation

CAPM study plan

8 weeks · About 6 hours per week

Week 1

Project Management Fundamentals and Core Concepts

  • List and restate in your own words all 12 project management principles and match each to one real project you have observed

  • Differentiate predictive, iterative, incremental, and agile life cycles by drawing the shape of each

  • Map the 8 project performance domains to the principle list and note where they overlap

  • Summarize the four PMI Code of Ethics and Professional Conduct values with one workplace scenario each

Your checkpoint

A one-page hand-drawn map of 12 principles, 8 performance domains, and 4 life-cycle types, plus a 30-question self-quiz scored at 75% or higher

Week 2

Project Management Fundamentals and Core Concepts

  • Contrast project, program, portfolio, and product management with a table of defining characteristics

  • Compare functional, matrix, and projectized organizational structures by authority, reporting, and PM influence

  • Explain the responsibilities of the project manager, sponsor, team, and other stakeholders in each structure

  • Describe how enterprise environmental factors and organizational process assets shape a project

  • Identify what tailoring and benefits realization mean in the context of delivering value

Your checkpoint

A 25-card flashcard set covering roles, structures, and artifacts, with a written 1-page summary of how structure changes PM authority

Week 3

Project Management Fundamentals and Core Concepts & Business Analysis Frameworks

  • Walk through each of the 8 performance domains and state two activities a project manager performs in each

  • Define business analysis and explain how the BA role interacts with the project manager role

  • Outline the steps of a needs assessment and construct a simple business case with costs, benefits, and a go/no-go recommendation

  • Identify stakeholders for a sample project and classify them by influence and interest

Your checkpoint

A written mini business case (1-2 pages) for a fictional project with a stakeholder register of at least 10 entries

Week 4

Business Analysis Frameworks

  • Sequence the requirements life-cycle stages from elicitation through traceability, prioritization, and approval

  • Select appropriate elicitation techniques (interviews, workshops, observation, surveys, document analysis) for given scenarios

  • Construct a requirements traceability matrix linking business needs to requirements to deliverables

  • Distinguish business requirements, stakeholder requirements, solution requirements, and transition requirements

  • Explain how product design and benefits realization connect requirements to value delivery

Your checkpoint

A completed requirements traceability matrix for the week-3 business case with at least 12 requirements categorized by type and priority

Week 5

Agile Frameworks/Methodologies

  • Summarize the Agile Manifesto values and principles and translate each into a team behavior

  • Compare Scrum, Kanban, and XP by roles, ceremonies, artifacts, and when each fits

  • Describe servant leadership and contrast it with command-and-control management

  • Explain how business analysis work is performed on an agile team, including backlog refinement and just-in-time requirements

Your checkpoint

A three-column comparison matrix of Scrum, Kanban, and XP plus a one-page reflection on how the BA role changes in agile

Week 6

Agile Frameworks/Methodologies & Predictive, Plan-Based Methodologies

  • Draft user stories with acceptance criteria and split an epic into at least six stories

  • Estimate using story points and relative sizing, then explain velocity and burndown to a stakeholder

  • Describe hybrid approaches and justify when a predictive life cycle is preferred over an agile one

  • Decompose project scope into a work breakdown structure with at least three levels

  • Identify dependencies and sequence activities into a network diagram with a critical path

Your checkpoint

A product backlog of 10 stories with acceptance criteria, plus a WBS and network diagram for the same project showing the critical path and total duration

Week 7

Predictive, Plan-Based Methodologies

  • Build a cost baseline and calculate planned value, earned value, cost variance, schedule variance, CPI, and SPI from given data

  • Forecast estimate at completion and interpret whether a project is ahead or behind and over or under budget

  • Outline quality management processes and match quality tools to common defects

  • Identify, analyze, and plan responses to risks using a risk register with probability and impact ratings

  • Summarize procurement and stakeholder engagement planning in a predictive project

Your checkpoint

A worked EVM problem set of 15 calculations with written interpretations, plus a 10-item risk register with response strategies

Week 8

Project Management Fundamentals and Core Concepts & Predictive, Plan-Based Methodologies & Agile Frameworks/Methodologies & Business Analysis Frameworks

  • Complete at least two timed full-length practice exams under test conditions

  • Log every missed question by domain and root cause (knowledge gap, misread, or terminology)

  • Re-study the two weakest domains using targeted review notes

  • Recite the exam structure, domain weightings, and question-format rules from memory

  • Build a one-page pre-exam review sheet of formulas, definitions, and principle names

Your checkpoint

A scored practice-exam log showing at least 80% on the final attempt, plus a completed one-page pre-exam review sheet

Milestones

Week 2: Explain all 12 principles and 8 performance domains aloud without notes, and score 75%+ on a 30-question Domain 1 quiz

Week 4: Complete the requirements traceability matrix and pass a 20-question mixed Domain 1 and Domain 4 quiz at 75%+

Week 6: Produce a backlog, WBS, and network diagram for one project and score 75%+ on a 20-question mixed Domain 3 and Domain 2 quiz

Week 8: Score 80%+ on a timed full-length practice exam and show a written weak-area remediation log covering every missed domain

CAPM exam day

Your checklist

Government-issued photo ID with signature

Your name on the ID must match your registration exactly, including spelling and order. If there is any discrepancy, contact PMI before exam day to correct it - do not wait until check-in. Confirm the accepted ID types for your test center with the provider.

Appointment confirmation and PMI eligibility/ID number

Have your appointment details and PMI identification number accessible (printed or on paper, since phones usually stay in a locker). You will need these at check-in.

Second form of identification

Some centers request a second ID, but requirements vary by location and delivery mode. Confirm with the provider whether one or two IDs are required before you travel.

Test center logistics plan

Confirm the exact address, building entrance, parking or transit options, and recommended arrival time. Do a dry run or map review the day before so you are not navigating under time pressure.

Remote-proctoring setup (if testing online)

Complete the provider's system test in advance: webcam, microphone, speakers, browser, and internet stability. Use a quiet, private room with a clear desk and no other people. Confirm the specific room and desk requirements with the provider.

Completed 23 contact hours of project management education

This is an eligibility requirement, not an exam-day item, but verify it is on file and that your application was approved before your appointment. Contact PMI if your application status is unclear.

Knowledge of the exam structure

The CAPM exam is 150 questions delivered in 3 hours, and a portion of those questions are unscored pretest items. Confirm the current question count and time limit with PMI, since PMI periodically updates exam specifications.

Comfort layers and a light snack for after

Testing rooms can be cold or warm. Food and drink are generally not allowed at the workstation, so plan to eat and hydrate before check-in and after the exam.

Leave phone, smartwatch, notes, and study materials at home or in the car

Personal items typically must be stored in a provided locker and are not permitted in the testing room. Fewer items means faster, less stressful check-in.

Restroom and hydration plan

Use the restroom immediately before check-in. Any time away from the workstation generally counts against your exam clock - confirm the provider's break policy on the day.

Backup plan for delays

Build at least 30 minutes of buffer into your travel time. Confirm with the provider what happens if you arrive late, since late arrivals may be denied entry.

A short, single-page formula and terminology warm-up

Bring nothing into the room, but review one page of key formulas and terminology in the car or lobby beforehand - a brief warm-up, not new learning.

Plan the day

Final 72 hours

Reconfirm your appointment date, time, and location (or your remote session details). Verify your ID name matches your registration exactly and resolve any mismatch with PMI immediately. Take one or two timed practice sets under exam conditions rather than starting new material. Build a one-page summary of formulas, agile/BA terminology, and your weakest two or three topics.

Final 72 hours (evening routine)

Shift your sleep schedule so you are alert at your actual appointment time, especially if the exam is early morning. Stop heavy study by the end of this window.

24 hours before

Pack your ID, appointment confirmation, and any permitted items. Confirm travel time and parking. Do a light review of your one-page summary only - no new topics and no full-length mock exams. Eat a normal meal, avoid alcohol, and go to bed at a reasonable hour.

Morning of

Eat a proper meal and hydrate. Leave earlier than you think you need to. If you are testing remotely, complete the check-in and room scan well before your start time and close all other applications. Do not cram - skim your summary once and stop.

At check-in

Follow the proctor's instructions exactly, present your ID, and store personal items in the locker. Ask the proctor about the break policy, scratch materials, and the procedure for flagging questions before the clock starts.

First minutes of the test

Before answering, note the time limit and calculate a rough per-question pace (roughly one minute per question for a 150-question, 3-hour exam). Take a few slow breaths and start with the first question rather than scrolling ahead.

During the test

Answer every question - there is no indication of a penalty for incorrect answers. Flag anything that takes longer than about 90 seconds and move on. If you have scratch materials, write down key formulas at the start while your mind is fresh. Reserve the last 10-15 minutes to revisit flagged items and confirm every question has a response.

After the test

Follow the proctor's exit procedure, collect your belongings, and note your result as reported at the center or in your PMI account. Confirm with PMI how and when unofficial versus official results are released.

Rules to check

  • Bring a valid, unexpired government-issued photo ID with signature. Your name must exactly match your registration. If it does not, contact PMI before exam day - do not assume the proctor can resolve it on site. Confirm accepted ID types with the provider.

  • Personal items - phones, smartwatches, notes, bags, food, and drinks - are generally not permitted at the workstation and must be stored as the proctor directs. Confirm the provider's policy on what may be brought into the testing room.

  • The CAPM exam generally has no scheduled breaks, and the clock typically continues to run if you leave the workstation. Confirm the break policy with your provider before the exam starts.

  • Read and follow all proctor instructions. Failure to comply with testing rules, or any attempt to access unauthorized materials or another person, can result in your exam being voided and may affect your certification eligibility.

  • You will likely be asked to accept a confidentiality agreement covering exam content. Do not discuss, reproduce, or share specific exam questions afterward - this applies to study forums and social media as well.

  • For remote proctoring, expect a room scan, a requirement that no other people be present, and a restriction on leaving the camera view. Confirm the full set of technical and environmental requirements with the provider in advance.

  • Results are typically reported as pass or fail rather than as a numeric score, and a portion of exam questions are unscored pretest items. Confirm the current scoring and reporting method with PMI, since exam specifications change periodically.

  • If you arrive late or experience a technical failure, stop and contact the proctor or provider immediately. Do not attempt to troubleshoot in a way that violates testing rules; confirm the incident policy and any rescheduling options with the provider.

CAPM FAQ

How many CAPM practice questions are available?

The practice set has 200 CAPM questions. Each one includes the choices, the correct answer, and an explanation, and the set is free to read with no signup.

How many CAPM flashcards are available?

The flashcard set has 32 CAPM cards. Each card shows the term and its definition.

Which topics does the CAPM study material cover?

The CAPM study material has 4 sections, including Project Management Fundamentals and Core Concepts, Predictive, Plan-Based Methodologies, and Agile Frameworks and Methodologies.

What format facts does the catalog list for the CAPM exam?

The catalog lists a duration of 180 minutes and these item types: multiple choice for the CAPM exam.