Your FREE Certified Associate in Project Management (CAPM) Practice Test 2026 – 330+ Q&A

Correct answer: To give the project manager formal authority to commit organizational resources to scheduled tasks

Correct answer: To give the project manager formal authority to commit organizational resources to scheduled tasks. The charter formally authorizes the project and grants the manager authority to apply organizational resources; without it the manager has no mandate. A detailed activity schedule is produced later in planning, while the charter holds just a summary milestone schedule. A complete list of requirements comes from requirements collection during planning, whereas the charter records high-level requirements. An itemized cost estimate is built during cost planning, and the charter carries only summary pre-approved financial resources.

Correct answer: Individuals or organizations actively involved in the project, or whose interests may be affected by its outcome

Correct answer: Individuals or organizations actively involved in the project, or whose interests may be affected by its outcome. The term covers every party with a stake, whether they work on the project or simply feel its effects, favorable or adverse. Contractors or consultants formally retained are only the supplier subset. Executives or directors personally accountable describe sponsors and governance bodies, again a subset. Developers or engineers repeatedly assigned name the delivery team alone. Each of those three narrows the definition to one group, which is the error the question tests.

Correct answer: Team members are grouped by their specialist discipline and report to the permanent head of that department

Correct answer: Team members are grouped by their specialist discipline and report to the permanent head of that department. A functional structure organizes staff by skill - engineering, marketing, finance - under a standing departmental head, which favors deep specialization but complicates cross-department project work. Grouping by immediate assignment under a temporary lead describes a projectized structure instead. Grouping by geographic location under a regional director describes a geographic divisional structure. Grouping by customer contract under a commercial leader describes an account-based divisional structure. None of those three groups people by skill.

Correct answer: Project team members report to a functional manager and to a project manager in parallel

Correct answer: Project team members report to a functional manager and to a project manager in parallel. A matrix organization is defined by that dual reporting line, which lets specialists stay in their home department while serving a project. Reporting to a project manager who also controls the budget and staff describes a projectized organization with a single chain of command. Reporting to a department head and doing project work beside daily duties describes a functional organization with no project manager in the reporting line. Reporting to a project management office that sets daily tasks describes a directive PMO arrangement, which is still one reporting line rather than two.

Correct answer: 20% of the work consumes 80% of the project time and resources

Correct answer: 20% of the work consumes 80% of the project time and resources. The Pareto Principle is the 80/20 rule: a small minority of causes accounts for most of the effects, which is why managers focus on the vital few first. The statement that 100% of the scope is contained in the work breakdown structure is the 100% rule for building a WBS, not Pareto. Crediting 50% of the earned value on starting a work package is the 50/50 rule for measuring earned value progress. The claim that 68% of the values fall within 1 standard deviation of the mean is the empirical rule for a normal distribution, used in estimating and quality control.

Correct answer: The uncontrolled growth of project scope without parallel changes to time, cost, and resources

Correct answer: The uncontrolled growth of project scope without parallel changes to time, cost, and resources. Scope creep is unauthorized expansion that arrives one small request at a time while the schedule and budget stay fixed, which is why it ends in overruns. The gradual slippage of the project schedule is a delay, which scope creep can cause but which is not the growth of scope itself. The steady rise in actual project costs from inflation is cost escalation driven by market prices while the scope stays the same. The planned breakdown of approved deliverables into work packages is decomposition, an authorized planning step that adds no new work.

Correct answer: Planning process group

Correct answer: Planning process group. Planning is where objectives are defined and refined and the course of action to reach them is chosen, covering scope, schedule, cost, quality, resources, risk and procurement. The Initiating process group only authorizes the project and identifies stakeholders; objectives are not yet refined there. The Monitoring process group tracks work against a plan that already exists rather than creating one. The Closing process group finalizes and hands over completed work. Only Planning builds the courses of action.

Correct answer: Projects are ever-present routine operations.

Correct answer: Projects are ever-present routine operations. This is the statement that is NOT true of a project: repetitive, permanent work of that kind is operations, and a project is precisely what operations are not. Being purpose-driven and targeted is true, since every project has defined objectives. Being time-boxed and temporary is true, since a project has a definite beginning and end. Being one-off and unrepeated is true, since a project creates a unique product, service or result.

Correct answer: The broad degree to which the organization is ready to pursue risk, judged by its investment choices

Correct answer: The broad degree to which the organization is ready to pursue risk, judged by its investment choices. Risk appetite is an attitude - how much risk the organization is prepared to take on in pursuit of reward, shown most clearly in the investments it chooses. The exact limit it is content to carry is risk tolerance, a narrower and measurable idea. The total volume it is able to absorb is risk capacity, set by its finances rather than its attitude. The fixed point at which it must report risk is a risk threshold, a trigger for action rather than a disposition.

Correct answer: The process of sourcing, obtaining, and managing external goods and suppliers for the project

Correct answer: The process of sourcing, obtaining, and managing external goods and suppliers for the project. Procurement management covers everything needed to buy or acquire products, services and results from outside the performing organization, including planning purchases, running the solicitation and administering the contracts. Tracking and projecting internal costs and budgets is cost management. Housing and servicing physical assets and equipment is resource management of things already owned. Hiring and directing assigned staff and specialists is team management, which deals with people inside the project rather than outside sellers.

Correct answer: Recording identified project risk entries along with their descriptive features

Correct answer: Recording identified project risk entries along with their descriptive features. The register is the repository created by risk identification: each entry carries a description, a category, causes, probability, impact and later a response. Approving forecast risk budgets and contingency allowances is reserve management, a cost decision. Scheduling periodic reviews and expected participants is a governance calendar item, not the register's content. Assigning trained custodians with contractual mandates names one field the register may hold, but it is not what the register is primarily used for.

Correct answer: It weighs the value a project returns against the money it consumes

Correct answer: It weighs the value a project returns against the money it consumes. The benefit cost ratio divides the present value of expected benefits by the present value of expected costs, and a ratio above one indicates a project worth funding, which is why it is used to compare candidates during selection. Weighing the cash a project recovers against the years it requires is the payback period. Weighing the return a project yields against the hurdle it targets is internal rate of return compared with a hurdle rate. Weighing the costs a project incurs against the budget it forecast is cost variance tracking during execution, not a selection measure.

Correct answer: To record which people receive which information, at what time, and by what channel

Correct answer: To record which people receive which information, at what time, and by what channel. The matrix answers the four communication questions - who, what, when and how - so that every stakeholder gets the right report through the right medium. Deciding which vendors supply information at what price is a procurement schedule. Fixing which auditors review information at what depth is an audit plan. Measuring which sponsors retain information is a comprehension survey, not a distribution instrument. Only the first defines the flow of information.

Correct answer: Coordinating the separate parts of the project plan to ensure cohesive delivery

Correct answer: Coordinating the separate parts of the project plan to ensure cohesive delivery. Integration management is the knowledge area that ties scope, schedule, cost, quality, resources, communications, risk, procurement and stakeholders into one coherent plan and one controlled change process. Controlling the financial parts to ensure accurate budgets is cost management. Improving wasteful parts for faster throughput is process improvement, not integration. Installing modern toolset parts is a technology decision that no knowledge area treats as its purpose.

Correct answer: They are costs that have already been spent and remain wholly unrecoverable.

Correct answer: They are costs that have already been spent and remain wholly unrecoverable. Because that money is gone whatever is decided next, sunk costs should be left out of any continue-or-cancel decision; counting them leads to the sunk cost fallacy. Costs estimated to complete the outstanding scope are the estimate to complete, a future cost that does belong in the decision. Costs held in reserve for identified risks are contingency reserves, which have not been spent and can still be released. The benefit lost by skipping the next best option is opportunity cost, which looks forward at alternatives rather than back at money already gone.

Correct answer: Define duties and accountabilities in task completion.

Correct answer: Define duties and accountabilities in task completion. A responsibility assignment chart maps each deliverable to the people who are Responsible, Accountable, Consulted and Informed, so nobody is left guessing who does the work and who signs it off. Comparing quotes and qualifications in vendor selection is a source selection matrix. Assembling stages and dependencies in schedule analysis is network diagramming. Capturing hazards and consequences in defect prevention is a failure mode analysis. None of those three assigns accountability.

Correct answer: Risks that emerge as a direct result of applying a chosen response

Correct answer: Risks that emerge as a direct result of applying a chosen response. A secondary risk is created by the response itself, as when transferring a threat to an insurer introduces counterparty exposure, so it has to be identified, analyzed and given a response of its own. Risks that surface as a fresh concern of entering a closed project are simply risks identified late; timing of discovery has nothing to do with what caused them. Risks that register as a slight threat of missing a stated outcome are low-impact risks, which is a severity rating rather than an origin. Risks that stand as a remote chance of troubling a future delivery are low-probability risks, again a rating and not a consequence of any response.

Correct answer: Refine the project plan in steps as fuller detail becomes available

Correct answer: Refine the project plan in steps as fuller detail becomes available. Progressive elaboration accepts that a project cannot be planned completely at the outset, so planning and documentation are developed in successive passes and made more detailed as information is learned. Shrinking the project scope in stages as budget pressure mounts is descoping, a response to a constraint rather than a planning technique. Boosting the project output in cycles as members gain momentum describes a learning curve, which is an effect on productivity and not a planning method. Expanding the project risks in waves as later phases progress is rolling risk identification, only one narrow slice of what progressive elaboration covers.

Correct answer: To ensure that project information is created, gathered, and shared

Correct answer: To ensure that project information is created, gathered, and shared. Manage Communications is the executing process that makes timely generation, collection, distribution, storage and retrieval of project information happen, so that stakeholders inside and outside the team actually receive what they need. Validating that spending is tracked, checked and reported belongs to Control Costs and moves money data, not messages. Confirming that staffing is planned, briefed and appraised sits in resource management and concerns people rather than information flow. Requiring that paperwork is sorted, indexed and retrieved is records administration, a storage activity that by itself delivers nothing to any stakeholder.

Correct answer: It supports live feedback and quick correction

Correct answer: It supports live feedback and quick correction. Interactive communication is a multidirectional exchange between two or more parties in real time, which lets a misunderstanding be surfaced and repaired inside the same conversation and is why it suits complex or sensitive topics. Carrying light overheads and smaller budgets describes push communication such as a circulated memo, which is cheap precisely because nobody has to attend. Reaching scattered readers and distant sites is the strength of pull communication like an intranet repository. Needing minimal hardware and standard cabling is an infrastructure point, and interactive methods usually demand more equipment rather than less.

Correct answer: The upfront Planning process group

Correct answer: The upfront Planning process group. Develop Project Management Plan sits in this group, which defines objectives and scope and produces every subsidiary plan and baseline, and the integrated result is approved before execution starts. The early Initiating process group authorizes the project through the charter and identifies stakeholders; it precedes the plan and does not contain it. The active Executing process group spends the plan by directing the work and no longer writes it. The eventual Closing process group finalizes records and releases resources, so it sits at the opposite end of the life cycle.

Correct answer: To assign and specify duties and accountabilities in project work

A Responsibility Assignment Matrix such as a RACI chart exists to assign and specify duties and accountabilities in project work, marking for every activity who is responsible, who is accountable, who is consulted and who is informed. Gauging stakeholder power and interest is done with a power/interest grid during stakeholder analysis. Documenting reporting lines and hierarchy is the purpose of an organization chart, which shows who reports to whom rather than who does what. Breaking down the project's scope and grouping it into work packages is the work breakdown structure, which defines the work but assigns no one to it.

Correct answer: A temporary effort undertaken to generate a unique product, service, or result

The standard definition is a temporary effort undertaken to generate a unique product, service, or result, and the two words carrying the weight are temporary, meaning a definite start and finish, and unique, meaning the output has not been produced before. An ongoing operation performed to sustain a routine product, service, or process describes operations, which continue indefinitely and repeat the same work. A set of linked projects managed jointly to realize a benefit, gain, or capability is the definition of a program, which groups projects rather than describing a single one. A collection of programs chosen to meet a strategic goal, target, or priority describes a portfolio, the level at which an organization selects and balances its investments.

Correct answer: Project, program, portfolio

In order the three tiers are project, program, portfolio: the single app launch is one project, the coordinated set of related apps run together for shared benefits is a program, and the full collection ranked against strategic goals is a portfolio. Portfolio, program, venture reverses the hierarchy and puts the broadest tier first. Mission, portfolio, program places the collection in the middle, which cannot be right because the collection is the widest container. Portfolio, package, program again starts at the top and leaves the coordinated group of related efforts at the narrowest level.

Correct answer: Initiating, Planning, Executing, Monitoring and Controlling, Closing

The five process groups are Initiating, Planning, Executing, Monitoring and Controlling, Closing, and they are logical groupings of activity that recur within every phase rather than a single pass through the work. Conception, Definition, Development, Testing and Deployment, Signoff names life-cycle phases of a product, which describe what is being built rather than how the work is managed. Discovery, Appraisal, Prototyping, Building and Publishing, Handover is a generic delivery sequence. Chartering, Scoping, Scheduling, Budgeting and Management, Clearance lists planning outputs and management tasks, none of which is a recognized process group.

Correct answer: The stakeholder register

The list of people and their attributes belongs in the stakeholder register, which identifies each party and records their role, interest, expectations and influence. The communication matrix sets out what information goes to whom, how often and in which format, so it follows from the register rather than holding it. The engagement checklist tracks the actions taken to move people toward the involvement the project wants, which is activity rather than identity. The relocation timetable orders the moves by date and never records who is affected or how much sway they hold.

Correct answer: Any individual or group that can impact, be impacted by, or consider itself to be impacted by the project

A stakeholder is any individual or group that can impact, be impacted by, or consider itself to be impacted by the project, and the third clause matters because a belief in being impacted creates real concerns that still have to be managed. Any vendor or buyer that can charge, be reimbursed by, or register itself to be reimbursed by the project limits the idea to commercial counterparties. Any volunteer or team that can approve, be appraised by, or nominate itself to be rostered by the project restricts it to people inside the performing organization. Any regulator or auditor that can inspect, be briefed by, or declare itself to be licensed by the project covers only oversight bodies, leaving out customers, users and the team.

Correct answer: Scope creep; redirect each new request through the formal change control process

Scope creep; redirect each new request through the formal change control process is correct: additions absorbed without revising the plan are scope creep, and change control makes sure each request's effect on time, cost, and quality is assessed and approved before any work starts. Gold plating is the team adding extras nobody asked for, and quietly absorbing sponsor-endorsed extras is exactly the behavior that has to stop. Progressive elaboration adds detail to work already inside the approved scope, so treating new features as refinements hides genuine scope growth. Rolling wave planning details near-term work in stages, and deferring new features to a later cycle still adds them without an approved change.

Correct answer: The sum of the products, services, and results that are to be provided plus the work to produce them

Scope is the sum of the products, services, and results that are to be provided, together with the work to produce them; it is what answers the question of what is and is not included. A calendar of dates, reviews, and approvals describes the schedule, which says when the agreed work happens rather than what it is. A catalog of threats, issues, and gaps describes the risk picture, which is about uncertainty around the work. A budget of funds, rates, and reserves describes cost. All three are constrained by scope, and none of them defines it.

Correct answer: Predictive approaches settle the scope through formal early change control, while agile approaches evolve the requirements through repeated short cycles

The accurate contrast is that predictive approaches settle the scope through formal early change control, while agile approaches evolve the requirements through repeated short iterations; predictive work suits stable requirements and agile work suits high uncertainty. It is not predictive work that leaves scope open to informal edits, nor agile work that forces requirements into one rigid plan, so that pairing reverses both halves. The two are not identical methods separated only by phase length, because they treat change in fundamentally different ways. And agile teams release value during the work and still produce the documentation their product needs, so the final claim is wrong on both counts.

Correct answer: A hybrid approach

A hybrid approach is the name for running a plan-based method on the stable hardware alongside iterative delivery on the volatile software within the same project. An agile approach would apply iterations to everything, including the hardware the team chose to plan predictively. A spiral approach is a single risk-driven life cycle that loops through repeated prototypes, not a combination of two methods. A staged approach divides one plan-driven method into sequential stages with reviews between them, leaving no part of the work run iteratively.

Correct answer: The project life cycle

The broad series of stages a project passes through from start to finish, whatever method is chosen, is the project life cycle, and it is the frame inside which all the work is organized. A change log records the requests that have been raised and the decisions taken on them, which is a record of events rather than a series of stages. A phase gate is one decision point sitting between two stages, so it is a part of the series and not the series itself. A scope tree breaks deliverables down into smaller parcels of work and says nothing about how the project progresses over time.

Correct answer: The project life cycle phases

Starting the project, organizing and preparing, carrying out the work, and ending the project are the generic project life cycle phases, which are time-bound stages describing where the work has reached. The process group phases are logical groupings of management activity that recur inside any stage, so they are not a sequence of stages at all. The triple scope cost balance names the competing demands that trade off against one another, not the progression of the work. Project review gates are decision points held between stages rather than the stages themselves.

Correct answer: Scope, schedule, and cost

The classic triple constraint is scope, schedule, and cost: move one of them and at least one of the others has to give, with quality usually drawn as the result of how the three are balanced. Plan, execute, and close name stages of a project life cycle, which follow one another in sequence rather than trading off. People, process, and tools is a model for building organizational capability, not a set of project constraints. Risks, issues, and decisions are entries kept in a project log, which are tracked and managed but do not form the classic trade-off relationship.

Correct answer: High-level requirements, objectives, a summary milestone schedule, the assigned project manager, and the sponsor authorization

A charter carries high-level requirements, objectives, a summary milestone schedule, the assigned project manager, and the sponsor authorization that formally brings the project into being, and it is deliberately high level because it is written before detailed planning happens. Detailed activity estimates, resource calendars, a baselined cost budget, quality metrics, and the change control procedure are outputs of planning that cannot exist yet. Final acceptance records, lessons learned, a closing performance report, archived files, and released resources belong to closure at the end of the project. Work package definitions, control accounts, a decomposed work breakdown structure, the WBS dictionary, and project exclusions make up the scope baseline built during planning, so it too comes after the charter is signed.

Correct answer: The project charter

The project charter is the document a sponsor signs to formally authorize the project and name the project manager, giving that person authority to apply organizational resources. The business case justifies the investment and feeds into the charter, but it authorizes nothing and names no project manager. The scope statement is produced during planning to describe deliverables and boundaries, after the project already exists. The management plan is built by the project manager during planning to define how the work will be run, so it cannot be the document that appointed that manager.

Correct answer: A deliverable

A unique and verifiable product, result, or capability produced to complete a process, phase, or project is a deliverable, and that is what the team is handing over. A requirement is a stated condition the output has to satisfy, so it describes what the thing must do rather than being the thing itself. A measurement is a recorded value taken about the output and is not the output. A contingency is an allowance of time or money held back against uncertainty, which is neither produced nor handed over for verification.

Correct answer: Milestones; they mark the significant moments and carry zero duration of their own

Milestones; they mark the significant moments and carry zero duration of their own is correct: a milestone such as design approved or system go-live flags an event and consumes no time or resources. Deliverables are the products or results the project hands over, whereas the points in the stem mark events rather than outputs. Summary tasks roll up their child activities and span the combined duration, so they are not zero-duration points. Lags add waiting time between linked activities, which means they have duration and mark no event.

Correct answer: The lessons learned register

The artifact that consolidates what went well, what went poorly, and the improvements recommended for future work is the lessons learned register; it is built up as the work proceeds and finalized so the organization can reuse the knowledge. A risk breakdown structure is a hierarchy of risk categories used during planning, not a record of experience. A final performance report summarizes how the work measured against its baselines and does not gather recommendations for other projects. A formal acceptance record is the customer's confirmation that deliverables meet their criteria, which settles ownership rather than capturing knowledge.

Correct answer: Continuously throughout the whole project, then finalized at closure

Continuously throughout the whole project, then finalized at closure is the right cadence, because knowledge is captured best while it is fresh and while the current team can still act on it. Updating solely during project closeout loses the detail that made each lesson useful and gives the current team no chance to apply it. Recording entries shortly after major risk events narrows the register to problems and misses what went well day to day. Updating formally at phase gate reviews leaves long gaps, so much of what happened inside each phase is forgotten before anyone records it.

Correct answer: A RACI matrix

A RACI matrix is the chart that states, task by task, who is Responsible for doing the work, who is Accountable for the outcome, who is Consulted for input, and who is Informed of progress. A WBS diagram decomposes the deliverables into ever smaller parcels of work and names no people at all. A CPM network shows how activities depend on one another and where the longest path runs, so it answers questions about sequence and float rather than ownership. A SIPOC chart maps suppliers, inputs, process, outputs, and customers for a process rather than assigning roles across tasks.

Correct answer: Exactly one person should be Accountable for a specific task

Exactly one person should be Accountable for a specific task, because a single point of answerability is what keeps ownership unambiguous. Spreading the Accountable role across four people reproduces the confusion the matrix exists to remove, since nobody then answers for the result. Leaving the role unassigned removes answerability altogether and makes the row of the matrix useless. Being Consulted means being asked for input, which is a separate and much lighter involvement, so it does not carry answerability with it.

Correct answer: A responsibility assignment matrix

A grid that ties each package or activity to the people who will carry it out is generically a responsibility assignment matrix, and RACI is simply one popular form of it. A hierarchical decomposition chart breaks scope down into smaller parcels of deliverable work but assigns none of it to anyone. An integrated performance baseline combines the approved scope, schedule, and cost measures used to judge progress, so it is a yardstick rather than an allocation of duties. An incremental burndown projection plots work still outstanding against time and identifies nobody.

Correct answer: The sponsor supplies resources, funding, and high-level backing, while the project manager runs the day-to-day work to reach objectives

The sponsor supplies resources, funding, and high-level backing and champions the work inside the organization, while the project manager runs the day-to-day effort to reach the objectives. Reversing that, so the sponsor tracks timesheets and the manager signs the funding, swaps the two roles completely. Putting the sponsor on the daily schedule while the manager merely attends a weekly status makes the manager a spectator on work that is theirs to run. And the roles are not interchangeable: one authorizes and protects the project, the other delivers it, and combining them removes the independent oversight the sponsor exists to give.

Correct answer: A risk register

The single place that holds each identified uncertainty with its description, probability, impact, owner, and planned response is a risk register, and it is maintained for the life of the work. A change ledger records requests to alter what was agreed, along with the decision taken on each, which is a different kind of entry entirely. A defect report captures faults already found in a deliverable, so it deals with what has happened rather than what might. A scope summary states what is and is not included in the work and carries no probabilities, owners, or responses.

Correct answer: The avoid strategy

Redesigning so the vendor is no longer needed removes the threat completely, and eliminating a threat by changing the plan is the avoid strategy. Transfer moves the impact to a third party through insurance or a contract clause, leaving the threat in existence and merely paying someone else to carry it. Mitigate lowers the probability or the impact but still leaves some exposure behind. Escalate hands the threat to a level of authority outside the project because it sits beyond the team's remit, which is not what the team did here.

Correct answer: The exploit strategy

Taking deliberate action to make certain that an opportunity actually happens is the exploit strategy, the opportunity response that removes the uncertainty by locking the upside in. Mitigate is a threat response that lowers probability or impact, so it works against an outcome rather than securing one. Escalate applies to either threats or opportunities but means handing the item to a higher authority instead of acting on it. Transfer is likewise a threat response, shifting an unwanted impact to a third party rather than realizing a benefit.

Correct answer: Avoid, transfer, mitigate, escalate, and accept

The recognized responses to threats are avoid, transfer, mitigate, escalate, and accept. Exploit, enhance, and promote belong to the opportunity side of the register, where the aim is to secure a benefit rather than remove an unwanted outcome. Prepare, develop, execute, evaluate, and refine describe a continuous improvement cycle used to strengthen a process, not a set of risk responses. Initiate, organize, execute, monitor, and close name the way management activity is grouped across a project and say nothing about how a specific threat is handled.

Correct answer: The outcomes and value it delivers to stakeholders

Current guidance judges a project by the outcomes and value it delivers to stakeholders, because outputs finished on time and on budget are worth little if nobody benefits from them. Meeting deadlines and budget for sponsors is the traditional constraint view, which measures delivery performance rather than benefit. Following processes and standards measures compliance, which can be flawless while value is missing. Velocity and efficiency each sprint measure team throughput, an output indicator that can rise while delivered value falls.

Correct answer: Servant leadership; it enables teams and is integral to agile and value-driven delivery

Clearing obstacles, supplying what the team needs, and enabling their best work is servant leadership, and it is emphasized because it enables self-managing teams and is integral to agile and value-driven delivery. Autocratic leadership centralizes decisions in one person and issues instructions, which is the commanding posture the manager here has explicitly rejected. Transactional leadership drives behavior through rewards and penalties rather than through support. Laissez-faire leadership withdraws the leader altogether, which is not the same as actively removing impediments on the team's behalf.

Correct answer: Tailoring

Adapting processes, governance, and the life cycle to suit a project's context, size, and risk is the tailoring principle, which holds that no single method fits every project. Governing is the oversight function that sets the rules a project works within, so it is one of the things being tailored rather than the act of tailoring. Levelling adjusts the schedule so resource demand stays inside available supply, which is a scheduling technique with no bearing on method selection. Reporting communicates status to those who need it and changes nothing about how the work is organized.

Correct answer: Recognize and address the interactions among the project parts and its environment

Systems thinking asks the team to recognize and address the interactions among the parts of the project and its surrounding environment, because a change in one area ripples into others. Treating expenditure as the thing to calculate and prioritize reduces a whole system to one variable and hides those ripples. Postponing and suppressing discussion cuts the project off from the very environment systems thinking says to watch. Cataloguing assignments in isolation is the opposite of a holistic view, since it examines each component as though nothing else touched it.

Correct answer: Ongoing, proactive engagement helps satisfy stakeholders and boosts project success and value

Ongoing, proactive engagement is what satisfies stakeholders and boosts project success and value, because needs surface early, support is built while it still matters, and costly rework is avoided. Delaying engagement to avoid alarming people trades a small early conversation for a large late one and usually costs more time than it saves. Treating engagement as a procedural box to tick leaves the real interests of stakeholders untouched, so the project learns nothing from it. Engaging only once a crisis has broken means every correction arrives after the damage, which is exactly the pattern the principle is written to prevent.

Correct answer: Outputs are the deliverables produced, while outcomes are the changes or benefits they enable

Outputs are the deliverables produced, while outcomes are the changes or benefits they enable; a new booking system is an output, and the shorter queues it causes are an outcome. Calling outputs the benefits gained and outcomes the work products behind them reverses the relationship, since benefits are what the products cause. Treating outputs as planned targets and outcomes as actual figures confuses the distinction with plan-versus-actual variance. Splitting outputs into internal documents and outcomes into products users receive still describes two kinds of deliverable, and neither one is a change or benefit.

Correct answer: The process groups are not strictly sequential phases; they overlap and can repeat as needed

The process groups are not strictly sequential phases; they overlap and can repeat as needed, so planning happens again whenever new information arrives. Matching them to life-cycle phases that end before the next starts confuses two ideas, since phases are time-bound stages of the work while the groups are clusters of management activity that can appear inside any stage. Setting them aside on agile work is wrong because initiating, planning, executing, monitoring, and closing activity still occurs in agile and hybrid delivery. Running them once in order and restarting only on a rebaseline describes a rigid waterfall, when in practice the groups interact continuously throughout the project.

Correct answer: Equip and support those affected so change is embraced and benefits are sustained

The change principle asks the team to equip and support the people affected so that the change is actually embraced and its benefits are sustained; a delivered change nobody takes up produces no value. Concealing a change and rushing it through creates the resistance that later stalls adoption. Obstructing change to protect an existing baseline confuses the plan with the purpose, since plans exist to serve outcomes rather than the reverse. Treating every change as a threat to be eliminated ignores that well-managed change is the mechanism by which projects deliver improvement at all.

Correct answer: The project management plan

The comprehensive, integrated document describing how the work will be executed, monitored, controlled, and closed is the project management plan, which binds the subsidiary plans and the baselines into one whole. A scope statement details what is and is not included in the deliverables and covers none of the executing or controlling arrangements. A charter summary restates the high-level authorization written before planning began, so it cannot describe how the work will be run. A budget forecast projects cost over time and is one input to the integrated plan rather than the plan itself.

Correct answer: Business analysis focuses on defining and managing requirements, complementing the project management focus on delivering the work

Business analysis focuses on eliciting, defining, and managing requirements so the right solution is built, and it complements project management, whose focus is delivering that solution effectively. It does not supersede project management: the two disciplines run alongside each other, and removing the delivery role would leave the requirements unbuilt. It is not a duplicate scheduling function either, since sequencing activities and setting deadlines sit squarely with the project manager. And it does not begin after delivery, because the greatest influence of requirements work is at the earliest stages, before anything has been built.

Correct answer: Quality built into processes and deliverables to meet stakeholder requirements and expectations

Focusing on quality means building it into both the processes and the deliverables so they meet stakeholder requirements and expectations, rather than hoping to find problems later. Inspecting finished consignments detects defects after the cost of making them has already been paid, which is the reactive posture the principle replaces. Letting quality be dictated by one person's individual preferences substitutes taste for the agreed criteria that stakeholders actually set. Postponing quality to preserve a pressing deadline usually costs more than it saves, because rework and warranty effort return the time with interest.

Correct answer: Stewardship

Stewardship is the principle that calls on a team to act as careful, responsible, and ethical caretakers of the resources and the trust placed in them, inside and outside the organization. Sponsorship names the funding and championing role a senior executive performs, not a principle of conduct. Partnership describes a commercial relationship between two organizations. Supervision is routine oversight of how people carry out assigned work. None of those three is a principle about responsible caretaking.

Correct answer: Complexity navigation

Complexity navigation is the principle for operating effectively where many interdependent parts, ambiguity, and unpredictable behavior meet; it asks teams to recognize the sources of complexity, such as human behavior and system interactions, and to respond as they emerge. Complexity prevention is wrong because complexity in a system of interacting parts cannot be designed away in advance. Complexity delegation is wrong because handing the situation to another party leaves it unmanaged. Complexity absorption is wrong because quietly tolerating the effects is not a recognized principle.

Correct answer: Assumptions and constraints

Assumptions and constraints is the correct pairing: an assumption is a factor treated as true without proof and validated later, while a constraint is a limiting factor such as a fixed deadline, budget, or regulation. Requirements and objectives state what the product must do and what the project must achieve, not what is believed or what limits the team. Estimates and prerequisites are predicted values and entry conditions for starting work. Milestones and dependencies mark zero-duration schedule events and logical relationships between activities.

Correct answer: The rollout, because it is a temporary endeavor that yields a unique result

The rollout is the project, because a project is a temporary endeavor undertaken to create a unique product, service, or result; the six-month portal work has a defined beginning and end and produces something new. The ticket answer is wrong because repeated work serving a steady stream of customers is operations, not a project. The launch answer is wrong because the portal work is not a continual program renewed under a yearly contract; it stops when the portal is delivered. The operation answer is wrong because a permanent team with a stable headcount is ongoing business as usual.

Correct answer: The coordinated effort is a program; the broader grouping is a portfolio

The coordinated effort is a program; the broader grouping is a portfolio. A program is a group of related projects managed in a coordinated way to obtain benefits not available from managing them individually, while a portfolio is the collection of projects, programs, and operations selected to achieve strategic objectives. Calling the related projects a portfolio and the wider collection a program reverses the two definitions. Calling the single effort a big project ignores that several separate projects are managed together, and a strategic selection of initiatives is a portfolio rather than a program. Calling the managed projects a portfolio misnames the program, and a PMO is an organizational body that supports project management, not a collection of initiatives.

Correct answer: Initiating, Planning, Executing, Monitoring and Controlling, Closing

The five process groups are Initiating, Planning, Executing, Monitoring and Controlling, Closing. They are logical groupings of project management activities rather than sequential phases of a product. Planning, Analyzing, Designing, Developing and Verifying, Delivering describes the phases of a development life cycle for building a product. Identifying, Analyzing, Treating, Monitoring and Reviewing, Auditing describes the steps of a risk management cycle. Proposing, Reviewing, Approving, Implementing and Verifying, Closing describes how a single change request moves through change control.

Correct answer: The project charter

The project charter provides that authorization: it is the document that formally authorizes the existence of the project, gives the project manager the authority to apply organizational resources, and records who that manager is. The scope statement is a planning output that details deliverables and exclusions only after the work is authorized. The project roadmap shows high-level timing and hands nobody any spending or staffing authority. The benefit summary records the value the work is expected to return and appoints no one.

Correct answer: Overall purpose, measurable objectives, summary milestones, and the project manager

Overall purpose, measurable objectives, summary milestones, and the project manager is the right set: a charter records the high-level purpose or justification, measurable objectives and success criteria, summary milestones, high-level requirements and risks, and the assigned project manager together with that manager's authority level. Detailed durations, approved baselines, tested integrations, and the final contract are planning and procurement outputs produced well after the charter. Completed requirements, scripted acceptance, reviewed records, and the risk manager belong to detailed analysis and testing. Summarized lessons, finalized handover, archived receipts, and the project outcomes are closing outputs.

Correct answer: Value

Value is the concept being described. The PMBOK Guide Seventh Edition defines value as the worth, importance, or usefulness of something, and it is what a project ultimately exists to deliver. Cost is the monetary resources spent to carry out the work, which is an input rather than the worth produced. Quality is the degree to which a set of inherent characteristics fulfills requirements, a measure of conformance rather than worth. Outcome is an end result or consequence of a process or project, which may or may not deliver value to stakeholders.

Correct answer: Predictive delivery, driven by a stable baseline

Predictive delivery, driven by a stable baseline, is the right fit: when requirements are well understood and the customer wants scope, schedule, and cost settled at the outset, a plan-based life cycle is the one that matches. Adaptive delivery steered by a variable roadmap suits volatile requirements, which is the opposite of the situation described. Iterative delivery reworked by a ranked backlog assumes the solution will be reshaped repeatedly as understanding grows. Incremental delivery scaled by a staged rollout releases usable pieces over time instead of committing the whole plan early.

Correct answer: Predictive sets scope and schedule early and resists change; agile delivers short iterations and welcomes new requirements

The accurate statement is: Predictive sets scope and schedule early and resists change; agile delivers short iterations and welcomes new requirements. Saying predictive ships working increments at regular intervals while agile freezes the approved scope reverses the two approaches. Saying predictive keeps documentation light while agile depends on detailed contracts also reverses them, since agile values customer collaboration over contract negotiation. Saying predictive suits small software teams while agile suits large construction programs flips the usual fit, because stable, well-defined construction work is where predictive planning is most common.

Correct answer: The sequence of phases a project runs through from start to completion

The sequence of phases a project runs through from start to completion is the life cycle; it gives the basic framework for managing the work from initiation to closure whatever the industry. The steps of purchases a project works through from invoice to closure describe a procurement cycle, which is only one thread of the work. The totals of spending a budget tracks through from forecast to actual describe cost control and earned value reporting. The list of parties a register carries through from kickoff to signoff describes the stakeholder register.

Correct answer: Starting the effort, organizing and preparing, performing the work, and ending the project

Starting the effort, organizing and preparing, performing the work, and ending the project is the typical generic life cycle; those four high-level phases describe the flow of any project whatever it delivers. Compiling the budget, reviewing and approving, tracking the cost, and storing the accounts describes a finance routine that runs inside a project rather than framing it. Marketing the project, selling and shipping, invoicing the buyer, and serving the customer describes commercial business functions. Recruiting the staff, training and coaching, assessing the team, and promoting the leaders describes a human resources process.

Correct answer: A RACI matrix

A RACI matrix is the tool that clarifies these roles: it is a responsibility assignment matrix mapping people to deliverables as Responsible, Accountable, Consulted, or Informed, which is exactly the accountable-versus-informed distinction the manager wants. A WBS diagram decomposes the work into smaller packages and never says who owns them. A PERT chart sequences activities and estimates their durations, a scheduling result rather than a role assignment. A RAID tracker logs risks, assumptions, issues and dependencies, and even where entries carry an owner it does not separate who is accountable from who is merely informed.

Correct answer: Accountable, and exactly one person should own each deliverable

Accountable, and exactly one person should own each deliverable, is the rule: a single accountable owner prevents confusion over who answers for the result, while the Responsible, Consulted, and Informed roles may each be held by several people. Assisting is not what the letter stands for, and junior staff who aid the work are Responsible parties. Advisory describes the Consulted role, which supplies input rather than ownership. Approval by two senior managers splits accountability between them, which is the very situation the single-A rule exists to prevent.

Correct answer: To map project tasks or deliverables to the people or groups accountable for them

To map project tasks or deliverables to the people or groups accountable for them is what a responsibility assignment matrix does, making ownership of every work package clear; a RACI chart is one common form. Listing the skills or certifications team members hold is a skills matrix used in resource planning, which describes capability rather than assigning work. Plotting start or finish dates of activities on a timeline is a Gantt chart, which shows when work happens rather than who owns it. Rating threats or opportunities by likelihood and impact is a probability and impact matrix used in qualitative risk analysis.

Correct answer: Any individual, group, or organization that may affect, be affected by, or perceive itself to be affected by the project

A stakeholder is any individual, group, or organization that may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of the project. That definition is deliberately broad, which is what makes it the most complete of the four, and it takes in customers, sponsors, team members, regulators, and end users alike. Purchasers, investors, and shareholders capture the financial stake and leave out users and regulators. Technicians, officers, and contractors capture the delivery side and leave out the paying customer. Regulators, assessors, and inspectorates capture external oversight and leave out the team. Each of those three names a genuine subset of stakeholders rather than the class itself.

Correct answer: The register names the interested stakeholders; the engagement plan sets tactics to involve them

The register names the interested stakeholders; the engagement plan sets tactics to involve them is the correct pairing: the stakeholder register is the inventory of identities, roles, interests, and influence, and the stakeholder engagement plan holds the strategies built from that inventory. Having the engagement plan list the stakeholders while the register records ways to win them over swaps the two artifacts. The communications plan sets what information goes to whom and when, and the issue log tracks open problems, so neither is the stakeholder list or the engagement strategy. A RACI matrix assigns responsibility for work and a risk register records risks and their responses, so neither is a stakeholder artifact.

Correct answer: Scope, schedule, and cost

Scope, schedule, and cost is the traditional triple constraint, and the three are interdependent, so enlarging scope normally pushes time or cost upward. Quality, risk, and people are all managed on a project, but they belong to the wider set of competing constraints rather than the original three. Safety, ethics, and value are obligations and outcomes the project must respect, not the trade-off limits of that model. Process, tools, and skill describe the capability a team brings to the work, not the boundaries the project manager balances.

Correct answer: The work required, and only that work, to produce the product, service, or result with its features and functions

Scope is the work required, and only that work, to produce the product, service, or result with its specified features and functions; it draws the line between what is included and what is excluded. The money required to finance designs, testing, or rollout is the budget, a cost figure rather than a definition of the work. The time required to sequence stages, handoffs, or reviews is the schedule. The quality required to certify parts, welds, or coats is the quality standard the deliverables must meet. None of those three states what work the project will and will not do.

Correct answer: A unique, verifiable product, result, or capability produced to conclude a process or project, such as a tested user manual

A deliverable is a unique, verifiable product, result, or capability produced to conclude a process, phase, or project, and a completed and tested user manual is exactly that. A formal, delegated authority, mandate, or privilege granted to control a budget or project is a governance right the manager holds, not something the work hands over. A declared, measured limit, threshold, or tolerance adopted to bound a venture or portfolio is risk appetite, an attitude rather than an output. A routine, recurring meeting, briefing, or gathering arranged to update a cohort or sponsor is an activity the team performs; it produces no verifiable artifact of its own.

Correct answer: Milestones

These are milestones: significant points or events in a schedule that carry zero duration and mark progress, such as an approval or a go-live date. Activities consume time and resources, so every one of them has a duration. Successors are simply the activities that follow a predecessor in the network, identified by their logical links rather than by significance. Iterations are fixed-length delivery cycles in adaptive work and also take time, so neither they nor the other two mark a point with no duration.

Correct answer: The lessons learned register

This knowledge belongs in the lessons learned register, a living document that captures insights as they are gained so they can be applied to the remainder of the work and to future projects. The risk breakdown structure sorts sources of risk into a hierarchy and holds no retrospective findings. The project status dashboard reports current progress against the plan and is replaced each reporting cycle. The change impact assessment analyzes one proposed change rather than what a whole phase taught the team.

Correct answer: The manager drives delivery to objectives; the sponsor supplies funding and executive backing

The manager drives delivery to objectives while the sponsor supplies funding and executive backing. The project manager is the person assigned to lead the team and is accountable for achieving the objectives, and the sponsor is the person or group that provides the resources and champions the work at senior level. Having the sponsor control delivery while the manager finds funding swaps the two roles outright. Having an engineer oversee progress while the manager grants funding puts spending authority with the person who should be spending it. Having a treasurer coordinate squads while the manager only offers guidance strips the project manager of the accountability the stem assigns to that role.

Correct answer: The product owner maximizes value and owns the backlog; the development team decides how to produce the increment

The product owner maximizes value and owns the backlog, while the development team decides how to produce the increment: the owner orders the work by the value it returns, and the team chooses how to design and construct it. Having an engineering squad score priorities while the product owner writes code reverses both responsibilities. Having the scrum master set budgets and sign contracts is wrong because that role facilitates and removes impediments and holds no commercial authority. Having the sponsor manage dashboards and host standups is wrong because day-to-day coordination sits with the team, not the funder.

Correct answer: Tailoring the approach

This is the tailoring principle: teams design the development approach, processes, and governance to fit the project's own context, objectives, stakeholders, and complexity rather than applying one fixed method to everything. Centralizing the rules pulls decisions away from the people closest to the work and is the opposite of what the principle asks. Eliminating the chance of surprise is not achievable; uncertainty is managed and responded to, never removed. Maximizing the returns states a financial goal rather than a principle about how the team should work.

Correct answer: Performance domains

Performance domains is the answer. The PMBOK Guide Seventh Edition organizes effective delivery around eight interrelated performance domains: Stakeholders, Team, Development Approach and Life Cycle, Planning, Project Work, Delivery, Measurement, and Uncertainty. Delivery principles misnames the twelve project management principles, which guide behavior rather than describe outcome areas to manage. Tailoring dimensions refers to adapting the approach, processes, and artifacts to the context, a practice applied across the domains rather than the domains themselves. Models and methods belong to the guide's toolbox of models, methods, and artifacts, not to its areas of focus.

Correct answer: Servant leadership

Servant leadership is the style described: the leader's first aim is to serve the team, clearing obstacles, supplying what the team needs, and creating conditions in which people can do their best work. Ethical leadership centers on modeling integrity and fair conduct, not on removing impediments for the team. Adaptive leadership mobilizes people to tackle unfamiliar challenges that have no ready answer, which is about navigating change rather than serving the team. Shared leadership spreads the leading role across several team members instead of describing one leader who serves the others.

Correct answer: A hybrid management approach

This is a hybrid management approach: it deliberately combines predictive and adaptive elements inside one project, using a plan-based method for the stable regulated infrastructure and iterations for the evolving features. A phased predictive approach runs the whole project through planned sequential phases and leaves no room for the iterative half of the work. A dual-track agile approach runs discovery and delivery as two agile streams, so neither track is plan-based. A staged incremental approach releases pieces of one solution in stages but does not mix a predictive method with agile iterations.

Correct answer: A daily standup, used to coordinate the team and identify impediments

This is a daily standup, used to coordinate the team and identify impediments: a short time-boxed event in which members align the day's plan and raise blockers so they can be cleared quickly. A status meeting reports task progress upward to a manager, whereas the standup is the team coordinating with itself. A sprint review shows the increment and collects user feedback at the end of an iteration, not every morning. A retrospective reviews the process and agrees on improvements at the end of an iteration, not as a daily sync.

Correct answer: The risk register

The risk register serves this purpose: it is the repository that records each identified risk together with its description, cause, potential impact, assigned owner, and planned response, and it is kept current throughout the project. The risk analysis is the assessment activity that feeds the register; it is a piece of work rather than the place the results are held. The cost baseline is the approved time-phased budget and carries no risk information at all. The audit summary reports compliance findings after a review and looks backward rather than forward.

Correct answer: Avoid, by removing the causal trigger

Changing the plan so the threat can no longer occur at all is the avoid strategy, and removing the causal trigger is precisely how avoidance is carried out. Accepting by holding the known exposure means taking no proactive action and dealing with the threat only if it materializes. Transferring by paying for outside cover moves the financial impact to a third party but leaves the threat perfectly able to occur. Mitigating by lowering the likely harm reduces probability or impact without eliminating the possibility.

Correct answer: Exploit, by making the gain certain

Exploit is the strategy that makes the gain certain: it takes action to ensure the positive risk actually occurs, which is what the team wants here. Enhance lifts the odds upward by improving probability or impact but stops short of guaranteeing the opportunity happens. Mitigate trims the size of a loss and is a threat strategy rather than an opportunity one. Transfer shifts cost away to another party and is likewise used against threats.

Correct answer: Escalate, avoid, transfer, mitigate, and accept

The categories for responding to threats are escalate, avoid, transfer, mitigate, and accept: escalate moves the risk to a higher authority, avoid eliminates it, transfer shifts its impact to a third party, mitigate reduces its probability or impact, and accept acknowledges it without further action. Escalate, exploit, share, enhance, and accept is the list for opportunities, where the aim is to increase a positive risk rather than contain a threat. Withdraw, smooth, force, compromise, and confront are conflict resolution techniques, not risk responses. Identify, analyze, plan, implement, and monitor names steps in the risk management process rather than the response categories chosen within it.

Correct answer: Weigh the impact and involve the right stakeholders to settle on a response

Weigh the impact and involve the right stakeholders to settle on a response is what the team should do first: value-driven guidance asks the team to understand the effect and bring in the people it touches before committing to any course of action. Rebaselining the schedule and revising the forecast locks in a delay before anyone knows how large the impact is. Substituting the resource and restarting the steady routine acts before checking whether the substitute actually solves the problem. Redirecting the funding and rewriting the signed contract to insist on a penalty turns an internal issue into a commercial dispute and still leaves the schedule unmanaged.

Correct answer: Systems thinking

This is systems thinking: the principle asks teams to recognize, evaluate, and respond to the interactions inside and around the project and to treat the project as part of a larger whole. Linear reporting passes information up a single chain and conceals the very interactions the principle is about. Local optimizing improves one part at the expense of the whole, which is the failure systems thinking exists to prevent. Isolated costing prices one component without regard to its effect on the rest of the system.

Correct answer: Success is measured by the value and expected outcomes delivered to stakeholders, not simply outputs

Success is measured by the value and expected outcomes delivered to stakeholders, not simply outputs: the PMBOK Guide Seventh Edition judges a project by the benefits it realizes rather than by the artifacts it produces. Measuring by the budget and unspent reserve retained to shareholders reduces success to a single constraint and ignores whether anything useful resulted. Measuring by the dates and stated milestones achieved to timetables does the same for schedule. Measuring by the volume and quality documents produced to regulators counts paperwork, which is an output rather than an outcome.

Correct answer: Iterative delivery in short cycles, with feedback that steers later work

Iterative delivery in short cycles, with feedback that steers later work is the best fit for highly uncertain requirements, because each short cycle gives users something to react to and that reaction reshapes what comes next. Single delivery at project close, with scope locked early, fixes requirements before anyone learns what users actually need. Sequential delivery with handoffs after sign-off moves work through specialists one step at a time, so feedback arrives too late to change earlier decisions. Staged delivery through set gates relies on reviews that approve moving forward, which controls progress but does not let changing requirements reshape the product.

Correct answer: Scope creep, addressed by the integrated change control process

Scope creep, addressed by the integrated change control process, names both the phenomenon and its remedy: work expands without matching adjustments to time, cost and resources, so every proposed addition must be raised, assessed for impact and approved before it is built. Progressive elaboration is the legitimate refinement of detail within approved scope, and rolling wave planning schedules that detail, so neither describes nor stops unapproved additions. Resource overload can be a side effect of the extra work, but resource leveling only smooths demand and leaves the unapproved features in place. Cost overruns can follow too, yet earned value management measures the damage rather than controlling what enters the scope.

Correct answer: A common definition of done

A common definition of done is the agreed set of conditions every work item must satisfy before the team calls it complete, which is exactly what the team has written. A checklist of testing done records which verification steps were actually carried out on one item, so it is evidence rather than the standard the evidence is judged against. A revised statement of work bounds what will be delivered under an engagement and says nothing about when one item is done. A detailed backlog of items is the ordered list of work waiting to be pulled, so it holds the items rather than the completion conditions applied to them.

Correct answer: Projected future value should drive the decision, because sunk costs stay irrecoverable

Projected future value should drive the decision, because sunk costs stay irrecoverable: money already spent cannot be recovered whether the project continues or stops, so it carries no information about whether continuing is worthwhile. Arguing that total capital invested justifies rescue is the sunk cost fallacy itself, which is precisely the reasoning the stakeholder is using. The initial charter scope records what was authorized at the start and cannot tell the team whether future benefits still exceed future costs. Sponsor pressure is an input to be managed, not an economic test of continued investment.

Correct answer: Be a diligent, respectful, and caring steward

Be a diligent, respectful, and caring steward is the stewardship principle, which asks practitioners to act with integrity and care toward the organization, its resources, its people and the wider environment. Be a visionary, engaging, and decisive leader restates the separate leadership principle, which is about influencing and motivating rather than about responsible custody. Be a probing, analytic, and accurate reviewer describes an assurance role, not a principle of the guide. Be a daring, adaptable, and resilient planner points at adaptability and resiliency, which concerns responding to change rather than honouring an obligation of care.

Correct answer: Create a collaborative environment for the project team

Create a collaborative environment for the project team is the principle that speaks directly to people: shared working agreements, shared accountability, and a culture in which the team can perform at its best. Engaging with stakeholders proactively is a separate principle aimed at the people outside the team whose interests the project affects. Tailoring the delivery approach to the project context governs how methods are chosen, not how the team works together. Being a diligent, respectful, and caring steward concerns integrity and the responsible use of resources rather than team collaboration and accountability.

Correct answer: Involve both stakeholders to understand their needs and seek a value-based resolution

Involve both stakeholders to understand their needs and seek a value-based resolution is the first step, because the disagreement can only be settled once the underlying need behind each position is known and weighed against project value. Tabulating preferences and adopting the popular position settles the count rather than the need, and the more valuable requirement can easily be the less popular one. Directing both parties to retract their objections suppresses the disagreement instead of resolving it, so the same conflict returns later. Replacing the stakeholders removes the very people who hold the requirement, which destroys the engagement the situation calls for.

Correct answer: Build quality into the work processes and the deliverables

Build quality into the work processes and the deliverables is the quality principle: defects are prevented by how the work is performed, not merely detected once it is finished. Tailoring the delivery approach to the context of the project is the tailoring principle, which fits methods to circumstances but says nothing about preventing defects. Optimizing risk responses across the project and its outputs is the risk principle, which addresses uncertainty rather than conformance of the work to requirements. Focusing on the value that each outcome delivers to customers is the value principle, which judges benefit rather than how quality is embedded in the work.

Correct answer: Tailoring and navigating complexity

Tailoring and navigating complexity are the two concepts demonstrated: the plans and processes were deliberately scaled to the context, which is tailoring, and the judgment that the effort was small and low risk is an assessment of complexity. Modeling and forecasting complexity would mean predicting how complexity behaves over time, which nobody in the scenario did. Budgeting and auditing procurements concern buying goods and services, and no procurement appears anywhere in the scenario. Estimating and modeling complexity would produce a measurement of how intricate the work is, whereas the scenario describes acting on that judgment by scaling the process itself.

Correct answer: It brings early frequent value and speedier feedback to guide the work

It brings early frequent value and speedier feedback to guide the work is the strongest justification, because a usable increment puts real value in the customer's hands sooner and turns their reaction into evidence that shapes the next increment. Securing firmly fixed scope and stable budgets is not the aim, since incremental delivery exists so scope can evolve with feedback. Lower total cost and shorter timelines are not guaranteed, because changing direction on feedback can add work. Needing less formal testing is false, since each increment must be tested to count as usable.

Correct answer: The product backlog

The product backlog is the ordered list of everything currently known to be potentially needed in the product, kept in value order so the team pulls from the top. The release roadmap shows intended direction and timing at a coarse level rather than the full ordered list of features, enhancements, and fixes. The scope statement is a predictive planning document that fixes agreed scope and exclusions rather than a continuously reordered list. The iteration plan covers just the items committed for one iteration, not everything potentially needed for the product.

Correct answer: A program and a portfolio

A program and a portfolio is correct in that order: a program is a group of related projects managed together for benefits none of them could deliver alone, and a portfolio is the collection of work an organization selects and funds to meet its strategy. Naming the first grouping a portfolio and the second a project reverses the hierarchy, since portfolios sit above programs rather than inside them. Calling the first a portfolio and the second a segment misplaces the funding body as well, because a segment is a slice of a market rather than a governance grouping. A function and a division describe permanent parts of an organization chart, which exist whether or not any project is running.

Correct answer: A project is temporary and generates a unique product, service, or result, with a defined start and finish

A project is temporary and generates a unique product, service, or result, with a defined start and finish: those two properties, temporary and unique, are what separate project work from operations. Work that is ongoing and sustains a steady output on a repeating funding cycle is the definition of operations, which is precisely what the help desk does. Being costly, or consuming a large budget and headcount, describes the size of the work and not its nature, since tiny efforts can still be projects. Exceeding a budgeted cost or duration threshold is an internal governance rule about which work needs oversight, not a definition of what a project is.

Correct answer: Initiating, Planning, Executing, Monitoring and Controlling, and Closing

Initiating, Planning, Executing, Monitoring and Controlling, and Closing are the five process groups, and they organize the work logically rather than marking stages on a calendar. Analyzing, Designing, Assembling, Verifying and Deploying, and Releasing is a product development sequence, which describes how a deliverable is built rather than how a project is managed. Selecting, Approving, Chartering, Measuring and Reporting, and Archiving mixes portfolio selection and records management into what looks like a governance cycle. Estimating, Scheduling, Budgeting, Reviewing and Auditing, and Closedown lists planning and control techniques, not the groups those techniques belong to.

Correct answer: A predictive (plan-based) approach, because scope is defined early and change is controlled

A predictive (plan-based) approach, because scope is defined early and change is controlled, is the fit here: the requirements are stable, the regulatory documentation has to be signed off before construction, and late change is expensive, which is exactly the situation detailed up-front planning was designed for. An adaptive approach assumes scope will emerge, and deliberately keeps it open, which would leave the regulatory package unapprovable. A stage-gate approach sends each scope change to an investment review, which is a funding control and says nothing about whether the scope is knowable in the first place. A hybrid approach splits the work into stable and volatile parts, but nothing here is volatile, so there is no portion that would benefit from iteration.

Correct answer: The project life cycle

The project life cycle is the series of phases a project passes through from start to completion, and it gives the framework used to organize and govern the work whether delivery is predictive, adaptive or hybrid. The stage gate process is the review mechanism applied between phases, so it governs the transitions rather than being the sequence itself. The work package level is the bottom tier of a decomposed scope, which concerns how work is broken down, not how the project progresses over time. The project phase gate is a single decision point, so it is one moment in the sequence rather than the whole sequence.

Correct answer: Milestones

Milestones are significant points or events in a project, such as the end of a design phase or a final acceptance, and they are shown with zero duration because they mark a moment rather than a span of work. Deliverables are the unique products or results the work produces, not points on the schedule that mark when something happened. Dependencies are the logical relationships that set the order of activities, so they describe links between tasks rather than events. Timeboxes are fixed periods allotted to a piece of work, so they occupy a span of time rather than marking an instant.

Correct answer: A hybrid approach

A hybrid approach is the name for deliberately blending predictive planning and iterative delivery inside one project, so the regulatory report and the dashboard each get the method that suits them. A linear approach runs all the work in one fixed sequence, which covers the report but leaves no room for the dashboard's iterations. A phased approach splits the project into sequential phases with reviews between them, which is still a single plan-driven style rather than a blend. A scaled approach extends one agile framework across many teams and says nothing about combining it with predictive planning.

Correct answer: The lessons learned register

The lessons learned register is the artifact used throughout a project to record what worked, what did not, and what should be done differently, so the knowledge is available to later phases and to other projects. The knowledge transfer brief hands over operating information to whoever will run the product, which is a handover aid rather than a running record of experience. The quality assurance report states whether processes were followed and deliverables conformed, not what the team would change next time. The phase acceptance summary records that the phase output was approved, so it documents the decision rather than the reflection behind it.

Correct answer: Mitigate

Mitigate is the strategy: qualifying a second vendor in advance reduces the impact the threat would have if the first vendor slips, and reducing probability or impact is what mitigation means. Transfer would move the financial consequence to another party, through a penalty clause or insurance, without changing how badly a late delivery would hurt the schedule. Tolerate means taking no proactive action and absorbing the consequence, which is the opposite of preparing an alternative in advance. Escalate hands the threat to a higher authority because it falls outside the team's remit, and here the team is acting on it itself.

Correct answer: To compare the quantity of work genuinely completed against the original approved budget

Correct answer: To compare the quantity of work genuinely completed against the original approved budget. Earned value integrates scope, cost and schedule by valuing finished work in budget terms, so performance can be read against the baseline at any moment. Comparing actual amounts spent against planned spending ignores how much work that money bought, which is exactly the gap earned value closes. Comparing activities finished against schedule dates tracks time alone and ignores the cost dimension. Comparing labor hours charged against allocated workloads is resource utilization tracking, not a measure of value earned.

Correct answer: To find the longest chain of linked tasks and compute the shortest possible project duration

Correct answer: To find the longest chain of linked tasks and compute the shortest possible project duration. The critical path is the longest dependent sequence through the network, and its length sets the earliest date the project can finish; activities on it carry zero float. Ranking costly items to reduce an overrun is cost control. Levelling busy weeks of assigned staff is resource levelling, which reacts to a schedule rather than producing one. Rating risky events to shrink exposure is risk analysis. None of those three yields the minimum duration.

Correct answer: To arrange and define the entire project scope into layered deliverable levels

Correct answer: To arrange and define the entire project scope into layered deliverable levels. A work breakdown structure decomposes the total scope hierarchically, level by level, until the work is small enough to estimate and assign; that decomposition is its purpose. Converting scope into priced budget lines is cost estimating, which uses the structure rather than creating it. Turning scope into dated schedule milestones is schedule development. Reducing scope to listed material quantities is a bill of materials, not a deliverable hierarchy.

Correct answer: It is a method for estimating the chance of finishing project tasks within the scheduled time frame

Correct answer: It is a method for estimating the chance of finishing project tasks within the scheduled time frame. Monte Carlo analysis runs the schedule model thousands of times using ranges rather than single values and returns the probability of hitting a given date. Averaging optimistic, likely, and pessimistic durations into one expected figure is three-point (PERT) estimating, which yields a single number rather than a probability distribution. Identifying the longest sequence of dependent activities is the critical path method, a single deterministic calculation. Ranking identified risks by probability and impact on a qualitative matrix is qualitative risk analysis, which scores risks rather than simulating outcomes.

Correct answer: A wait in the launch of an activity due to the late completion of its predecessor

Correct answer: A wait in the launch of an activity due to the late completion of its predecessor. A lag is waiting time between dependent activities, so the successor cannot begin the moment the predecessor ends. A cushion in the float from unused timetable capacity is total float, which is available slack rather than imposed waiting. A reduction in length from added labor is crashing, a compression technique. A switch in order from parallel overlap is fast tracking, which removes waiting instead of creating it.

Correct answer: Running more tasks in parallel to shorten the project duration

Correct answer: Running more tasks in parallel to shorten the project duration. Fast tracking overlaps activities that were planned to run in sequence. It saves time but adds rework risk. Adding paid overtime to critical path work is crashing, which buys time with money instead of overlapping activities. Shifting activity start dates to even out peak resource demand is resource leveling, which often makes the schedule longer, not shorter. Removing low-priority scope items to meet the project deadline is a scope reduction that needs change approval and is not a schedule compression technique.

Correct answer: To confirm that the project products, services, or results are consistent and meet requirements

Correct answer: To confirm that the project products, services, or results are consistent and meet requirements. Configuration management keeps the functional and physical attributes of the deliverable aligned with its requirements and design, and controls every change to that definition. Archiving files, templates, and lessons learned is knowledge management, which preserves organizational assets rather than governing the product definition. Configuring servers, networks, and software settings is technical setup that borrows the word but has nothing to do with deliverable integrity. Tracking costs, schedule, and scope against baselines is performance monitoring, which measures progress rather than controlling the attributes of the product.

Correct answer: Managing limited project resource constraints

Correct answer: Managing limited project resource constraints. The critical chain method extends network scheduling by treating scarce resources as the binding limit and protecting the plan with feeding and project buffers rather than task-level padding. Locating the longest sequence of linked tasks is the critical path method, which assumes resources are unlimited. Padding individual task estimates with safety is exactly what the critical chain method strips out, pooling that safety into shared buffers instead. Measuring earned value against cost baselines is performance measurement, not a scheduling method. Only the resource constraint is what the critical chain is built around.

Correct answer: Level out resource peaks across the whole span of the project to avoid overallocation

Correct answer: Level out resource peaks across the whole span of the project to avoid overallocation. Leveling shifts start and finish dates so that no resource is booked beyond its availability; the trade-off is that the critical path and the end date often move. Adding extra resources to critical path activities to shorten duration is crashing, a compression technique that adds cost and can create new peaks. Shifting activities within available float to keep the finish date unchanged is resource smoothing, which differs from leveling precisely because leveling may move the end date. Estimating the type and quantity of resources each activity needs is Estimate Activity Resources, which supplies the demand that leveling later balances.

Correct answer: Adjusting resource usage so that demand stays inside preset limits

Correct answer: Adjusting resource usage so that demand stays inside preset limits. Smoothing uses only the free and total float already in the schedule, so peaks are shaved without moving the critical path or the completion date. Shifting dates so the finish stays inside frozen windows is schedule compression and does move the end date. Trimming scope so effort stays inside tight ceilings changes what is delivered rather than how resources are spread. Securing funds so hiring stays inside raised budgets buys capacity instead of smoothing it.

Correct answer: To gather expert opinions on narrow project issues under anonymous conditions

Correct answer: To gather expert opinions on narrow project issues under anonymous conditions. The Delphi technique circulates rounds of questionnaires to a panel whose members never see each other's names, so consensus forms without any one voice dominating. Creating costed schedules under external timetables is schedule development. Sharing written updates under published protocols is communications management. Assigning limited resources under changed priorities is resource allocation. None of those three collects independent expert judgment.

Correct answer: Determine the project schedule variance and forecast its likely completion date.

Correct answer: Determine the project schedule variance and forecast its likely completion date. Earned schedule converts earned value into time units, so schedule performance is expressed in weeks rather than currency and stays meaningful right to the end of the project. Valuing work performed in dollars to predict total cost at completion is the cost side of earned value, which yields a cost forecast rather than a date. Balancing resource demand over time to level workload peaks is resource leveling, which adjusts the plan rather than measuring progress against it. Identifying activities likely to lag and shortening them by crashing or fast-tracking is schedule compression, which acts on a delay instead of measuring it.

Correct answer: Assess process variation and consistency over time.

Correct answer: Assess process variation and consistency over time. A control chart plots measurements against a mean with upper and lower control limits, so common-cause noise can be told apart from special-cause signals that need investigation. Contrasting vendor invoices and payments is financial reconciliation. Recording monthly actions and decisions is meeting administration. Predicting staff shortages and overtime is resource forecasting. None of those three tests whether a process is in statistical control.

Correct answer: Prioritizing risks based on their likelihood and effects on project objectives.

Correct answer: Prioritizing risks based on their likelihood and effects on project objectives. Qualitative analysis uses relative ratings and a probability and impact matrix to sort the register, so limited attention goes to the risks that matter most. Quantifying risks by valuation and exposure is quantitative analysis, which puts numbers on effects rather than ranking them. Forecasting risks by duration and slippage is schedule risk modeling. Budgeting risks by remediation and handling is response planning, which happens after prioritization.

Correct answer: Map stakeholders based on their level of authority and concern for project outcomes.

Correct answer: Map stakeholders based on their level of authority and concern for project outcomes. The grid plots power against interest and sorts people into manage closely, keep satisfied, keep informed and monitor, which sets the engagement effort each one receives. Billing stakeholders for a share of overheads is cost recovery. Calling stakeholders about a choice of calendar is meeting administration. Paying stakeholders for years of service is a compensation decision that sits outside project stakeholder analysis.

Correct answer: Judging the duration or cost of activities from past similar projects.

Correct answer: Judging the duration or cost of activities from past similar projects. Analogous estimating takes the actual values of a comparable earlier project as the basis for the current one; it is quick, cheap and least accurate, which is why it is used early when detail is scarce. Scaling unit rates by quantities with a statistical model is parametric estimating. Summing detailed estimates of small work packages up to higher levels is bottom-up estimating. Averaging the optimistic, most likely, and pessimistic values per task is three-point estimating, which draws on no earlier project.

Correct answer: To measure the extent of deviation from the original project budget.

Correct answer: To measure the extent of deviation from the original project budget. Cost variance subtracts actual cost from earned value, so a negative figure says the work completed cost more than was budgeted for it. Measuring adherence to the planned schedule is schedule variance, the time dimension rather than the money one. Measuring feedback from the project audience is a communications metric. Measuring the speed of delivery from the workforce is a productivity metric, and neither compares spend against budget.

Correct answer: The efficiency with which the team uses allocated project time.

Correct answer: The efficiency with which the team uses allocated project time. The schedule performance index divides earned value by planned value, so a result below one means less work has been completed than planned by this date. The efficiency with which the team spends its approved funding is the cost performance index, earned value divided by actual cost. The amount by which earned value is above or below planned value is schedule variance, a difference rather than a ratio. The amount by which earned value is above or below actual cost is cost variance, likewise a difference rather than an efficiency index.

Correct answer: The work breakdown structure, its WBS dictionary, and the scope statement

Correct answer: The work breakdown structure, its WBS dictionary, and the scope statement. Those three approved documents are the scope baseline, and only a formal change request can alter them. A project charter with a RACI matrix and a variations repository mixes initiation and control records that sit outside the baseline. An annual budget with a SWOT summary and a verification procedure belongs to cost and quality planning. Quality plans with a PERT calendar and a compliance assessment name schedule and quality artefacts instead.

Correct answer: A method that applies unit costs and past output rates to estimate project totals

Correct answer: A method that applies unit costs and past output rates to estimate project totals. Parametric estimating multiplies a measured rate - cost per square meter, hours per drawing - by the quantity of work, which makes it more accurate than an analogy when reliable historical rates exist. Applying the recorded costs of a comparable project as a whole is analogous estimating, which scales one past project rather than a unit rate. Applying optimistic, likely and pessimistic values to get an average is three-point estimating. Applying detailed estimates of each work package and summing them is bottom-up estimating, which adds components rather than scaling a rate.

Correct answer: It forecasts the cost difference between the budget and the estimate

Correct answer: It forecasts the cost difference between the budget and the estimate. Variance at Completion is an earned value forecast that subtracts the estimate at completion from the budget at completion, predicting whether the work will finish under, on, or over its authorized budget. Scope drift captured between the charter and the deliverables is a scope variance and carries no money in it. Project workload gauged between a baseline and a timeline is resource or productivity reporting, not a budget forecast. Delivery dates compared between the schedule and the handover give schedule variance, a measure in units of time that Variance at Completion never reports.

Correct answer: Product Analysis

Correct answer: Product Analysis. Defining scope means translating a high-level product description into tangible deliverables and requirements, and product analysis does exactly that through product breakdown, systems analysis and value engineering. The Delphi Technique builds anonymous expert consensus for requirements or estimates but produces no description of the product itself. Scope Inspection belongs to Validate Scope, where finished deliverables are examined after the scope has already been defined. An Affinity Diagram sorts large numbers of ideas into groups while requirements are collected, which organizes input rather than detailing the deliverables.

Correct answer: Transfer

Correct answer: Transfer. Transferring a threat shifts both its impact and the responsibility for responding to a third party, typically through insurance, warranties, performance bonds or a fixed-price subcontract; ownership leaves the project team. Mitigating keeps the threat in-house and works to reduce its probability or impact. Escalating moves a threat to a higher level of the organization because it sits outside project authority, which is not a third party. Tolerating leaves the threat with the project and simply prepares for it, so no ownership moves anywhere.

Correct answer: Monte Carlo Simulation

Correct answer: Monte Carlo Simulation. Quantitative analysis needs a numeric model, and simulation samples the ranges attached to costs and durations thousands of times to produce probability distributions and confidence levels for the whole project. Expert judgment panels return opinion on ratings and produce no distribution, which keeps them qualitative. Assumption log reviews test whether stated assumptions still hold and surface new risks rather than quantify known ones. Prompt risk screenings sort exposures into standard categories, so they help identification but yield no probabilistic result.

Correct answer: Cost Plus Incentive Fee (CPIF)

Correct answer: Cost Plus Incentive Fee (CPIF). The buyer repays allowable costs against an agreed target and shares any underrun or overrun with the seller through a ratio fixed in advance, so the seller earns more fee by spending less and loses fee by spending more, which ties its profit directly to cost control. Cost Plus Percentage Cost works the other way, since the fee grows with spending and the seller is better off letting costs run. Time and Materials pays hourly rates that already include profit, so more hours billed means more revenue and there is no reward for working efficiently. Cost Plus Fixed Fee pays the same fee whatever the final cost, so the seller gains nothing from saving money and gives cost control only minimal attention.

Correct answer: The Power/Interest Grid

Correct answer: The Power/Interest Grid. This classification model plots each stakeholder on two axes, the authority they hold and the concern they feel about the outcome, which is precisely the mix of hard and soft information the question describes and it yields the manage-closely, keep-satisfied, keep-informed and monitor quadrants. The Salience/Role Model grades claimants by urgency and legitimacy and never asks about level of concern. The Impact/Value Matrix ranks work items by payoff and is applied to backlogs, not to people. The Interest/Effort Map weighs how much work an activity costs, so it grades tasks rather than the parties affected by them.

Correct answer: To ensure that changes are recorded and reviewed

Correct answer: To ensure that changes are recorded and reviewed. Perform Integrated Change Control logs every request, evaluates its effect across scope, schedule, cost, quality and risk together, and then approves or rejects it before anything is built, which is what keeps the baselines trustworthy. Ensuring that changes are estimated and charged covers only the money side and ignores the integrated review of every other constraint. Ensuring that changes are briefed and published is communication work that happens after a decision has already been taken. Ensuring that changes are programmed and queued is schedule updating, an implementation step that follows approval rather than producing it.

Correct answer: To formalize the acceptance of finished project deliverables

Correct answer: To formalize the acceptance of finished project deliverables. Validate Scope takes deliverables that quality control has already verified and walks them through the customer or sponsor for signed acceptance, producing accepted deliverables as its output. Establishing the alignment of published requirements is traceability work carried out during Collect Requirements, long before anything exists to accept. Monitoring the advancement of unfinished assignments is Monitor and Control Project Work and reports on effort rather than closing anything out. Restricting the overspending of budgeted commitments is Control Costs, which has no authority to accept a deliverable.

Correct answer: The project risk register

Correct answer: The project risk register. The register is the running repository for each identified risk, holding its description, root cause, category, owner, agreed response and residual status, and it is updated from identification onward through every later risk process. The risk management plan describes how risk activities will be structured and performed, so it sets the approach and does not list individual risks. The risk breakdown structure is a hierarchy of risk sources used to organize where risks may arise, so it names categories rather than tracking specific risks. The project assumption log records assumptions and constraints, which may later give rise to risks but are not documented there with causes and consequences.

Correct answer: Flow Diagrams

Correct answer: Flow Diagrams. A flow diagram, also called a flowchart or process map, draws the sequence of a process as boxes and arrows, so what enters it, what is done to it, what decisions branch it and what leaves it are all visible in one picture. Control Charts plot process measurements against control limits over time and show no sequence of steps. Run Charts track a single measure over time with no process structure at all. Tree Diagrams break a goal or requirement into hierarchical levels, which depicts decomposition rather than inputs, actions and outputs.

Correct answer: The project cost aggregation

Correct answer: The project cost aggregation. Determine Budget works upward, summing activity estimates into work packages, work packages into control accounts and control accounts into a project total, and that total becomes the authorized cost baseline. The parametric cost estimate uses a statistical relationship to produce individual activity figures, so it feeds the summation rather than creating the baseline. The earned value measurement compares performance against a baseline that must already exist. The funding limit reconciliation adjusts the timing of planned spending to fit funding constraints, which changes distribution rather than establishing the authorized total.

Correct answer: To appraise the effectiveness of the procurement process

Correct answer: To appraise the effectiveness of the procurement process. A procurement audit is a structured review of the whole procurement cycle from planning through closure, judging how well it worked and capturing lessons that improve the next one. Selecting the qualified seller through a competitive bid is the work of Conduct Procurements itself, not a review of how that work went. Verifying each invoice before releasing vendor payments is routine payment control carried out during Control Procurements. Settling outstanding claims and disputes with the vendor is claims administration, which resolves individual disagreements rather than evaluating the process as a whole.

Correct answer: Perform Integrated Change Control

Correct answer: Perform Integrated Change Control. This process reviews every change request, decides it, and manages the resulting changes to deliverables, organizational process assets, project documents and the plan, keeping all of the baselines consistent with one another. Perform Qualitative Risk Analysis prioritizes risks by probability and impact and issues no decisions on requests. Develop Project Management Plan produces the baselines in the first place, before any change to them can exist. Monitor and Control Project Work compares performance against the plan and raises change requests, but the authority to approve or reject them sits elsewhere.

Correct answer: Using historic data to compute costs from project parameters

Correct answer: Using historic data to compute costs from project parameters. Parametric estimating multiplies a measurable parameter, such as square meters or lines of code, by a unit rate derived statistically from past work, and its accuracy depends on the quality of that historical relationship. Summing the estimates of each work package upward is bottom-up estimating, which builds from decomposition rather than from a rate. Adjusting the final cost of one similar past project is analogous estimating, which reasons by whole-project resemblance and uses no unit rate. Asking subject matter experts to judge costs is expert judgment, which relies on individual experience rather than a statistical relationship.

Correct answer: Ishikawa (Fishbone) Diagram

Correct answer: Ishikawa (Fishbone) Diagram. The fishbone places the problem at the head and branches the possible contributing causes along the spine by category, so a team can work backwards from an undesirable effect to the conditions that produce it. The Control (Variation) Diagram plots measurements against limits over time and tells you that a process is unstable without telling you why. The Flowchart (Process) Diagram shows the sequence of steps and may suggest where a failure sits, yet it lists no causes. The Bar (Distributions) Diagram shows how often values fall in each range, which describes spread rather than causation.

Correct answer: To build workable steps for engaging the project stakeholders

Correct answer: To build workable steps for engaging the project stakeholders. Plan Stakeholder Engagement is a planning process whose output is the stakeholder engagement plan, setting out the approaches that will move each party from its current level of involvement to the level the project needs. Surveying ongoing trends for reading the stakeholders is Monitor Stakeholder Engagement, which watches the results of a plan already in force. Collecting fresh records for listing the stakeholders is Identify Stakeholders, and it feeds the register that this planning process consumes. Sending scheduled notes for briefing the stakeholders is execution work carried out under Manage Communications.

Correct answer: Running linked tasks in overlapping blocks

Correct answer: Running linked tasks in overlapping blocks. Fast tracking compresses a schedule by starting activities that were sequenced one after another before their predecessors have finished, which buys time at the price of extra risk and possible rework. Injecting costly labor in tighter windows is crashing, the other compression technique, and it adds resources instead of overlapping work. Stretching cheaper effort in longer spells lengthens the schedule deliberately and compresses nothing. Inserting careful checks in fixed clusters adds quality activity, which consumes time rather than saving it.

Correct answer: Decision Tree Analysis

Decision Tree Analysis lays out each choice, the chance events that follow it and the payoff at every end point, so the whole set of outcomes and their impacts can be compared in one structure. Critical Path Analysis finds the longest chain of dependent activities in a schedule network and explores no decision options. Business Case Analysis justifies whether a single investment is worthwhile but does not branch through the chance outcomes that follow each choice. Root Cause Analysis traces a problem that has already happened back to its origins instead of exploring future outcomes.

Correct answer: To examine the likelihood of finishing activities within cost and schedule limits

Monte Carlo Simulation is used to examine the likelihood of finishing activities within cost and schedule limits: it draws thousands of samples from the ranges assigned to uncertain inputs and returns the probability of each result. Ranking risks by probability and impact on a qualitative scale is qualitative risk analysis, which assigns ratings rather than simulating outcomes. Tracing the longest sequence of dependent activities is the critical path method, a deterministic calculation from single duration values. Weighting the expected value of each decision branch is decision tree analysis, which compares defined choices rather than sampling from ranges of uncertainty.

Correct answer: PV is 80,000, EV is 70,000, and AC is 75,000

PV is 80,000, EV is 70,000, and AC is 75,000. Planned value (PV) is the authorized budget for the work that was scheduled to be finished by today, which the scenario gives as 80,000. Earned value (EV) is the budgeted value of the work actually completed, which is 70,000. Actual cost (AC) is the money genuinely spent to complete that work, which is 75,000. Every other mapping puts the spend figure where a budgeted figure belongs, and once the three are mislabelled every downstream variance and index comes out wrong.

Correct answer: Cost variance is -5,000, meaning that the project overspent against the earned value

Cost variance is -5,000, meaning that the project overspent against the earned value: cost variance is earned value minus actual cost, so 70,000 minus 75,000 gives -5,000, and a negative result says more money went out than the completed work was worth. A positive 5,000 read as underspending reverses the subtraction and turns an overrun into a saving. Reading -5,000 as running behind schedule confuses cost variance with schedule variance, which needs planned value and none is given. A positive 5,000 read as running ahead of schedule makes both errors at once, flipping the sign and swapping cost for schedule.

Correct answer: Schedule variance is -10,000, showing that the project now stands behind the plan

Schedule variance is -10,000, showing that the project now stands behind the plan: schedule variance is earned value minus planned value, so 70,000 minus 80,000 gives -10,000, and a negative figure says less work has been completed than was scheduled by this date. A positive 10,000 showing the project ahead of the plan reverses the subtraction, taking planned value minus earned value. Reading -10,000 as spending over the budget confuses schedule variance with cost variance, which compares earned value with actual cost, a figure the question does not give. A positive 10,000 read as spending under the budget makes both mistakes at once, reversing the sign and treating a schedule measure as a cost measure.

Correct answer: 0.90, meaning the team earns 90 cents of value per dollar consumed

0.90, meaning the team earns 90 cents of value per dollar consumed, is correct: the cost performance index is earned value divided by actual cost, so 90,000 divided by 100,000 gives 0.90, and a value below 1.0 shows the work delivered is worth less than the money spent. Reading 0.90 as 10 percent behind schedule confuses the cost index with the schedule performance index, which needs planned value and cannot be calculated from these figures. A result of 1.11 inverts the ratio, and reading it as 11 cents saved per dollar turns a cost overrun into a saving. Reading 1.11 as 11 percent more work than planned both inverts the ratio and treats a cost measure as a schedule one.

Correct answer: The project is ahead of schedule, completing more work than the plan projected

The project is ahead of schedule, completing more work than the plan projected: the schedule performance index is earned value divided by planned value, so a result above 1.0 means the value of work finished exceeds the value that was scheduled by this point. Being over budget is a statement about cost, which the schedule performance index cannot measure since actual cost never enters its calculation. Being short of funding concerns cash availability, which is a financing question rather than a progress measure. Being behind schedule is the reading for an index below 1.0, so 1.05 says exactly the opposite.

Correct answer: Earned value management

Earned value management is the technique described, because it is the only one that folds scope, schedule and cost into a single measurement system: budgeted work, completed work and money spent are expressed in the same units, which yields variances, performance indexes and forecasts of the final outcome. Critical chain planning protects a schedule with buffers against resource contention, so it touches duration alone. Rolling wave estimation is a planning habit of detailing near-term work and leaving later work coarse, which produces no performance measures at all. Schedule trend analysis charts how dates have drifted over successive reports, so it covers time without ever involving cost or scope.

Correct answer: Work package

Work package is the lowest-level component of a work breakdown structure: it is the point at which cost and duration can be estimated with confidence and the effort can be handed to one owner to schedule, execute and control. Cost account, like the control account it belongs to, sits above that level and exists to roll costs up for management reporting rather than to define the smallest unit of scope. Work product names an output the effort creates, so it describes a result rather than a component of the decomposition. Plan package covers a future branch that has been identified but deliberately not yet broken down, so by definition it still sits above the lowest level.

Correct answer: Decompose the project deliverables and scope into gradually smaller parts at work package level

Decompose the project deliverables and scope into gradually smaller parts at work package level is how a work breakdown structure is built: it is deliverable-oriented, it works top down, and the hundred percent rule means every piece of scope lands somewhere in it. Sequencing work against a calendar timeline with start and finish dates produces a Gantt chart or schedule, which arranges work in time rather than breaking it into components. Assigning the work into owner roles set as responsible, accountable, consulted or informed produces a responsibility assignment matrix, which maps people to work that has already been defined. Assessing work by probability and impact produces a risk register, which ranks uncertainty rather than organizing scope.

Correct answer: Total float covers three days and free float allows one day

Total float covers three days and free float allows one day. Total float is how long an activity can slip before the project's own finish date moves, which the scenario states is three days. Free float is how long it can slip before the early start of the very next activity moves, which the scenario states is one day. Reversing the two figures attaches the project-level tolerance to the successor instead, and free float can never exceed total float in any case. Setting both figures to one day ignores the three-day tolerance the project finish still has, and setting both to three days ignores the successor that begins to shift after a single day.

Correct answer: The activity stands on the scheduled critical path, so this project finish date follows it

The activity stands on the scheduled critical path, so this project finish date follows it. Float is the time an activity can be delayed without pushing a successor or the project end, so an activity with none has no scheduling flexibility at all, and that is the defining property of a critical path activity. Having zero successors would say nothing about float, since a terminal activity can still carry plenty of slack. The size of an activity's staffing load is a resource question and has no bearing on how much the schedule network allows it to move. Finishing ahead of baseline describes past performance, whereas total float describes the room remaining in the plan.

Correct answer: The critical path method, which finds the longest sequence of dependent activities and the shortest project duration

The critical path method, which finds the longest sequence of dependent activities and the shortest project duration, is the technique: a forward and backward pass through the network exposes the chain with zero float, and because every path must complete, the longest one sets the earliest possible finish and its activities cannot slip. The parametric estimate method derives durations from unit rates and quantities, which helps size individual activities but never reveals which chain drives the finish date. The Delphi survey method gathers anonymous expert judgment, which is an input to estimating rather than a network calculation. Resource smoothing rearranges work within existing float to even out demand, so it deliberately leaves the driving chain untouched.

Correct answer: Path B is critical, setting the project duration at 18 days

Path B is critical, setting the project duration at 18 days. The critical path is the longest route through the network, because the project cannot finish until every route has finished, so the longest one fixes the earliest completion. Calling the 14-day route critical inverts that rule and would leave Path B unfinished at the stated end date. Adding the two routes together treats them as sequential when the stem says both run from start to finish in parallel, so a combined figure badly overstates the work. Noting that Path A is quickest is true but irrelevant, and attaching the 18-day figure to it mixes the shorter route with the longer route's duration.

Correct answer: A Gantt chart

A Gantt chart is the artifact described: it plots each scheduled activity as a horizontal bar against a calendar axis, so start dates, finish dates, durations and overlaps are all readable at a glance. A RACI matrix maps people to work by responsibility, accountability, consultation and information, which says who acts rather than when. A risk matrix arranges threats by probability and impact, so its axes are exposure rather than time. A cost report summarizes money spent and committed, which tracks budget consumption and shows no schedule bars at all.

Correct answer: The project baseline

The project baseline is the combined approved reference: the approved scope, schedule and cost baselines together form the benchmark that actual results are compared against, including in earned value analysis. The project schedule is only one of the three components, so on its own it cannot serve as the combined reference for cost or scope performance. The measurement plan would describe how performance will be assessed, which is a method rather than the approved yardstick itself. The project estimate is a forecast produced during planning, and an estimate only becomes a baseline once it has been approved and placed under change control.

Correct answer: Submit the request through the formal change control process and await evaluation and approval

Submit the request through the formal change control process and await evaluation and approval. On a plan-based project every change to an approved baseline becomes a documented change request, is assessed for its effect on scope, schedule, cost and risk, and is approved or rejected before anyone builds anything. Rejecting the request outright skips that assessment, and an approved baseline is meant to be changed through a process, not treated as permanently closed. Delivering the feature first and submitting the change documentation to a later assessment commits the cost before anyone has weighed it, which is how scope creep starts. Absorbing the work quietly while stretching the schedule hides the impact and destroys the integrity of the baselines the team is measured against.

Correct answer: Regular adaptation to changes and constant stakeholder involvement

Correct answer: Regular adaptation to changes and constant stakeholder involvement. Agile works in short iterations that welcome changing requirements and keep the customer engaged throughout, rather than freezing a plan at the start. Complete commitment to forecasts with advanced requirement analysis is predictive planning, the approach agile was created to replace. Rigorous adherence to sequence with documented milestone acceptance is stage-gated waterfall delivery. Steady resistance to variation with unchanged contractual handovers is fixed-price contracting, which actively discourages the change agile expects.

Correct answer: To probe a narrow concept or build a rough prototype

Correct answer: To probe a narrow concept or build a rough prototype. A spike is a timeboxed piece of investigation taken on when a story cannot be estimated or designed with confidence, and its deliverable is knowledge, often in the form of a throwaway experiment that retires the uncertainty. Rekindling a fading mood or holding a friendly contest is a team-building activity with no product question behind it. Resolving a growing debt or tidying a tangled codebase is refactoring, which improves code already written rather than answering an open question. Reshuffling a bloated backlog or dropping a stale story is backlog refinement, a routine grooming activity owned by the product owner.

Correct answer: Feature-Driven Development

Correct answer: Feature-Driven Development. This method organizes all work around a list of small client-valued features, each expressed as an action, a result and an object, and drives the project through five processes that design and build feature by feature, which suits large teams needing a repeatable model. Outcome-Driven Development frames work by the result a user wants to achieve and prescribes no feature list or process set. Quality-Driven Development puts defect prevention first and is a quality posture rather than a delivery method. Client-Focused Development names an attitude toward the customer and carries none of the five defined processes.

Correct answer: Work In Progress Limit, applied in Kanban systems

Correct answer: Work In Progress Limit, applied in Kanban systems. The limit caps how many items may sit in any column of a Kanban board at once, which forces the team to finish work before starting more, exposes bottlenecks and shortens cycle time. Work In Process Limit, applied in Sprint backlogs, misplaces the idea: a sprint backlog is bounded by capacity for the whole iteration, not by a per-column cap. Work Interval Plan Limit, applied in Agile squads, is not a recognized term and describes timeboxing instead. Work Interface Point Limit, applied in Lean flows, invents a handover measure that no Lean or Kanban practice defines.

Correct answer: To maximize the worth of the product incrementally

Correct answer: To maximize the worth of the product incrementally. Scrum exists to deliver the highest possible value, and it does so by producing a usable increment every sprint, inspecting it with stakeholders and adapting the plan on what is learned. Eliminating the waste of the pipeline permanently is the central aim of Lean, which Scrum borrows from but does not take as its goal. Guaranteeing the rollout of the release flawlessly promises a certainty that an empirical framework explicitly refuses to offer. Transferring the control of the process voluntarily describes self-management, which is a means Scrum uses rather than the end it pursues.

Correct answer: Incremental Development

Correct answer: Incremental Development. Dividing a project into small usable pieces that are each built, tested and delivered inside a short timebox is exactly this practice, and it is what allows feedback to arrive early and planning to adapt between cycles. Collaborative Debugging has two people working a single defect and governs how a task is executed, not how the project is carved up. Automated Certification runs checks against a candidate build and is a verification step inside a cycle. Continuous Provisioning stands up environments on demand, which is infrastructure support and decomposes nothing.

Correct answer: Eliminate Waste

Correct answer: Eliminate Waste. Lean defines waste as anything the customer would not pay for, including partly done work, extra features, handoffs, delays, and defects, so this principle is the one that concentrates effort solely on value-adding work. Amplify Learning uses short iterations and fast feedback to build knowledge, which concerns discovery rather than filtering out non-value work. Defer Commitment keeps options open until the last responsible moment and governs the timing of decisions rather than value. Respect People pushes decisions to the people doing the work and addresses authority and motivation, not the content of the work.

Correct answer: Scaled Agile Framework (SAFe)

Correct answer: Scaled Agile Framework (SAFe). It was built specifically for scale, supplying agile release trains, program increment planning, portfolio and large solution levels and defined roles so that many teams can align on one product. Extreme Programming is a set of engineering practices such as pair programming and test-first development for a single team and defines no cross-team structure. Agile Unified Process is a streamlined version of the Rational Unified Process aimed at one project team, not at coordinating many. Adaptive Software Development is a speculate, collaborate, and learn cycle for an individual team and offers no roles or cadences for aligning multiple teams.

Correct answer: Refactoring

Correct answer: Refactoring. Restructuring existing code without altering its external behavior keeps the design clean as requirements arrive, so a change can be introduced at any point without decaying the system. Integrating merges contributions and rebuilds often, which catches conflicts early but leaves a poor internal structure exactly as poor as it was. Prototyping explores an idea with throwaway code and deliberately ignores the integrity of the production system. Documenting records how the system behaves today and changes no structure at all, so it cannot protect integrity when the code is modified.

Correct answer: To list the checks by which a single task is judged complete

Correct answer: To list the checks by which a single task is judged complete. The Definition of Done is a shared, explicit set of conditions that every item must satisfy before the team may call it finished, which gives transparency and keeps quality uniform across the increment. Naming the steps by which a new venture is formally started describes chartering and authorization, which sit before any work item exists. Fixing the hurdles by which a final build is deemed saleable is a release readiness gate applied once to the product, not to each item as it is worked. Charting the duties by which a senior sponsor is held liable is a role description and says nothing about when work is finished.

Correct answer: To illustrate the stability and efficiency of the process

Correct answer: To illustrate the stability and efficiency of the process. The diagram stacks the count of items in every stage over time, so widening bands expose bottlenecks while the horizontal and vertical distances between bands read directly as approximate lead time and work in progress. Showing the hours each team member logged is a timesheet view, and the diagram counts work items rather than effort or people. Ordering backlog items by value and urgency is prioritization, a decision the diagram informs but does not make. Tracking story points completed per iteration is a velocity chart, which measures output per timebox rather than the flow of items through each stage.

Correct answer: To voice the customers and rank the product backlog

Correct answer: To voice the customers and rank the product backlog. The Product Owner is the single person accountable for maximizing value, which means carrying the interests of customers and other stakeholders into the team and ordering the backlog so the most valuable item is next. Running the daily standup and removing impediments is the Scrum Master's service to the team. Sizing the stories and building the working increment belongs to the developers, who own estimates and how the work gets built. Approving the budget and reporting status to sponsors is traditional project-manager and governance work that Scrum does not assign to this role.

Correct answer: Velocity

Correct answer: Velocity. Counting the story points a team actually completes each iteration gives a trend that smooths out estimation noise over several sprints and becomes the basis for forecasting how much future work will fit. Burndown shows remaining effort inside one iteration and answers whether that sprint is on track rather than how the team performs across time. Capacity is the availability the team plans with before the work starts, so it is an input rather than a measurement of delivery. Overtime records hours spent and rewards effort instead of completed value, which makes it a poor productivity signal.

Correct answer: The formal Scrum framework

Correct answer: The formal Scrum framework. Scrum names three artifacts, the product backlog, the sprint backlog, and the increment, each with a commitment attached, and they exist precisely to make the work visible to everyone inspecting it. The visual Kanban framework relies on a board, work-in-progress limits, and flow metrics, and it defines no artifacts in this sense. The iterative XP framework centers on engineering practices such as pair programming and test-driven development rather than a set of named artifacts. The tailored Crystal framework varies its practices and outputs with team size and criticality, so it prescribes no fixed artifacts at all.

Correct answer: A large block of work that can be split into smaller stories

Correct answer: A large block of work that can be split into smaller stories. An epic is a container far too big to finish in a single iteration, so it is decomposed into features and then into stories that each fit inside one, while the epic itself tracks the larger outcome. A small parcel of work that can be packed into one iteration is a user story, the unit an epic breaks down into rather than the epic itself. A formal review of work that can be slotted into agile gates is a ceremony and carries no scope. A brief meeting of work that can be folded into daily rounds is the daily stand-up, an event rather than a backlog item of any size.

Correct answer: To host Scrum events and remove daily blockers

Correct answer: To host Scrum events and remove daily blockers. The Scrum Master serves as a coach and servant-leader, making sure the events happen and stay useful, and clearing the impediments that stop the team from making progress toward the sprint goal. Ordering Scrum backlogs and setting feature values is the Product Owner's accountability for value and sequence. Briefing Scrum sponsors and voicing buyer wishes is also the Product Owner's work, since that role carries the customer voice into the team. Auditing Scrum outputs and raising build quality belongs to the developers, who own the technical standard of what they produce.

Correct answer: JIT product replenishment

JIT product replenishment is the Lean answer: Just-In-Time releases work only when a downstream demand signal arrives, so nothing is built ahead of need and overproduction disappears. SMED changeover reduction shortens machine setup time; it makes small batches affordable but never decides when a batch is released. TOC bottleneck management paces the line to the single constraining resource, which is an internal limit rather than a customer demand signal. OEE equipment measurement is a utilization metric that scores availability, performance and quality after the fact, and a metric cannot pull work.

Correct answer: To describe a feature as the end user experiences it

A user story exists to describe a feature as the end user experiences it, stating who wants the capability and what value it delivers, so the team builds outcomes rather than components. Validating a delivery as the pilot user approves it is acceptance testing, which happens after the story is built. Estimating a workload as the senior user reviews it is sizing, a planning activity that consumes stories instead of defining them. Documenting a problem as the support user records it is a defect report, which describes something already broken rather than a wanted capability.

Correct answer: Adaptive Planning

Adaptive Planning is the practice of revisiting priorities and plans every iteration in the light of feedback and measured results, so the plan changes as knowledge grows. Feature Branching is a source-control practice that isolates code in progress and says nothing about priorities. Backlog Splitting breaks large items into smaller ones; it changes item size, not the ordering or the plan behind it. Refactoring Cycle improves the internal structure of existing code without altering behavior, so it cannot reassess what the team should build next.

Correct answer: Test-Driven Development 'TDD'

Test-Driven Development 'TDD' is the Extreme Programming practice in which a failing automated test is written first and production code is then written only to make that test pass. Acceptance-Test Signoff 'UAT' comes at the end of delivery, when users confirm finished software against business needs. Integration-Test Stages 'SIT' exercise assembled components after each part has already been coded. Stress-Test Verification 'QA' loads a completed build beyond normal volumes to find its breaking point, so all three run after the code exists rather than before it.

Correct answer: Lean Methodology

Lean Methodology is built on removing anything the customer would not pay for and improving the remaining flow in small steps, which is precisely the pairing of waste reduction with value maximization described here. The Waterfall Method moves through fixed sequential phases with heavy handover documents and tolerates rework rather than attacking it. The Spiral Lifecycle repeats risk-driven cycles and is organized around retiring risk, not around eliminating waste. The Rational Process prescribes disciplined phases, roles and artefacts for software delivery, so its focus is governed process rather than continuous waste removal.

Correct answer: Agile Methodology

Agile Methodology is the one built on adaptive planning, evolutionary development, early and frequent delivery and continual improvement, and its whole premise is welcoming change late in development. The Waterfall Process fixes requirements at the outset and moves forward through sequential phases, so late change is treated as a defect in planning. Structured Design decomposes a system into modules from a complete specification and assumes that specification is settled before building starts. Change Management is the discipline of assessing and approving alterations once they are raised, which controls change instead of advocating a way of delivering work.

Correct answer: By visualizing flow, limiting work in progress, and maximizing efficiency

Kanban helps by visualizing flow, limiting work in progress, and maximizing efficiency: the board makes every item and its state visible, the column limits stop the team from starting more than it can finish, and the resulting pull exposes bottlenecks. Scheduling jobs, recording time in timesheets, and reporting variances is classic time and cost control, which measures work rather than limiting it. Forecasting outlay, checking costs in ledgers, and certifying balances is financial administration. Recruiting staff, assigning roles in teams, and appraising performance is people management and never touches the flow of work items.

Correct answer: Product owner, scrum master, and development team

The three Scrum accountabilities are the product owner, scrum master, and development team: the product owner answers for product value and backlog ordering, the scrum master coaches the team and clears impediments, and the developers build the increment. A project sponsor, agile coach, and delivery squads mixes a governance role with coaching and team titles that Scrum does not define. A product manager, release train engineer, and agile teams are roles from the Scaled Agile Framework, not Scrum. A business owner, project lead, and technical staff describe a traditional project hierarchy, which Scrum's self-managing team replaces.

Correct answer: The daily standup; to synchronize the team and uncover impediments swiftly

A short gathering each day where members say what they did, what they will do, and what is blocking them is the daily standup, and its purpose is to synchronize the team and uncover impediments swiftly. An iteration review demonstrates the finished increment to stakeholders and happens once per cycle, not once per day. Sprint planning selects and sizes the work for the coming cycle, so it looks forward across weeks rather than across one day. A retrospective inspects how the team works and agrees improvements, which is about process rather than daily coordination.

Correct answer: For the team itself, to coordinate; it is time-boxed to about 15 minutes

The event belongs to the team itself, who use it to coordinate their own plan for the coming day, and it is time-boxed to about 15 minutes. It is not a report to management; turning it into one makes the team perform for an audience instead of planning together. It is not a client approval session either, since acceptance of the increment happens at the review. And it is not a slot for the scrum master to hand out assignments, because a self-managing team decides its own next steps.

Correct answer: The sprint retrospective

The end-of-iteration event in which a team inspects its own way of working and agrees improvements for the next cycle is the sprint retrospective. Refinement clarifies and orders the work still waiting to be built, so it examines the product rather than how the team collaborates. A morning coordination event synchronizes the coming day's plan and is far too short and too frequent to serve as a considered review of working practice. A stakeholder showcase presents finished work and gathers feedback on the product, which inspects the result rather than the process that produced it.

Correct answer: The product backlog

The single ordered, continually evolving list of features, fixes, and requirements that the product owner keeps is the product backlog, and it is the only source of work the team draws from. A product roadmap sketches broad themes and intended timing at a much coarser grain, so it cannot be pulled from directly. A product charter authorizes the effort and sets its goals, which is a founding document rather than a working queue. A product catalog lists what already exists and is offered to customers, not what remains to be built.

Correct answer: An agile, adaptive approach with repeated incremental rollouts

An agile, adaptive approach with repeated incremental rollouts fits, because the requirements are expected to move as customers react to working software and the sponsor wants usable functionality in their hands early and repeatedly. An audited, phased approach with scheduled checkpoints controls change rather than welcoming it, so each new customer insight becomes an exception to process. A fixed, sequenced approach with detailed upfront requirements assumes the scope is knowable before anyone sees the software, which is the opposite of the situation described. A combined approach with paired parallel workstreams describes how work is divided among people and says nothing about how often value reaches the customer.

Correct answer: Predictive fixes scope, schedule, and cost up front, while agile lets features evolve later

Predictive fixes scope, schedule, and cost up front, while agile lets features evolve later. That is the real dividing line: a plan-based approach defines the full scope in detail at the start and manages every departure against the approved baseline, whereas an adaptive approach holds time and cost steady and allows the content of the work to change as the team learns. Claiming predictive skips documentation reverses the two, since plan-based delivery is the heavily documented one. Claiming predictive ships in short cycles while agile delivers at the end reverses the cadence as well. How many roles or owners a method uses is an organizational detail, not the difference in how scope is treated.

Correct answer: The definition of done

The definition of done is the shared checklist of quality criteria that every backlog item must satisfy before it may count toward the increment, so it is the objective completion standard the developer is asking about. The sprint goal states the single objective for the sprint and does not judge whether an individual item is finished; the team working agreement sets norms for how members collaborate rather than quality criteria for the work; and the sprint burndown chart tracks remaining work over time without defining what complete means.

Correct answer: The sprint review event

The sprint review event is the working session at the end of the iteration where the team and its stakeholders inspect the increment, gather feedback and decide what to do next. The daily standup event is a short internal synchronization with no stakeholders present; the team planning event selects work at the start of the iteration instead of inspecting what was built; and the quality audit event tests conformance to process rules, not the increment itself.

Correct answer: The sprint retrospective

The sprint retrospective is the event in which the team privately inspects its own people, interactions, processes and tools and then plans improvements for the next iteration. The product presentation shows finished work to stakeholders and so looks at the product rather than the way of working; the delivery examination confirms that outputs match their specification; and the increment assessment judges what was built, not how the team built it.

Correct answer: A brief, set-length time-box during which a usable increment is generated

A sprint is a brief, set-length time-box during which a usable increment is generated, and its duration stays constant so the team builds a predictable rhythm. A vague, open-ended timeframe contradicts the set length that defines a sprint; a brief, half-day conference describes an estimating session rather than the iteration itself; and a closing, one-off handover describes end-of-project acceptance, which happens once instead of every iteration.

Correct answer: The product backlog

The product backlog is the single ordered list of everything that might be needed in the product, continuously refined and reordered by the product owner. The release roadmap plots planned themes and releases across time rather than ordering individual items; the scope statement fixes the agreed boundary of the work and is not continuously reprioritized; and the change register logs requested changes to a baseline rather than everything the product might need.

Correct answer: The sprint backlog

The sprint backlog is the set of product backlog items selected for the iteration together with the plan for delivering them, and the developers own and update it daily. The burndown chart plots remaining work over time rather than holding the selected items and their plan. The iteration goal is the single objective the sprint serves, not the set of items and the plan to deliver them. The release plan spans several iterations and forecasts larger scope, so it is broader than one sprint's commitment.

Correct answer: Story points

Story points are the relative unit that captures effort, complexity and uncertainty for a backlog item instead of a count of hours. Budget hours are precisely the absolute time estimate the team chose not to use; actual costs record money already spent and reveal nothing about the size of the items still to come; and elapsed days state how long something took rather than how large it was.

Correct answer: Velocity

Velocity is the number of story points a team actually completes each iteration, averaged across recent iterations to forecast what it can take on next. Capacity is the time the team has available rather than the work it has finished; variance compares an achieved result against a baseline; and duration states how long something takes, not how much was delivered.

Correct answer: A burndown chart

A burndown chart plots the work still remaining against the days of the iteration, so its line falls toward zero as the sprint ends. A velocity chart compares completed totals across past sprints instead of tracking the current one; a schedule chart lays out dated activities; and a resource chart shows who is assigned, and neither of those trends to zero within an iteration.

Correct answer: A burnup chart

A burnup chart draws completed work as a rising line and total scope as a second line, so scope that is added or removed appears immediately as a change in the upper line. A demand chart shows incoming requests; a defect chart counts faults found in testing; and a points chart totals sizing values, and none of the three separates delivered work from the scope it is measured against.

Correct answer: A kanban board

A kanban board maps the stages of a workflow as columns and shows every work item as a card that moves from left to right, so queues and blockages become visible to everyone. A RACI diagram allocates responsibility for tasks and displays no flow at all; a fishbone map traces the causes of a single problem; and a scatter plot tests whether two variables move together, so none of them tracks items across workflow stages.

Correct answer: A flow-based method that visualizes tasks, limits work in progress, and pulls items as capacity frees up

Kanban is a flow-based method that visualizes tasks, limits work in progress, and pulls items as capacity frees up, optimizing continuous flow instead of fixed iterations. The time-boxed description belongs to Scrum, which does prescribe iterations, roles and events; the cost-shared description is a procurement arrangement for splitting savings with a supplier; and the float-driven description is critical chain scheduling, a predictive technique for buffering a network.

Correct answer: A WIP limit, which improves flow and exposes bottlenecks

A WIP limit, which improves flow and exposes bottlenecks, is the name for a cap on how many items may sit in a column at once; the cap cuts multitasking, shortens cycle time and makes a constrained stage visible because work piles up in front of it. A CCM buffer absorbs schedule variation and caps nothing; a PBI goal states an objective for one item instead of limiting flow; and a QMS standard fixes quality criteria, which is a different kind of rule altogether.

Correct answer: Scrum uses fixed-length sprints with set roles and events, while Kanban uses continuous flow with WIP limits and optional iterations

The accurate contrast is that Scrum uses fixed-length sprints with set roles and events, while Kanban uses continuous flow with WIP limits and optional iterations. Scrum does not run open-ended stages with a single owner, and Kanban has no change control board approving work; Scrum does not front-load plans around cost codes, and Kanban does not batch releases around earned value reporting; and neither framework builds hierarchical charts or hands scope control to a project management office.

Correct answer: Product owner, scrum master, and developers

The three accountabilities are product owner, scrum master, and developers: the product owner maximizes value and orders the backlog, the scrum master fosters effectiveness and clears impediments, and the developers build the increment. A sponsor and a coach sit outside the framework, and coaching is not an accountability within it; engineer, analyst and tester are job titles rather than accountabilities; and a manager with an oversight group describes governance roles the framework does not define.

Correct answer: Remove the impediment by raising the supplier delay and fixing the broken tooling

Remove the impediment by raising the supplier delay and fixing the broken tooling is the correct action, because a scrum master serves the team by clearing obstacles and coaching rather than directing work. Approving changes and ranking features is the product owner's decision; assigning workloads and tracking logged estimates is the directive management a scrum master avoids; and reordering the backlog by client value again belongs to the product owner.

Correct answer: Iterative development

Iterative development is the approach in which the team repeatedly revisits the same solution, using feedback from each cycle to refine it until it meets the need. Predictive estimation produces up-front figures rather than a way of building the product; progressive execution names no recognized delivery approach and describes only steady effort; and resource optimization adjusts assignments and workloads, which says nothing about repeating cycles of refinement.

Correct answer: Incremental delivery

Incremental delivery is the term for handing over finished, usable slices of functionality one at a time so stakeholders gain value before the whole product exists. Schedule compression shortens a plan by crashing or fast tracking and delivers nothing early; governance oversight reviews decisions rather than releasing functionality; and scheduled acceptance is a single sign-off point at the end, which is the opposite of releasing in pieces.

Correct answer: That the development approach is tailored for every part of the work

The decision demonstrates that the development approach is tailored for every part of the work, blending predictive and agile methods within one project where each fits best. Current guidance does not ban the predictive approach; it explicitly supports hybrids. Enforcing one standard approach across every portion contradicts the whole idea of tailoring, and nothing blocks the iterative approach either, since the evolving customer-facing features are exactly where it belongs.

Correct answer: Servant leadership

Servant leadership is the style described: the leader serves the team by clearing obstacles, supplying resources, and enabling self-organization. Transactional leadership manages through rewards, penalties, and agreed performance terms rather than by removing obstacles. Democratic leadership invites the team to vote on or share in decisions, but it describes how choices are made rather than a leader clearing obstacles and supplying resources. Passive leadership steps back and intervenes only when problems force it, offering none of the active support the stem describes.

Correct answer: The daily scrum standup

The daily scrum standup is the short event held every day and time-boxed to roughly a quarter of an hour, in which the developers synchronize, inspect progress toward the sprint goal and replan the coming day. The sprint demo session shows the increment to stakeholders once per iteration; the stage gate handover is a predictive checkpoint between phases; and the team charter review revisits working agreements rather than the plan for tomorrow.

Correct answer: Cycle time

Cycle time is the elapsed time from the moment active work starts on an item until that item is finished and ready for delivery. Lead time runs from the moment the item is requested, so it also includes the waiting before work begins; queue time counts only that waiting and none of the active work; and buffer time is a reserve added to a schedule to absorb delays, which is a planning allowance rather than a flow metric.

Correct answer: Deliver the highest-value work early to increase return and gather feedback

Deliver the highest-value work early to increase return and gather feedback is the principle behind ordering a backlog by value: benefit arrives sooner and so does the learning that shapes what comes next. Postponing the highest-risk work defers exactly the learning the team needs most; scheduling the highest-cost work later smooths spending but ignores value; and handling every item evenly abandons ordering altogether, which is the opposite of what the product owner is doing.

Correct answer: To keep pending backlog items clear, estimated, and prioritized so sprints can launch smoothly

The goal of refinement is to keep pending backlog items clear, estimated, and prioritized so sprints can launch smoothly; it is a continuous activity that readies work ahead of the iteration that will use it. Pricing, staffing and contracting items is procurement rather than refinement; ranking items as approved and resourced describes a funding gate the product owner does not run; and merging and archiving duplicates is housekeeping that does not prepare work for delivery.

Correct answer: It yields recurring feedback and reduces the risk of building the wrong things

Demonstrating a working increment every two weeks yields recurring feedback and reduces the risk of building the wrong things, because course corrections happen early and often. It does not abolish testing, since the increment has to be integrated and tested to be shown at all; it guarantees nothing about the budget, which depends on scope and cost drivers; and it does not retire the product owner, whose ordering of the backlog decides what each increment contains.

Correct answer: To capture requirements from the user viewpoint and clarify the value delivered

Writing a story as a role, a capability and a benefit exists to capture requirements from the user viewpoint and clarify the value delivered, which keeps the team focused on outcomes rather than outputs. Recording system functions in technical detail is the job of a specification, whereas stories are deliberately short, plain-language placeholders for a conversation. Freezing the full product scope and locking down the architecture early is a predictive habit, and stories assume scope will evolve. Assigning work items to individual developers and tracking their working hours is task administration that says nothing about why the work matters to a user.

Correct answer: Acceptance criteria

Acceptance criteria are the conditions a single story must satisfy before the team will call it satisfactory, which is exactly what the stem describes. Baseline tolerances are the permitted variation around an approved plan and belong to predictive control; delivery thresholds set limits for releasing rather than conditions for one story; and iteration forecasts predict how much will be completed, which says nothing about whether a story is acceptable.

Correct answer: Self-organizing teams

Self-organizing teams are the agile characteristic described: the team itself decides how to turn its work into a finished increment rather than being told how. Cross-functional teams hold all the skills needed to deliver, which concerns capability rather than who decides how the work is done; co-located teams sit together in one place to ease communication, which concerns where they work; and servant-led teams are supported by a leader who removes obstacles, which describes the leader's style rather than the team's own authority over its methods.

Correct answer: A spike

A spike is the time-boxed research or prototyping activity a team runs to answer a technical question and cut uncertainty before it commits to an item. A sprint is the fixed-length iteration in which committed items are delivered, not a focused investigation ahead of commitment; a retro is the retrospective where the team reflects on how it worked, which looks back rather than resolving a technical unknown; and a demo shows completed work to stakeholders, which presents results instead of exploring a question.

Correct answer: Transparency, inspection, and adaptation

Transparency, inspection, and adaptation are the empirical pillars: make the work visible, examine it at regular intervals, and change course on what is learned. Standardization, prediction, and control describe a defined process model that assumes the work is known in advance, the opposite of empiricism; communication, simplicity, and feedback are values of Extreme Programming; and commitment, openness, and courage are among the Scrum values, which guide team behavior rather than forming the empirical pillars.

Correct answer: An adaptive delivery lifecycle

An adaptive delivery lifecycle is the one described: short cycles each produce a tested, usable increment and the learning from one cycle shapes the next. An ordered waterfall lifecycle runs a single pass through requirements, build and test, so feedback arrives only at the end; an unchanging staged lifecycle gates between phases without reworking earlier ones; and an untouched charter lifecycle fixes everything up front, which is why late corrections become expensive.

Correct answer: A cumulative flow diagram

A cumulative flow diagram stacks the quantity of work sitting in each workflow stage over time, so a widening band shows exactly where items are piling up and flow is constrained. A cycle time scatter plot shows how long individual items took to finish but not how many sit in each stage; a team velocity bar chart shows how much work was completed in each sprint; and a release burndown chart tracks total remaining work against time, so none of them exposes where work is accumulating between stages.

Correct answer: Minimum viable product

Minimum viable product is the concept that guides releasing as soon as the increment carries enough value to be useful and to teach the team something from real users. An approved final product is the complete, signed-off version, which is precisely what the owner is being told not to wait for; an iteration zero product is scaffolding built before delivery starts and carries no user value; and a threshold gate product names a governance checkpoint rather than a release decision.

Correct answer: Continuous integration

Continuous integration is the practice described: small changes go into the shared codebase often, and automated builds and tests check each one so defects surface at once. Contracted integration hands assembly to a supplier under an agreement and does nothing about frequency; downstream integration pushes the merge to a later stage, which is what the practice avoids; and sequential integration joins components one after another at the end, recreating the large, late merge.

Correct answer: Because it lets the team get fast answers and adapt to evolving demand, cutting rework

Continuous collaboration matters because it lets the team get fast answers and adapt to evolving demand, cutting rework and keeping the product aligned with value. It does not let anyone drop the backlog, which remains the ordered source of work; it does not hand every decision to the developers, since the product owner still decides what is built; and it does not freeze scope, because agile expects scope to change and close contact is how the team absorbs that change.

Correct answer: A scaled agile framework such as SAFe or Nexus

A scaled agile framework such as SAFe or Nexus exists specifically to align several agile teams building one product, coordinating their backlogs, cadences and dependencies. A lean agile approach such as Kaizen or Kanban improves flow inside a single team and prescribes nothing about cross-team alignment; a risk analysis method quantifies uncertainty; and a fixed price agreement is a contract structure, not a way of organizing teams.

Correct answer: Planning poker

Planning poker is the card-based technique in which every member reveals a relative estimate at the same moment and the team then talks through the outliers, which limits anchoring. Delphi polling gathers estimates anonymously across several rounds and deliberately keeps the experts apart rather than discussing face to face; expert opinion relies on one informed judgment instead of the whole team; and parametric fit calculates a figure from historical rates, using no cards and no discussion.

Correct answer: Flow efficiency

Flow efficiency is the share of an item's total elapsed time that is active work rather than queue time, so a team raising the proportion of active time is working on flow efficiency. Flow velocity counts how many items finish per period and says nothing about waiting; flow distribution describes the mix of work types the team takes on, not the timing of any one item; and flow visibility concerns how clearly the workflow is displayed on a board, which can reveal queues but is not the ratio being measured here.

Correct answer: A steady cadence keeps velocity comparable and forecasts dependable

A steady cadence keeps velocity comparable and forecasts dependable is the reason: an unchanging iteration length makes the work completed in each iteration directly comparable, which is exactly what gives velocity meaning and makes forecasting reliable. A frozen backlog that keeps priorities unchanged and estimates permanent is not what a fixed length buys, because the backlog goes on changing. A padded iteration that keeps commitments tentative and overtime routine is the opposite of a fixed boundary. And a shared checkpoint that keeps stakeholders engaged does not make reviews optional, since inspecting the increment at the boundary is part of what the fixed boundary exists for.

Correct answer: Predictive methods may fit this initiative better than a totally adaptive one

Predictive methods may fit this initiative better than a totally adaptive one: stable, well-defined requirements, low expected change and heavy up-front regulatory documentation are precisely the conditions in which plan-based delivery outperforms an adaptive life cycle. Iterative delivery is not the better fit here, because iteration buys learning the team does not need when requirements are already settled. Frequent releases do not replace a formal change board on regulated work, where the change record is part of the evidence. Emergent design is the wrong choice against a fixed requirement set, since the set is known in advance and is what the regulator will inspect.

Correct answer: It is potentially releasable, and the product owner sets the release date

It is potentially releasable, and the product owner sets the release date: meeting the definition of done makes the increment fit to release, while when to release is a business decision the product owner owns. It is not formally unfinished, because the definition of done is the completeness test and the increment met it. It is not wholly uncounted either, since work that meets the definition of done counts toward velocity whether or not it ships. And it is not already obsolete, because holding a finished increment for a later release date does not degrade it.

Correct answer: Requirement elicitation via prototypes

Requirement elicitation via prototypes surfaces hidden needs best on a complex project, because stakeholders react to something concrete and say what is missing rather than trying to imagine it in the abstract. Requirement validation via inspections tests whether an already stated requirement delivers business value, so it cannot reveal one nobody has stated. Requirement prioritization via surveys ranks requirements that have already been captured. Requirement verification via briefings checks that written requirements meet quality criteria such as clarity and testability, which again presumes they exist.

Correct answer: Data Flow Diagram

A Data Flow Diagram is the technique built for this purpose: it shows processes, external entities, data stores and the data moving between them, which is exactly how a system's processing is documented. A Gantt Bar Diagram plots activities against a calendar and carries no processing logic at all. A Fish Bone Diagram arranges candidate causes of a single problem into categories, so it explains a defect rather than a process. A Cash Flow Diagram tracks money in and out over time and belongs to financial appraisal, not systems documentation.

Correct answer: MoSCoW method

The MoSCoW method sorts every requirement into Must have, Should have, Could have and Won't have, which is a direct statement of relative value to stakeholders and to the objectives, and it is therefore the prioritization tool wanted here. Pareto charts rank defect or failure categories by frequency, so they prioritize problems rather than requirements. Delphi rounds build anonymous expert consensus on an estimate or a forecast and produce no ordered requirement list. Scatter plots display the relationship between two measured variables and carry no ranking at all.

Correct answer: Strategy Analysis

Strategy Analysis is where stakeholders are identified and assessed, because that work establishes the current state, the desired future state and who has a stake in moving between them before any solution is shaped. Solution Analysis judges a delivered or proposed solution against measured value, which happens long after stakeholders have been catalogued. Workflow Analysis maps the sequence of steps in an existing process and produces a process model, not a stakeholder assessment. Scenario Analysis tests how outcomes change under alternative future conditions and treats stakeholders as inputs that are already known.

Correct answer: To evaluate organizational achievement from distinct perspectives

A Balanced Scorecard exists to evaluate organizational achievement from distinct perspectives, pairing the financial view with customer, internal process and learning and growth views so that no single lens dominates. Demonstrating departmental efficiency from published comparisons describes benchmarking, which measures one organization against others rather than balancing several internal views. Extrapolating incremental investment from discounted projections is a financial appraisal technique and sits inside only one of the four perspectives. Standardizing procurement disclosures from mandated publications is a compliance activity with no performance framework behind it.

Correct answer: Root Cause Analysis

Root Cause Analysis is the technique that keeps asking why a problem occurred until the underlying condition is exposed, so the fix removes the source instead of the symptom. Cause Loop Analysis charts reinforcing and balancing feedback between variables in a system, which explains ongoing behavior rather than pinpointing one originating fault. Cost Trend Analysis tracks how spending moves over time and answers a budget question, not a causal one. Life Cycle Analysis totals the cost or impact of an asset from acquisition to disposal, so it evaluates a whole asset rather than diagnosing a single failure.

Correct answer: Examining the project's strengths, weaknesses, opportunities, and threats

The benefit of a SWOT is exactly that it sets out examining the project's strengths, weaknesses, opportunities, and threats, pairing the two internal factors with the two external ones so decisions rest on a complete picture. Sequencing the project's milestones, durations, dependencies, and buffers is schedule development and produces a network, not a strategic picture. Forecasting the project's cashflows, benefits, commitments, and overheads is cost planning and touches only money. Documenting the project's deliverables, exclusions, acceptance, and dates defines scope, which fixes what will be produced rather than weighing internal and external conditions.

Correct answer: 80% of issues are created by 20% of sources

Applying Pareto tells you that 80% of issues are created by 20% of sources, so effort concentrates on the small number of vital sources that generate most of the loss. Saying 40% of issues are created by 60% of sources spreads causation across most sources, which is the opposite of the principle. Saying 20% of issues are created by 80% of sources inverts the ratio, leaving no vital few to target. Saying 60% of issues are created by 40% of sources describes only a mild imbalance that falls well short of the 80/20 concentration the principle predicts.

Correct answer: Requirements traceability matrix

A requirements traceability matrix links every requirement forward to the deliverable and test that satisfy it and backward to the objective that justified it, which is how a team proves nothing was dropped and nothing unjustified was built. A requirements prioritization list ranks items by importance but does not show whether they were delivered or tie them to an objective. A requirements elicitation summary records what was heard during gathering sessions and stops before delivery begins. A requirements acceptance register logs customer sign-off on items without linking each one to the objective or the test behind it.

Correct answer: Governing and maintaining requirements from creation to retirement

Requirements Life Cycle Management is about governing and maintaining requirements from creation to retirement, which covers tracing, prioritizing, approving and reassessing each requirement for as long as it exists. Estimating and scheduling requirements from submission to handover is planning work and belongs to the planning and monitoring area. Collecting and ordering requirements from stakeholders to sponsors is elicitation and prioritization, which is only the first part of the life cycle. Allocating and resourcing requirements from analysts to developers is staffing, which assigns people rather than governing the requirements themselves.

Correct answer: To recognize how operations within an organization produce value for customers

Value Chain Analysis exists to recognize how operations within an organization produce value for customers, breaking the firm into primary and support activities so the margin added by each can be judged. Establishing how departments within an organization control funds for projects is financial planning and describes how money is divided, not how value is produced. Estimating how directors within an organization report value for shareholders concerns investor communication rather than the activities themselves. Explaining how committees within an organization approve tenders for suppliers describes procurement governance, which is one narrow support activity and not the chain as a whole.

Correct answer: System Dynamics Modeling

System Dynamics Modeling is the tool suited to this, because it represents stocks, flows, feedback loops and delays and therefore shows how the parts of a complex system influence one another over time. Critical Path Scheduling arranges activities into a dependency network to find the longest path, so it models a plan rather than a system. Earned Value Forecasting converts cost and schedule performance into projections and produces indices, not a structural picture. System Storyboard Charts sketch a sequence of screens or events for review and capture presentation order rather than the interactions between components.

Correct answer: PESTLE Analysis

PESTLE Analysis scans the political, economic, social, technological, legal and environmental conditions surrounding a project, which is exactly the set of outside forces that can help or wreck it. Pareto Analysis ranks the causes of defects or problems by frequency, a quality tool rather than an environmental scan. MoSCoW Analysis sorts requirements into must, should, could and won't have, which is prioritization of scope. VRIO Analysis tests whether a resource is valuable, rare, inimitable and organized for use, which judges internal capability rather than the outside environment.

Correct answer: To describe the behaviors that a system can perform with outside users

A Use Case Diagram exists to describe the behaviors that a system can perform with outside users, drawing actors beyond the boundary and the goals they pursue inside it. Itemizing the expenses that a sponsor can approve with agreed budgets is cost control and has no notion of an actor or a system boundary. Recording the problems that a tester can reproduce with scripted cases belongs to test management and concerns faults in built software. Measuring the savings that a manager can realize with revised methods is benefits analysis, which values an outcome instead of modeling system behavior.

Correct answer: Exposing discrepancies between present project state and target outcomes

Gap Analysis means exposing discrepancies between present project state and target outcomes, because naming the distance between where you are and where you intend to be is what tells you which actions close it. Allocating resources between approved project teams and external vendors is resource management and assumes the target is already agreed. Splitting payments between completed project stages and remaining claims is a payment schedule and measures money rather than capability. Comparing submissions between competing project bids and published rates is procurement evaluation, which ranks suppliers instead of exposing a shortfall against an objective.

Correct answer: To identify how concerned stakeholders will be affected by a project

A Stakeholder Impact Analysis is conducted to identify how concerned stakeholders will be affected by a project, so that interests, expectations and likely reactions are understood before the change lands. Recording how external stakeholders will be consulted by a committee is engagement planning, which decides communication mechanics after the impacts are already known. Assessing how technical stakeholders will be retrained by a supplier is a training need and covers only one consequence for one group. Confirming how regulatory stakeholders will be audited by a reviewer is a compliance arrangement and describes scrutiny of the project rather than its effect on people.

Correct answer: By presenting a graphic layout with blocks outlining a firm's value proposition, infrastructure, customers, and finances

The Business Model Canvas assists by presenting a graphic layout with blocks outlining a firm's value proposition, infrastructure, customers, and finances, so the whole business logic sits on a single page and can be challenged block by block. Scheduling a fixed timetable with deadlines governing a team's sprint sequence, milestones, handovers, and completion is a delivery plan and says nothing about how the business earns. Compiling a ranked register with balances recording a buyer's credit exposure, collateral, guarantees, and repayments is credit administration. Negotiating a formal contract with clauses binding a vendor's service targets, penalties, warranties, and indemnities is procurement drafting, which governs one supplier relationship rather than the business model.

Correct answer: SWOT Analysis

SWOT Analysis is the tool that sets internal strengths and weaknesses against external opportunities and threats in one grid, which is exactly how strategic fit between capability and opportunity is judged. PERT Analysis weights optimistic, likely and pessimistic durations to estimate an activity's expected time, so it addresses schedule uncertainty only. FMEA Analysis ranks potential failure modes by severity, occurrence and detection and is a reliability method. MOST Analysis traces mission, objectives, strategies and tactics downward through an organization, so it stays wholly inside the firm and never examines the external environment.

Correct answer: Stakeholder Mapping

Stakeholder Mapping plots each party on a grid such as power against interest, so the level of influence and the attention each one deserves become visible at a glance. Stakeholder Workshops bring people together to elicit requirements or build agreement, not to classify their power and interest. Influence Diagramming models how decisions, uncertainties, and outcomes affect one another in decision analysis, so it deals with variables rather than people. The Delphi Technique gathers anonymous expert opinion over several rounds to reach consensus on an estimate or forecast, and it does not assess where stakeholders stand.

Correct answer: To determine the areas that must be successfully managed to achieve project objectives

The Critical Success Factor method exists to determine the areas that must be successfully managed to achieve project objectives, concentrating management attention on the few conditions without which the work cannot succeed. Estimating the effort and budget for each requirement is cost and effort estimation, which sizes the work rather than naming what must go right. Identifying whose sign-off is needed before the project begins is stakeholder and approval analysis, which maps authority rather than success conditions. Comparing individual employees against appraisal targets is personnel performance management and says nothing about what the initiative itself needs to succeed.

Correct answer: It supplies a consistent approach for describing business procedures

BPMN matters because it supplies a consistent approach for describing business procedures: the same symbols for events, activities, gateways and flows mean a model drawn by one analyst reads identically to everyone else. Saying it delivers a sequential catalog for monitoring business incidents describes an incident log, which records occurrences instead of modeling how work proceeds. Saying it establishes a weighting algorithm for ranking supplier quotations describes a procurement scoring scheme. Saying it prescribes a mandatory timetable for approving contract purchases describes a purchasing control, and none of the three carries any notation at all.

Correct answer: Context Diagram

A Context Diagram shows the system as a single process bounded against the external entities around it, with the information passing in and out drawn as labeled flows, which is why it answers what enters and what leaves. A Network Diagram links activities by dependency to expose the critical path, so it models schedule logic. A Scatter Diagram plots paired measurements to reveal correlation between two variables. A Tornado Diagram ranks the sensitivity of an outcome to each input, so all three display numbers or timing rather than information moving through a system.

Correct answer: The set of tasks that elicit, analyze, record, and validate requirements so the solution delivers business value and meets stakeholder needs

Business analysis is the set of tasks that elicit, analyze, record, and validate requirements so the solution delivers business value and meets stakeholder needs; it is the discipline that connects the business problem to what the solution must do. Initiating, organizing, controlling, and closing project activities so the effort finishes on schedule and within budget is project management, which delivers against requirements rather than defining them. Selecting, prioritizing, funding, and monitoring projects so the portfolio supports strategic goals is portfolio management, which chooses among initiatives rather than shaping the solution inside one. Preparing, informing, mentoring, and supporting impacted users so the organization embraces the change is organizational change management, which drives adoption of a solution rather than determining what it must do.

Correct answer: Gathering, assessing, and handling the product requirements with stakeholders

Gathering, assessing, and handling the product requirements with stakeholders is the business analyst's core work, because the analyst defines what the solution must do. Planning, sequencing, and controlling the delivery schedule is schedule management, which the project manager owns. Estimating, monitoring, and reporting the cost baseline is cost management, which stays with the project manager even when finance officers supply figures. Acquiring, developing, and managing the project team is resource management, which the project manager leads with functional managers rather than handing to the analyst.

Correct answer: A structured set of techniques and practices for conducting business analysis activities such as elicitation, modeling, prioritization, and validation

A business analysis framework is a structured set of techniques and practices for conducting business analysis activities such as elicitation, modeling, prioritization, and validation; it tells the analyst how to do the work. A standardized set of processes and controls for scheduling, budgeting, and procurement is a project management methodology, which governs delivery rather than analysis. A commercial set of software tools and repositories for storing artifacts is requirements-management tooling, which holds outputs but prescribes no method. A mandated set of policies and approval gates for investment decisions is portfolio governance, which decides what gets funded rather than how analysis is performed.

Correct answer: A requirement of the business for the whole enterprise

The statement is a requirement of the business for the whole enterprise, which is what a business requirement is: a high-level need or goal expressed for the organization as a whole, here staying competitive by cutting order-processing time. It is not a requirement for one stakeholder role, because no particular group or user is named. It is not a requirement for the planned solution, because it describes no system behavior or quality the solution must exhibit. And it is not a requirement for the transition phase, because nothing about moving from the current state to the future state is described.

Correct answer: A functional requirement naming a discrete behavior

Sending a confirmation email when an order is submitted is a functional requirement naming a discrete behavior: it states one specific thing the solution must do. It is not a transition requirement naming a migration routine, because it describes steady-state operation rather than the temporary work of moving to the new system. It is not a stakeholder requirement naming a specific concern, because it is written as system behavior rather than as one group's need. And it is not a nonfunctional requirement naming a quality target, because it sets no threshold for how well the behavior must perform.

Correct answer: A nonfunctional requirement covering a performance quality

A two-second ceiling on search response is a nonfunctional requirement covering a performance quality: it constrains how well the solution must behave, not what it does. It is not a functional requirement covering a verifiable transaction, because no new action or transaction is being specified, only a limit on an existing one. It is not a stakeholder requirement covering a consistent preference, because a measurable response threshold is a solution quality rather than one group's preference. And it is not a business requirement covering a demonstrable improvement, because it sets no organizational goal or benefit.

Correct answer: The activity of drawing information, needs, and expectations from stakeholders

Elicitation is the activity of drawing information, needs, and expectations from stakeholders, and from documents, systems and other sources as well; it is active discovery rather than paperwork. Mapping interests, influence, and authority among stakeholders is stakeholder analysis, which decides whom to engage rather than drawing out what they need. Reporting progress, variances, and escalations to stakeholders is communications management, which pushes information out instead of drawing it in. Documenting requirements, rules, and criteria for stakeholders records what elicitation has already uncovered, so it follows elicitation rather than defining it.

Correct answer: Job shadowing or observation

Job shadowing or observation is the technique of watching people do the work in their own environment, which is exactly what is needed to see how warehouse staff actually perform the task rather than how they describe it. Records analysis or sampling examines artifacts that already exist and cannot reveal undocumented habits. Group brainstorming or polls generates opinions in a room away from the floor. Wireframing screens or demos asks for reactions to a proposed design, which is premature when the current way of working has not yet been understood.

Correct answer: A facilitated workshop

A facilitated workshop is the fit: it puts many stakeholders in one structured, neutrally led session where requirements can be surfaced, argued, and converged on agreement quickly. A sequential interview reaches one person at a time, so it is slow and never produces a shared position. A questionnaire review collects answers without letting participants hear or resolve each other's differences. A dispersed brainstorm generates ideas but has no facilitator or structure to drive the group to a single agreed set of requirements in one sitting.

Correct answer: Prototyping sessions

Handing stakeholders an early mock-up so they can react and refine is prototyping sessions: an approximate model of the solution is built precisely so feedback can sharpen uncertain requirements. Benchmarking studies compare the organization against outside performance standards and produce no model to react to. Interface inspection examines the boundaries between existing systems rather than proposed screens. Collaborative gaming uses structured group play to surface shared understanding, but it does not put a working representation of the solution in front of the stakeholder.

Correct answer: The ongoing work of organizing, tracing, prioritizing, and controlling requirements throughout the project

The ongoing work of organizing, tracing, prioritizing, and controlling requirements throughout the project is the accurate description, because requirements keep evolving and must stay managed until the work ends. Eliciting, interviewing, surveying, and documenting requirements before design starts is elicitation, a single early activity rather than the whole discipline. Inspecting, verifying, validating, and accepting deliverables against signed contracts is end-of-project acceptance, which checks outputs rather than managing the requirements behind them. Logging, assessing, approving, and rejecting change requests against the scope baseline is integrated change control, which handles every kind of change and is only one input to requirements control.

Correct answer: A matrix linking requirements to sources, deliverables, and verifications

A matrix linking requirements to sources, deliverables, and verifications is the requirements traceability matrix, which lets each requirement be followed from its origin through design, build, and testing. A document detailing requirements by owner, urgency, and success criteria is requirements documentation, which describes each requirement but does not link it forward to deliverables and tests. A log recording change requests with their dates, approvals, and outcomes is the change log, which tracks changes rather than individual requirements. A diagram ordering activities by duration, dependencies, and float values is a schedule network diagram, which sequences work and traces no requirements.

Correct answer: Reciprocal linkage showing each requirement against deliverables and tests, which evidences coverage

What the auditor is being shown is reciprocal linkage showing each requirement against deliverables and tests, which evidences coverage: the traceability matrix runs in both directions, so every approved requirement can be followed to what was built and tested, and every built item can be followed back to an approved requirement. Financial linkage against estimates and invoices evidences overspend, which is cost reporting. Scheduled linkage against milestones and slippage evidences lateness, which is schedule reporting. Weighted linkage against influence and positions evidences consensus, which describes stakeholders rather than proving that requirements were delivered.

Correct answer: To rank requirements by value, risk, and dependency so the vital items ship earliest

The goal is to rank requirements by value, risk, and dependency so the vital items ship earliest, which is what lets a team spend limited time and budget on what matters most. To size requirements by effort, duration, and volume so the full plan holds together is estimating, which tells you how big the work is but not which part to do first. To split requirements by owner, ability, and location so the local team keeps moving is resource assignment, which allocates people once the order is already settled. To freeze requirements by scope, date, and release so the final baseline stands firm is baselining, which fixes a reference point and deliberately stops the reordering that prioritization performs.

Correct answer: MoSCoW

Sorting items into Must have, Should have, Could have and Won't have this time is MoSCoW, a prioritization technique whose four named categories are exactly those labels. Kanban is a flow method built on visualizing work and limiting work in progress, not on sorting items into obligation bands. Pareto directs attention to the small share of causes producing most of an effect, which is analysis rather than a categorization scheme. Delphi gathers anonymous expert opinion over successive rounds to converge on an estimate or forecast, and produces no Must or Could grouping.

Correct answer: Scoring sequence from value and effort

Dividing the value an item delivers by the effort to build it, then working the highest results first, is scoring sequence from value and effort: a prioritization approach that buys the most benefit for the least work. Forecasting cost from value and effort is estimating, which predicts what the work will consume rather than which work comes first. Fixing deadlines from value and effort is schedule planning, which dates work whose order has already been settled. Allocating staff from value and effort is resource assignment, which decides who does the work rather than what the team does next.

Correct answer: A user story card

The 'As a [role], I want [goal] so that [benefit]' template is a user story card: a short, negotiable statement of need written from the user's point of view and used as a placeholder for a conversation. A use case report sets out actors, preconditions and numbered interaction steps, which is a far more formal structure than this one sentence. A task ticket log tracks units of work assigned to people, which is not a statement of user need at all. A sprint goal card states the single objective the team commits to for an iteration, not the need of one type of user.

Correct answer: To state the conditions a story satisfies before the team calls it complete

Acceptance criteria exist to state the conditions a story satisfies before the team calls it complete: they give a shared, testable definition of correct behavior for that one story. Stating the estimate a story requires is sizing, which forecasts cost or effort and says nothing about correctness. Stating the supplier a story involves is procurement, which chooses who supplies the work. Stating the developer a story needs is assignment, which decides who builds it; none of those three tell anyone whether the finished story is acceptable.

Correct answer: A product roadmap

A product roadmap is the high-level, time-oriented view asked for: it shows how the product is expected to evolve and which major capabilities are planned across coming releases. A product charter authorizes and frames the work but carries no forward view of capability over time. A product backlog is the ordered, detailed list of work the team will do next, which is far more granular and is not organized by time horizon. A product catalog lists what already exists and is offered today, not what is coming.

Correct answer: The roadmap carries strategic direction and major milestones, while the backlog carries ordered, detailed work

The accurate statement is that the roadmap carries strategic direction and major milestones, while the backlog carries ordered, detailed work: the roadmap is the longer-horizon, higher-level view and the backlog is the granular list the team pulls from. Saying the roadmap carries itemized tickets and hourly projections while the backlog carries broad, corporate themes inverts both artifacts. Saying the roadmap carries scrum routines and facilitator agendas while the backlog carries sponsor, funding records describes neither, since neither artifact is a ceremony schedule or a funding record. And saying the roadmap carries identical contents and equal ordering while the backlog carries renamed, duplicate labels is wrong, because the two differ in altitude, horizon, and how often they change.

Correct answer: The agile product owner

The agile product owner is accountable for maximizing the value of the product and for managing and ordering the backlog so the team always works the most valuable item next. The agile product coach describes the servant-leader who protects the process and removes impediments, which is a facilitation role rather than an accountability for value. The agile product buyer acquires goods and services under contract. The agile product chair presides over a governance forum; neither of those holds the backlog or decides what gets built.

Correct answer: The product owner ranks the value and decides the scope, while the business analyst elicits the needs and details the requirements

In a typical agile setting the product owner ranks the value and decides the scope, while the business analyst elicits the needs and details the requirements that inform those decisions; the two roles overlap, but the decision right on what gets built sits with the product owner. Assigning tasks and tracking timesheets is not how a self-organizing team is run, and writing tests and approving builds is quality work owned by the delivery team. Approving the budget and funding the work is the sponsor's call, and signing contracts and managing suppliers belongs to procurement. Running the ceremonies and clearing blockers is the scrum master's work, and designing the system and coding modules is the developers' job.

Correct answer: Solution evaluation

Measuring whether a deployed solution actually delivered the intended business benefits is solution evaluation, the business analysis work of judging performance and value realized. Solution definition happens earlier and describes what is to be built. Solution estimation forecasts the cost, size or duration of that build. Solution deployment is the act of putting the solution into use, which in this scenario has already happened; none of the three asks whether the promised benefits arrived.

Correct answer: Analyze the shortfall and the causes, then recommend changes that restore the value

The first recommendation is to analyze the shortfall and the causes, then recommend changes that restore the value: a solution that works as built but underdelivers has a benefit problem whose cause must be understood before anything is changed. Canceling the program and the contracts throws away a working solution before the cause is known. Approving the outcome and the findings treats meeting functional requirements as sufficient, which is exactly the confusion the scenario exposes. Replacing the sponsor and the deputies changes who is accountable without touching why the benefits are missing.

Correct answer: To confirm the requirements are complete, clear, consistent, and meet quality standards

Verification asks whether the requirements were written correctly, so its goal is to confirm the requirements are complete, clear, consistent, and meet quality standards. Confirming they are budgeted, assigned and scheduled is planning work that assumes the requirements already exist. Confirming they are valuable, wanted and justified is validation, the different question of whether these are the right requirements to deliver business benefit. Confirming they are cataloged, indexed and archived is records handling, which governs where a requirement is stored rather than how well it is expressed.

Correct answer: Formal requirements validation

Asking whether documented requirements truly reflect the business need and will deliver value is formal requirements validation, which tests whether these are the right requirements. Full requirements verification asks the narrower question of whether they are well expressed: clear, consistent and conforming to quality standards. Early requirements elicitation is the discovery work that produced them in the first place. Iterative requirements tracing follows each requirement to design, build and test artifacts, proving coverage rather than judging business worth.

Correct answer: Because each role carries divergent authority, interests, and duties that shape how requirements are gathered and settled

The analyst separates process owner, process manager, product manager and product owner because each role carries divergent authority, interests, and duties that shape how requirements are gathered and settled; knowing who can decide and who must merely be consulted is what makes elicitation efficient. Separate budgets, cost centers, and sign-offs govern how funds are authorized and disbursed, which is a financial control rather than the reason an analyst tells these roles apart. Distinct reporting lines, grades, and titles govern how escalations travel through the organization, which the governance structure handles rather than requirements analysis. Unique test skills, tools, and access shape how acceptance testing is run, but that happens after requirements are settled and is not why these four roles are distinguished.

Correct answer: Process modeling, drawn as a workflow diagram

Capturing the steps, decisions and flow of an existing process so it can be improved is process modeling, drawn as a workflow diagram: the picture exposes sequence, branching and handoffs where waste and rework hide. Process costing, drawn as a spending forecast, prices the process without showing how it runs. Process staffing, drawn as a skills inventory, records who can do the work rather than how the work moves. Process auditing, drawn as a control register, checks compliance against controls and presumes the process is already understood.

Correct answer: Use case diagrams

Mapping the interactions between actors and a system to capture the goal each actor wants to achieve is what use case diagrams do, which makes use case modeling the technique in play. Root cause charts trace a defect or problem back to its origins and model no actor at all. Data flow mapping follows data as it moves between stores and processes rather than following a user pursuing a goal. Risk impact grids plot threats by likelihood and consequence, which supports risk analysis and not the description of system interactions.

Correct answer: Acceptance, judging the increment against the stated conditions

Checking a delivered increment against criteria fixed in advance and deciding whether it passes is acceptance, judging the increment against the stated conditions; solution or requirement acceptance is exactly this comparison. Smoothing, levelling the increment against the acceptance phase adjusts resource demand within available float and decides nothing about quality. Procurement, ordering the increment against the acceptance term is contract administration with a seller. Refinement, breaking the increment against the acceptance order splits and re-sizes work for future iterations rather than ruling on work already delivered.

Correct answer: Gap analysis

Setting the documented current state beside the desired future state and reading off the differences is gap analysis, which is how the work needed to close the distance is identified. SWOT analysis catalogs internal strengths and weaknesses alongside external opportunities and threats, and it does not compare two states. ROI analysis weighs the expected financial return of an investment against its cost, which can justify a change but does not reveal the work it requires. Root cause analysis traces a problem back to its underlying causes, explaining why the current state exists rather than what must change to reach the future one.

Correct answer: A business case

A document setting out the problem, the options considered, the costs and benefits, and a recommended approach so the investment can be judged is a business case. A business plan describes how an enterprise as a whole intends to operate and earn over a period, not whether one proposed project is worth funding. A business rule is a policy statement constraining how the organization behaves. A business need is the underlying problem or opportunity itself, which the business case analyzes rather than being.

Correct answer: INVEST checks for story quality

The set of qualities used to judge whether one backlog item is well formed is INVEST checks for story quality: Independent, Negotiable, Valuable, Estimable, Small and Testable. SMART targets for story quality describe how an objective should be written and are applied to goals, not to story readiness. DEEP measures for story quality grade the backlog as a whole, asking whether it is detailed appropriately, emergent, estimated and prioritized, rather than judging a single item. RACI mappings for story quality assign responsibility for tasks and say nothing about whether a story is ready.

Correct answer: Gauging stakeholder interest, influence, and impact on the requirements

Gauging stakeholder interest, influence, and impact on the requirements is stakeholder analysis, and it is the activity that tells the analyst whom to involve in requirements work and how deeply. Auditing sign-offs, dates, and versions is configuration control exercised after approval, not a plan for participation. Tallying edits, comments, and revisions measures requirement churn, which says nothing about who should contribute. Forecasting budget, savings, and payoff builds the business case rather than the engagement approach.

Correct answer: Document analysis

Document analysis is the elicitation technique of mining material that already exists - manuals, regulations, and system documentation - for requirements and current-state facts. Guided interviews draw on one person at a time and produce new statements rather than recorded ones. Moderated surveys poll people in writing, which is again fresh input rather than existing record. Rapid prototyping builds a mock-up to provoke reaction. Only one of the four studies artefacts the organization already holds.

Correct answer: Settle the conflict with the stakeholders and rewrite the requirements

Settle the conflict with the stakeholders and rewrite the requirements: a business analyst facilitates a resolution with the people who own the competing needs and then updates the requirements to record what was agreed. Escalating to the sponsor first skips the analyst's own facilitation duty and is reserved for conflicts the stakeholders cannot resolve themselves. Keeping the senior stakeholder's requirement lets rank decide instead of business value and discards a need without examining it. Building both contradictory requirements and comparing them in testing guarantees rework and defers a decision that belongs before development.

Correct answer: A product epic

A product epic is the large body of work that gathers related user stories into one bigger capability and is deliberately too big to finish inside a single iteration; teams split it into stories as it nears the top of the backlog. A design spike is a time-boxed investigation run to reduce uncertainty, not a container for stories. A work package is the lowest element of a work breakdown structure in predictive planning. A sprint story is one of the small items the grouping is made from, so it cannot be the name of the grouping itself.

Correct answer: The hundred-dollar distribution method

The hundred-dollar distribution method hands every stakeholder the same imaginary budget of points or dollars and asks them to spread it across the competing items, so relative priority falls out of how the pot was divided. The parametric-cost forecasting method derives cost from historical unit rates and never ranks anything. The fixed-percentage comparison method contrasts figures against a set proportion, which is a variance test rather than a ranking. The resource-loading simulation method models staffing demand over time. Only one of the four asks stakeholders to spend a limited allocation.

Correct answer: Verification checks requirements for formal correctness; validation checks them for business value

Verification checks requirements for formal correctness; validation checks them for business value - that is, verification asks whether the requirements were written right (clear, complete, consistent, testable) while validation asks whether the right requirements were written at all. The realized-benefit statement reverses the two definitions and so attaches each test to the wrong question. Product coverage describes tracing built features back to requirements, and funding approval is a spending decision, neither of which is a requirements quality check. Stakeholder approvals and stage dates are governance and schedule events, not tests of requirement quality or worth.

Correct answer: Baselining the requirements and steering revisions through a formal control process

Baselining the requirements and steering revisions through a formal control process keeps an approved set steady while still letting it change. The baseline fixes the agreed version, and every later revision must be approved before it replaces that version. Freezing the approved requirements and refusing updates for the rest of the project keeps them stable but blocks the controlled updates the analyst still needs. Tagging the requirements and linking them to work products in a traceability matrix shows where each requirement goes, but it does not approve or block any change. Refining the requirements and adding details over time with progressive elaboration keeps changing the set and leaves no fixed, approved version to protect.

Correct answer: Business rules inside the requirements list

Business rules inside the requirements list is where a constraint such as an order threshold that triggers extra sign-off belongs: it is a standing policy the solution must enforce, so it is captured and traced with the other requirements. An approval workflow is one process the rule might govern, not the place the rule is defined, and burying the policy there hides it from every other process it constrains. A configuration log records versions and change history of controlled items. A quality checklist records how a deliverable will be inspected. None of the last three is a home for the organization's operating policy.

Correct answer: Transition requirements

Transition requirements describe the temporary capabilities needed only to move from the current state to the future state - data migration, parallel running, and user training for cutover - and they stop being needed once the switchover is done. Behavioral requirements describe what the delivered solution does permanently, every day it runs. Procedural requirements describe how ongoing work is to be carried out after go-live. Regulatory requirements impose obligations drawn from law or standards and outlive the project entirely. Only one of the four names a need that exists solely for the changeover.

Correct answer: A survey or questionnaire

A survey or questionnaire reaches a large, scattered audience cheaply and lets each person answer privately, so the loudest participants cannot steer the rest. A workshop or walkthrough puts everyone in one room at one time, which is exactly the setting where a dominant voice carries the group and where distance is hardest to bridge. A prototype or storyboard gathers reaction from the handful of people put in front of it. A briefing or observation studies one site or one audience at a time and still exposes answers to the room.

Correct answer: Weighing the fit as part of solution evaluation

Weighing the fit as part of solution evaluation is the activity that tests a proposed solution against the business objectives that justified it, and it is what must happen before anyone recommends deployment. Measuring the output as part of quality control checks deliverables against their specifications rather than against the business objectives. Documenting the gap as part of needs assessment happens at the start, when the problem is defined and before any solution exists. Staging the rollout as part of release planning organizes deployment itself, which presumes the fit question has already been answered.

Correct answer: It reveals the design, build, and test items a change would affect

It reveals the design, build, and test items a change would affect - that is the point of keeping traceability current, because the forward and backward links turn a proposed change into a known list of work to reassess, which is the impact analysis. Traceability does not remove the check, review, and audit steps; a traced change still needs the same approval it always did. It does not shorten idle, queue, or cycle times, since it adds no capacity. And it does not fix unit, labor, or total costs, which come from estimating, not from links.

Correct answer: The business work that elicits, analyzes, and governs requirements so the solution delivers value

The business work that elicits, analyzes, and governs requirements so the solution delivers value is business analysis: it draws out what stakeholders need, examines and records it, and keeps it managed through change so the thing the project builds is the thing worth building. Inspecting, sampling, and grading deliverables is quality assurance, which judges output after it exists. Tallying, forecasting, and reporting deviations is cost control. Ordering, sequencing, and smoothing dependencies is schedule management. Each of those three is a real project function, but none of them decides what the solution should do.

Correct answer: Eliciting and analyzing the needs and turning them into clear, confirmed requirements

Eliciting and analyzing the needs and turning them into clear, confirmed requirements is the business analyst's own work: the analyst is the bridge between what stakeholders want and what the team builds. Leading the project team and balancing the competing demands of scope, time and costs is the core of the project manager's role. Authorizing the project charter and appointing a project manager is the sponsor's decision. Coaching the team in agile practices and clearing impediments is the work of a scrum master or agile coach rather than the analyst.

Correct answer: Drawing requirements from stakeholders and other sources by interview, workshop, and observation

Drawing requirements from stakeholders and other sources by interview, workshop, and observation is elicitation: the discovery step in which needs are drawn out of people, documents, and systems. Ranking requirements against business goals by value, urgency, and complexity is prioritization, which can act only on requirements already elicited. Confirming requirements with customers by review, walkthrough, and sign-offs is validation, which checks requirements after they have been captured. Tracing requirements to designs by trace matrix, test script, and release is traceability, which follows requirements once they are known.

Correct answer: Facilitated requirements workshop

A facilitated requirements workshop brings the stakeholder group together with a neutral facilitator, so competing views surface and are reconciled while everyone is present, which suits both speed and conflict resolution. A one-on-one requirements interview gathers views from a single person, so conflicts between stakeholders cannot be settled in real time. An online requirements questionnaire collects answers asynchronously and gives nobody a chance to respond to anyone else. Workflow requirements observation watches people doing their jobs, which reveals tacit needs but does not resolve disagreements.

Correct answer: A business requirement names the goal that the organization pursues, while a functional requirement names the behavior that the solution performs

A business requirement names the goal that the organization pursues, while a functional requirement names the behavior that the solution performs: the first answers why the project exists, the second answers what the product has to do. Hardware and budget are an environment and a constraint, so neither is the defining content of either requirement type. Naming a developer or a sponsor describes who is involved, which is a stakeholder question and not a requirement class at all. Naming an approach or a stage describes delivery method and timing, which are planning choices independent of what the requirements say.

Correct answer: Business requirements lead to stakeholder requirements, which lead to solution requirements

Business requirements lead to stakeholder requirements, which lead to solution requirements: the organization's high-level need comes first, the needs of particular stakeholder groups are derived from it, and the solution statements the team builds against - functional and non-functional alike - are derived from those. Placing operational requirements above business requirements inverts the pyramid, because how the organization will run day to day is an answer to the business need rather than its parent. Beginning with security requirements makes one quality attribute the origin of everything else the business wants. Beginning with operational requirements and deriving training from them never reaches a business objective at all, so nothing in the chain can be traced to a reason for doing the work.

Correct answer: Non-functional requirements

Non-functional requirements are the right class for an encryption standard and a response-time limit, because both describe how well the system has to behave - security and performance - rather than a function it carries out. Contract-based requirements would be obligations owed under a supplier agreement, which is a commercial origin rather than a category of system quality. Department-set requirements would describe who asked for something, which is a source and not a class. Compliance-led requirements name where a rule came from; encryption often does originate in a compliance rule, but the statement as documented is still a quality constraint on the system, and a two-second response limit has no compliance origin at all.

Correct answer: Transition requirements

Transition requirements cover the temporary capabilities needed to move from the current state to the future state, such as data conversion and user training, and they are retired once cutover succeeds. Functional requirements describe the behaviors the new order-entry system itself must perform on an ongoing basis, not temporary switch-over work. Stakeholder requirements describe the needs of a particular stakeholder or group rather than the capabilities that exist only for the changeover. Business requirements describe the higher-level organizational needs and reasons for the change, not the mechanics of cutover.

Correct answer: MoSCoW prioritization

MoSCoW prioritization sorts every candidate into Must have, Should have, Could have, and Won't have this time, which is precisely the decision a fixed timebox forces: the team commits to the first band, negotiates the second, and defers the rest. Parametric estimation derives size or cost from historical unit rates, so it tells you what something costs but never which item wins. Rolling-wave planning decides how far ahead to plan in detail. Decomposition mapping breaks large items into smaller ones without saying which of them matters most.

Correct answer: Ranking items by the business value delivered against the effort consumed

Ranking items by the business value delivered against the effort consumed is the value-versus-effort principle: the items that return the most for the least work rise to the top, so the team maximizes what is delivered early. Ranking by an alphabetical label is arbitrary and correlates with nothing the business cares about. Ranking by the personal value someone claims rewards whoever argues hardest rather than whatever pays back most. Ranking by the arrival moment an item was recorded is first-come-first-served, which ignores worth entirely even when an effort figure is quoted alongside it.

Correct answer: A requirements traceability matrix

A requirements traceability matrix is the tool that links each requirement backward to the business need that justified it and forward to the design, build, and test artefacts that satisfy it, so coverage gaps become visible rather than being discovered late. A requirements documentation index only records where each requirement document is stored, so it locates files without linking them to needs or tests. A requirements breakdown structure groups requirements into a category hierarchy but shows nothing about build or test status. A requirements validation register logs whether stakeholders confirmed each requirement is correct, which does not follow it through to what was built and tested. None of the three maintains the two-way links that give the assurance being asked for.

Correct answer: Requirements traceability matrix

Requirements traceability matrix is the document that carries the bidirectional link: from each requirement back to its origin, such as a business objective or a regulation, and forward to the deliverables, designs, and test cases that satisfy it. A requirements management database may store the requirements themselves without ever recording what each one came from or what fulfills it. A requirements elicitation summary reports what was gathered in a session. A requirements categorization tree groups items by type or theme, which organizes them but creates no path to origin or deliverable.

Correct answer: A user story

A user story is exactly this shape - as a role, I want a capability, so that a benefit follows - and it deliberately records who wants something, what they want, and why, leaving the how to the team. A spec sheet lists detailed technical properties of a solution rather than a user's goal and the benefit behind it. A work order authorizes a specific piece of work to be carried out, so it instructs rather than expresses a need. A risk entry records an uncertain event with its probability and impact, not a capability someone wants.

Correct answer: Acceptance criteria

Acceptance criteria are the specific conditions a story must satisfy before it can be called complete, and writing them is what makes a story testable: each criterion becomes a pass or fail check agreed in advance. A readiness checklist, often called the definition of ready, says when a story is prepared to enter an iteration, not when it is finished. Test coverage goals measure how much of the code automated tests exercise, a technical quality target rather than the conditions for one story. Decomposition rules guide splitting large stories into small, independent ones, which shapes a story but does not define when it is done.

Correct answer: The named product owner

The named product owner is the single person accountable for maximizing the value of the product and for the content and ordering of the backlog; the whole organization is expected to respect that ordering decision. The senior scrum master serves the team and the process, removing impediments and coaching, but does not decide what gets built next. The lead product tester judges whether what was built behaves correctly, which is a quality verdict rather than a value decision. The agile delivery lead worries about flow and delivery cadence, not about which item is worth the most.

Correct answer: Reordering the product backlog so the team builds the highest-value items soon

Reordering the product backlog so the team builds the highest-value items soon is the product owner's defining act: the role owns backlog content and order, and re-ordering is how value gets steered from one iteration to the next. Approving timesheets so contract-set hours are logged is a line-management duty that sits outside the delivery roles entirely. Estimating subtasks and pledging a locked-down scope belongs to the people doing the work, who alone can size it. Chairing the standup and clearing flow-stopping issues is the scrum master's service to the team. The product owner decides what and why, never how.

Correct answer: The product roadmap

The product roadmap is the high-level, time-oriented picture of where the product is going: the major features or themes and the sequence in which releases are expected to land. The product backlog holds the ordered detail of work items, which is far finer grained than a stakeholder asking about direction wants to see. The product tracker reports how much of the current work is finished, which is progress rather than intent. The product charter states why the product exists and who it serves, but it carries no release sequence over time.

Correct answer: The roadmap sets the strategic release sequence, while the backlog holds the prioritized work items

The roadmap sets the strategic release sequence, while the backlog holds the prioritized work items: one answers where the product is heading and roughly when, the other answers what gets built next. Saying the roadmap lists individual stories and the backlog shows quarterly themes swaps the two levels of granularity exactly the wrong way round. Tying the roadmap to predictive work and the backlog to agile work is false, since both artefacts appear in either approach. Assigning the roadmap to build squads and the backlog to sponsors misplaces both audiences; the product owner owns both artefacts.

Correct answer: Solution evaluation

Solution evaluation is the business analysis activity that looks at a delivered solution and asks whether it actually meets the business need and returns the value that was expected, then recommends whether to improve, replace, or retire it. Solution deployment is the act of putting it into live use, which happens before there is anything to measure. Solution estimation sizes the effort or cost of building it, and is done up front. Solution governance sets the decision rights and controls around it. Only evaluation is aimed at realized value after delivery.

Correct answer: To confirm the value the solution gives the business and the changes still needed

To confirm the value the solution gives the business and the changes still needed is the purpose of solution evaluation: it establishes how much of the expected benefit has actually arrived and what adjustment, enhancement, or retirement decision follows from the shortfall. Verifying the build against the approved design and its test cases is quality verification, which proves the solution was built as specified but not that it delivers value. Checking schedule and cost targets against the baseline measures project performance, which says nothing about whether the business gained the intended benefit. Formally closing the project and handing the solution to operations is transition work that ends delivery rather than judging the value it produced.

Correct answer: Requirements management

Requirements management is the umbrella term for the continuing work of planning, tracing, prioritizing, approving, communicating, and maintaining requirements - including handling changes to them - for as long as the project runs. Requirements refinement adds detail to individual requirements as understanding grows, but it does not cover planning, tracing or approval. Requirements validation confirms that a requirement reflects the real stakeholder need, which is one check inside the larger effort. Requirements allocation assigns individual requirements to components or releases and is another single task. Each of the three is a single activity; only one name covers the whole ongoing effort.

Correct answer: A systematic set of practices, techniques, and knowledge areas that guide business analysis

A systematic set of practices, techniques, and knowledge areas that guide business analysis is what a framework is: it supplies the vocabulary, activities, and typical order of work, so different analysts produce comparable results. A standard set of templates, checklists, and document formats is a documentation standard, which records outputs without defining how analysis is done. A licensed set of software tools, databases, and dashboards is tooling, which automates tasks but prescribes no method. A governing set of policies, stage gates, and sign-off rules is a governance structure, which controls approvals rather than guiding the analysis itself.