Quick 10

A. Both projects and operations consume resources; that is what makes them compete for the same people, not what tells them apart.

B. Who manages the work says nothing about its nature. In a functional organisation the same managers often run both operations and projects.

C. A project is temporary and creates a unique product, service or result. The eight-month team and the first-ever online store are exactly those two marks.

D. Repetitive, procedure-driven work that sustains a stable output is the definition of operations, the opposite of what the stem describes.

A. A program is a group of related projects and activities managed in a coordinated way to obtain benefits not available from managing them individually, which is exactly the reason given in the stem.

B. A portfolio groups projects, programs and operations to meet strategic objectives; its components need not be related to one another, and the grouping is about investment choice rather than coordinated benefits.

C. A subproject is a smaller, more manageable piece of a single project, not a grouping of several projects.

D. A phase is a collection of logically related activities within one project's life cycle, not a way of grouping separate projects.

A. An issue is a condition that has already happened and needs resolution, such as the damaged paving stones. The vote has neither passed nor failed, so nothing has occurred yet.

B. A refusal is indeed a risk that flows from this planning basis, and it belongs in the risk register. But the stem asks how the basis itself is recorded, and a factor the plan treats as true without proof is an assumption from which the risk is then derived.

C. A constraint is a fixed limit imposed on the project, like finishing before the frost. An amount that has not been confirmed cannot yet act as a limit.

D. An assumption is a factor considered true, real or certain for planning purposes without proof. The plan is built on the vote passing in time, which is exactly that.

A. The sponsor's authority does not extend to asking for a misleading report. The Code of Ethics places honesty above a superior's instruction, and a private note does not make an incomplete report accurate.

B. Honesty and responsibility require accurate reporting of material facts, and respect requires the sponsor to hear it directly rather than be surprised. This keeps both the information and the relationship intact and stays inside the project's governance.

C. This avoids one falsehood by creating a back channel. It still produces a status report the project manager knows to be incomplete and steps outside the project's agreed reporting path.

D. Stopping work and going to the client's lawyers are escalations the project manager has not yet earned by following the project's own process. The finding must be reported and dealt with first; legal escalation may follow if governance fails.

A. Fixed, externally approved acceptance criteria are a stability signal; they favour defining the scope up front and building to it, a predictive trait.

B. Requirements that emerge from use rather than from analysis are the classic reason to choose an adaptive approach, which exists to discover scope through short cycles and feedback.

C. A fully specified scope under a fixed price is the strongest argument for a predictive approach, where the plan is baselined and changes are controlled formally.

D. Well-understood technology lowers uncertainty, which reduces the need for the experimentation that an adaptive approach provides.

E. Frequent incremental delivery with adjustment from feedback is the delivery cadence adaptive approaches are built around.

A. This describes the funding boundary of the project, not its purpose. Framing a project as an expense misses the outcome it exists to bring about.

B. Keeping the system running after go-live is operations, which the project hands over to. The project itself is temporary.

C. Governance structures set decision rights and oversight; they are not what moves the organisation from one way of working to another.

D. Projects are how organisations bring about change, taking them from the present state (paper files) to a chosen future state (a shared digital system) and enabling the outcomes that come with it.

A. The register records, for each identified risk, the agreed response and the risk owner. Once the event occurs, those two entries tell the project manager what happens next and who is accountable for it.

B. Probability and impact are in the register, but they served to rank the risk before it happened. Now that it has occurred, the probability is no longer a question and the scores do not tell anyone what to do.

C. Secondary risks are recorded once a response is chosen and are worth re-checking, but only after the planned response itself has been identified and set in motion.

D. Categorisation helps organise and analyse risks during planning. It does not guide the response to a risk that has just materialised.

A. The communications plan says what each audience receives, how often and in which format. It relies on the analysis in the register rather than containing the authority, interest and attitude of each person.

B. A responsibility assignment matrix maps team members to work packages or deliverables. It shows who does the work, not who has influence over a decision or how outsiders feel about the project.

C. The register holds, for each identified person or group, their role, interest, influence and level of engagement. That is exactly the combination of authority, impact and attitude the invitation list requires.

D. The charter names the sponsor and lists key stakeholders at a high level at initiation. It is not maintained as the project progresses and does not track how each person has reacted.

A. Waiting for an approval may take calendar time, but that waiting is modelled as lag or as a separate activity, not as the entry itself. The sign-off is an event, not a stretch of work.

B. A milestone is a significant point or event in the project; it is recorded with zero duration because nothing is being worked on, only reached.

C. A summary activity or hammock rolls up a group of activities into one bar. A milestone stands at a point and carries no roll-up of effort.

D. Resources are assigned to activities that consume effort. An approval point consumes none, so it cannot carry the largest share.

A. Moving work into a next iteration belongs to an ongoing adaptive delivery cycle. Once the final deliverable is accepted, there is no next iteration inside this project.

B. Baselines are changed through change control while the work is under way. At closure, actuals are recorded against the final baseline for lessons learned; the baseline itself is not rewritten.

C. Defining new scope is initiating work, for a new phase or a new project. It is not part of bringing the current project to an orderly end.

D. Transitioning the deliverable to the people who will run it, together with what they need to run it, is a core part of closing, alongside final reporting, releasing the team and archiving records.

A. The scope management plan is a subsidiary plan describing how scope will be defined, validated and controlled. It is a standard component of the project management plan.

B. A roadmap belongs to product management. It outlines the direction of the product across its life, which extends well beyond this project's end, and it is owned by the product function.

C. Baselines for scope, schedule and cost are components of the project management plan; the schedule baseline is the approved version against which time performance is measured.

D. A bill of materials describes what the product is made of. It is a product specification, part of the deliverable, not a plan for how the project will be managed.

E. The change management plan describes how change requests will be submitted, evaluated and approved. It is a subsidiary plan within the project management plan.

A. The sponsor provides resources, removes obstacles, makes decisions above the project manager's authority and champions the project; the project manager directs the team. A direct, respectful conversation that restores that division is the first and least disruptive step.

B. The sponsor's authority is over funding, priorities and decisions above the project manager's level, not over daily assignments. Passing the team to the sponsor abandons the project manager's own role.

C. Governance is the right place if the conversation fails. Going there first escalates over the sponsor's head before the project manager has tried to resolve it directly, which damages the relationship the project depends on.

D. This is the right outcome delivered as a demand, without hearing why the sponsor is stepping in. It may be that the sponsor has lost confidence, which a conversation would surface and a rule would not.

A. Management is about processes, plans and control, the Monday work of schedules, budgets and assignments. Tuesday is not about the plan at all.

B. Leadership works through vision, motivation and involving people in how the goal is reached. Explaining why the project matters and inviting the team to shape the approach is that, not a control activity.

C. Controlling is measuring performance against the plan and acting on variances. Nothing on Tuesday measures anything.

D. Facilitation is guiding a group through a process to its own outcome. Tuesday's activities may happen in a meeting, but their essence is giving purpose and ownership, which is leadership.

A. Public correction protects the stakeholder at the developer's expense and adds a second sharp exchange to the first. Emotional intelligence includes empathy for the person under pressure, not only the person offended.

B. Avoidance leaves the feeling in the room unaddressed and the stakeholder's concern unanswered. Recognising emotion means naming it, not skipping past it.

C. This is self-awareness (noticing the irritation and pausing), self-regulation (not acting on it), empathy (naming the difficulty) and relationship management (redirecting to the shared goal), the four parts of emotional intelligence in one move.

D. Routing feedback around the team removes the live conversation the review exists for. It manages the project manager's discomfort rather than the people in the room.

A. A project manager may contribute hands-on work on a small team, but certified welding is not a task to absorb, and doing so would leave the underlying resource conflict unresolved.

B. Cutting scope to fit a resource problem sacrifices the project's objective to avoid a conversation. Change control is for changes the project needs, not a substitute for negotiating.

C. Listening is part of the response, but accepting a four-week slip on the critical path without exploring alternatives is passivity, not the active listening PMI describes.

D. In a matrix, the project manager has no authority over the functional manager's people and must negotiate for them. Seeking a solution that meets both needs, such as a split allocation, a short deferral or a substitute, is the role the situation calls for.

A. The response was planned, funded and assigned. Executing it means checking that the owner is carrying it out, and only then turning to the consequences for the plan. This follows the agreed strategy and assesses before acting further.

B. Accountability for the outcome does not mean doing the risk owner's job. Overriding the assigned owner discards the planning that put the right person in place and leaves the project manager doing two roles.

C. A go or no-go question may reach the sponsor later, but only once the impact is known. Escalating before assessing gives the sponsor a question without the information needed to answer it.

D. Spending the reserve first reverses the planned response. The transfer to the insurer was chosen so that the reserve would not have to carry this risk; drawing it down anyway leaves other identified risks unfunded.

A. The charter authorises the project and the management plan says how it will be run. Neither is the justification for the investment, and neither tracks benefits after the project has closed.

B. A feasibility study tests whether an option can be done, and the scope statement describes what the project will deliver. The justification of value and the measurement of benefits are different documents.

C. The business case sets out the justification for the investment; the benefits management plan defines the benefits, how and when they will be realised and measured, and who owns them, including after closure.

D. The business case is the right first document, but the charter authorises the project rather than describing how benefits will be measured once it is over.

A. Serving one stakeholder outside the plan creates an unplanned channel, costs time the plan did not budget and leaves the other directors with less than this one receives.

B. Holding the line on the plan without asking why it is failing treats the plan as an end in itself. Something is not working for this stakeholder, and refusing to learn what leaves it unaddressed.

C. The director's problem is frequency, not detail; a monthly dashboard arrives less often than the summary already does. It also shares a governance artifact with an audience it was not designed for.

D. The plan is a strategy to be followed and, when it stops serving a stakeholder, to be updated deliberately. Understanding the need first and then changing the plan keeps all directors on an agreed footing.

A. A daily standup is the team's own synchronisation point: a shared view of where the work stands and an early warning of anything in the way, so that help can be arranged the same day.

B. The standup is for the people doing the work, not for reporting upward. Stakeholder reporting happens through status reports, dashboards and reviews.

C. Inspecting what has been built and gathering feedback on it is the purpose of a review at the end of an iteration, not a daily event.

D. Improving the process is the purpose of a retrospective. A standup may reveal a problem, but the discussion of how to fix the way of working is deliberately kept out of it.

A. Brainstorming generates ideas in open discussion, which is exactly where the two senior voices have dominated before, and it does not produce a ranking on its own.

B. Nominal group technique has each participant write ideas independently, shares them round-robin and ranks them by vote. The silent step neutralises dominant voices and the vote delivers the ranking the project manager needs.

C. A focus group explores attitudes and expectations through guided conversation. It deepens the voices the project manager is trying to balance and gives no ranked outcome.

D. A standup is a coordination meeting for a team's own work. Giving each person a turn does not produce a prioritised list and misuses the event.

A. An agenda with a stated purpose and named decisions gives the meeting a target, lets people prepare and makes it possible to notice when the discussion has drifted. It is the first fix for a meeting that overruns and decides nothing.

B. More attendees lengthen discussion and dilute ownership. Effective meetings invite the people needed for the decisions on the agenda, not everyone who might have a view.

C. A longer slot accommodates the drift rather than removing it. A meeting that lacks purpose and decisions will fill whatever time it is given.

D. Writing down actions, owners and dates converts discussion into commitments and is exactly what is missing when people leave unsure what they owe. It also gives the next meeting something concrete to follow up.

E. A status sheet shares information but cannot make the coordination decisions the meeting exists for. It removes the symptom by removing the decision-making, which the project still needs.

A. A survey collects structured answers from many people at once. It scales well but captures neither people's own words nor how they respond to each other.

B. Brainstorming generates ideas from the project team or a working group. It is not a way of listening to customers describe their expectations.

C. A focus group brings a handful of prequalified participants together with a moderator to explore their expectations and attitudes through interactive conversation, which is exactly the small-group, in their own words, reacting-to-each-other purpose in the stem.

D. An interview is one-to-one or one-to-few and yields depth from each person, but it cannot capture the interaction between participants that the team wants to observe.

A. An adaptive approach suits requirements that are uncertain and expected to change through feedback. Here the requirements are fixed by a regulator before work starts, so there is nothing to discover iteratively.

B. Stable, externally fixed requirements, a fixed-price contract and a single deliverable that only has value when complete are the classic conditions for planning the whole scope, schedule and cost up front and then executing against baselines.

C. An incremental approach delivers usable pieces of the product early. A chlorination unit that cannot be used until it is installed and certified offers no increment with stand-alone value.

D. A hybrid approach mixes predictive and adaptive elements when part of the scope is stable and part is uncertain. Nothing in this project is uncertain enough to justify the adaptive part.

A. Measuring performance against a baseline and recommending corrective or preventive action is the core of Monitoring and Controlling; it is what Control Schedule does.

B. Obtaining people, equipment and services for the project is an Executing activity (Acquire Resources). It carries out the plan rather than checking performance against it.

C. The charter is developed in the Initiating Process Group; it authorises the project and names the project manager before any control can take place.

D. Perform Integrated Change Control sits in Monitoring and Controlling: every change request is reviewed, decided and recorded there so the baselines stay under control.

E. Archiving records and releasing resources are Closing activities, performed once the deliverables have been accepted and the project or phase ends.

A. A milestone is a significant point or event in the schedule with no duration; the end of a phase is often marked by one, but a milestone is not itself a review with a continue-or-stop decision.

B. A kick-off meeting launches a project or phase after it has been authorised, to align the team on objectives and roles. The decision to proceed has already been made by then.

C. A phase gate is the review held at the end of a phase where performance and progress are compared with the business case and plans, and a decision is made to continue, continue with changes, or end the project. That is exactly what the steering committee is doing.

D. The change control board reviews individual change requests against the baselines. It does not decide whether the next phase of the project goes ahead.

A. Nine days is the length of the paths A-B-D and A-B-E. They are the shorter paths through the network, so activities B and E carry one day of float; the critical path is the longest one.

B. The path A-C-D is 3 + 5 + 2 = 10 days. The other paths, A-B-D and A-B-E, are 3 + 4 + 2 = 9 days each. The longest path through the network is the critical path, so the project cannot finish in fewer than 10 days.

C. Twelve days is A + B + C, which adds the parallel activities B and C as if one had to wait for the other. They start together after A, so only the longer of the two counts.

D. Sixteen days is the sum of all five activities. Adding every duration ignores that B runs in parallel with C and that D runs in parallel with E.

A. SV = EV - PV = 320,000 - 350,000 = -30,000. Less value has been earned than was planned by this date, and a negative schedule variance means the work is behind the schedule baseline.

B. The arithmetic is right but the reading is wrong. Schedule variance compares earned value with planned value and says nothing about spending; over or under budget is read from the cost variance, which needs the actual cost.

C. This subtracts in the wrong order (PV - EV). With less earned than planned, the variance must be negative and the project cannot be ahead.

D. Both the sign and the interpretation are wrong: the order of subtraction is reversed and schedule variance does not measure cost.

A. Rolling wave planning details near-term work and leaves later work at a higher level. It is allowed in a WBS, but even a high-level element must still represent all of the work below it.

B. Progressive elaboration is the refining of the plan as more becomes known. It describes how detail grows over time, not whether the children of an element cover everything the parent contains.

C. The 100 percent rule says the WBS includes all of the project's work and that the children of any element together represent 100 percent of that element, no more and no less. Work packages that add up to less than their parent break it.

D. The 8/80 rule is a sizing heuristic that keeps a work package between roughly 8 and 80 hours of effort. It is about the size of a package, not about whether the packages together cover the parent.

A. Following the quality plan is right, but a baseline is only changed through the change control process. The project manager cannot re-baseline the schedule on their own authority, even to record a delay that is certain.

B. This protects the date by abandoning the quality management plan. The plan states that inspection defects are repaired before acceptance, and acceptance of known-defective work is not a decision the project manager can make alone.

C. Following the quality plan is right, and logging the slip is harmless, but the issue log does not authorise a change to a baseline. Only an approved change request moves the schedule baseline.

D. Both plans are followed as written: the quality plan decides what happens to the defective deliverable, and the change management plan decides how the resulting baseline change is handled. The board, not the project manager, approves the new baseline.

A. A risk is an uncertain event that may happen. The supply stoppage has already happened, so it is no longer a risk; if it had been listed as one, its entry would now be closed and the event tracked elsewhere.

B. The change log tracks change requests and their status. No change to scope, schedule or cost has been requested yet; that may follow, but first the problem itself must be tracked.

C. The lessons learned register captures what was learned and what to do differently. Once the stoppage is resolved a lesson may be recorded, but it is not the place to manage an open problem.

D. An issue is a current condition or event that has already happened and needs to be resolved. The issue log records it with an owner, a priority and a target date, which is exactly what the project manager wants.

A. CV = EV - AC = 400,000 - 500,000 = -100,000, and CPI = EV / AC = 400,000 / 500,000 = 0.80. Both say the same thing: the project has spent more than the value of the work it has completed.

B. This reverses both formulas (AC - EV and AC / EV). A project that has spent 500,000 to earn 400,000 cannot have a favourable variance or an index above one.

C. The variance is right but the index is AC divided by EV. CV and CPI always point the same way: a negative CV goes with a CPI below one.

D. The index is right but the variance is AC minus EV. A CPI below one cannot go with a positive cost variance.

A. A product backlog is the ordered list of work in an adaptive project; it is reprioritised continually and is not measured against a baseline.

B. The change log records every change request and its status. Because baselines are only altered through approved changes, the log is the record of how and why the baselines have moved.

C. The business case justifies the project and is revisited at phase gates to confirm it still holds. It is a business document, not a control artifact; performance is measured against the baselines, not against the business case.

D. The charter authorises the project and gives the project manager authority. It is an initiating artifact and is not used to measure performance or to control the work against the baselines.

E. Work performance reports present measured performance against the baselines, such as schedule and cost variances, so that decisions and corrective actions can be taken. They are the core control document of a predictive project.

A. Fixed, well-understood requirements and a fixed-price contract suit a predictive life cycle, where the work is planned once and executed to the specification. Iterating would add cost without producing any learning.

B. The deliverable and its format are known in advance and delivered once. This is definable work with low uncertainty, the classic case for a predictive approach.

C. Requirements are uncertain, change is expected and feedback arrives after each release. That is the high-uncertainty, high-change situation in which an adaptive approach delivers value in small increments and adjusts the backlog as the clinics learn.

D. A short, repeatable task done to a proven procedure has no requirement uncertainty to resolve. Iterations and feedback loops would bring nothing, so a predictive plan fits.

A. Adaptive approaches depend on rapid decisions about value and priority. A product owner who is present every day answers questions, accepts work and reorders the backlog without waiting for a committee, and for a team split between offices that presence matters even more.

B. The scrum master is a servant leader who removes impediments and coaches the team; work is pulled by self-organising team members, not assigned. A scrum master who assigns work undermines the self-organisation the approach relies on.

C. A product owner exists, but quarterly feedback defeats the point of short iterations: the team would build for months without knowing whether the increment is right. Feedback has to arrive at least once per iteration.

D. These are organisational process assets that support a predictive life cycle. Phase gates and detailed schedule templates add ceremony an adaptive team does not use, so they do not facilitate the approach.

A. The product goal is the longer-term objective the whole product backlog works toward, spanning many sprints. The objective proposed for one sprint is a step toward it, not the goal itself.

B. The sprint backlog is the set of items the team selects plus its plan for delivering them. It is built to serve the objective; it is not the objective.

C. The definition of done states the quality conditions every item must meet before it counts as complete. It applies to all sprints and does not describe what one particular sprint sets out to achieve.

D. The sprint goal is the one objective the sprint commits to, agreed in sprint planning. It gives the team a shared purpose and guides which items are selected and how scope is negotiated during the sprint.

A. Work packages describe deliverables, so they map naturally to features and user stories. Placed in a product backlog and ordered by value they become the input from which the team pulls work into each iteration and the product owner reprioritises as learning arrives.

B. Uses agile vocabulary but keeps the predictive idea of committing the entire scope up front. A sprint backlog holds only what the team forecasts for one timebox; the rest waits in the product backlog and can still change.

C. A Gantt chart of fixed activities is predictive tracking. The iteration review inspects a working increment with stakeholders; reporting percent complete against a schedule there mixes the two approaches without gaining any adaptability.

D. Phase gates are a predictive control that delivers nothing usable until the end of each phase. Adaptive planning works from a value-ordered backlog and delivers increments, not sequential gated phases.

A. Critical-path schedule variance assumes a fixed network of activities agreed in advance. With the backlog reordered every iteration there is no stable activity network to measure against, so the variance would describe a plan that no longer exists.

B. Remaining size is half the picture. Without the rate at which the team finishes points it cannot say when the backlog will be exhausted, so it does not answer whether the date holds.

C. Effort spent is an input measure; it says nothing about how much accepted, working product exists or how much remains. Adaptive tracking measures completed value, not hours consumed.

D. Velocity is the amount of work the team actually completes per iteration. Plotted with the remaining scope on a burnup chart it projects when the backlog will be done and shows scope changes as they happen, which is what the sponsor's question needs.

A. The ordered list of everything the product may need is the central planning artifact of an adaptive project. Every iteration is planned from it and it changes as the product owner learns.

B. A schedule network diagram fixes activity sequences and float for the whole project in advance. It belongs to predictive scheduling; adaptive teams plan one iteration at a time from the backlog.

C. A traceability matrix links a fixed set of requirements to design, build and test through a predictive project. In an adaptive project requirements live as backlog items with acceptance criteria and are expected to change, so the matrix is not a standard artifact.

D. A burndown chart shows the work remaining in an iteration or release against time. It is one of the standard visual artifacts adaptive teams use to track progress and keep it visible.

E. Phase gates close one phase before the next begins, which is a predictive life-cycle control. Adaptive projects replace them with iteration reviews of a working increment.

A. Acceptance criteria are the conditions specific to one story that the product owner uses to accept it, and the stem says they were satisfied. They are necessary but not sufficient; the story fails a team-wide condition instead.

B. The sprint review is the event where the increment is inspected with stakeholders. It is a meeting, not the rule that decides whether an item counts as complete before it reaches that meeting.

C. The definition of done is the shared list of quality conditions that every item must meet regardless of its individual acceptance criteria. An untested story does not meet it, so it cannot be counted as complete or included in the increment.

D. The sprint goal is the objective the sprint commits to. It shapes which items are selected, but it does not define the quality state an item must reach to be counted as complete.

A. Sprint planning opens the sprint: the team sets the sprint goal and selects backlog items. It looks forward at what to build, not back at what was built.

B. The sprint review closes the sprint's work by inspecting the increment with stakeholders and adapting the product backlog; it is the feedback event that keeps the product on track.

C. The retrospective inspects how the team worked, its process, tools and relationships, and plans improvements. It is held by the Scrum team without stakeholders and does not examine the product increment.

D. The daily scrum is a short event for the developers to inspect progress toward the sprint goal and plan the next day. It is internal to the team and happens every day, not at the end of the sprint.

A. WIP limits are the defining practice of the Kanban method, used to expose bottlenecks and improve flow. They are not part of XP's practice set, although a team may choose to add them.

B. Pair programming is a core XP practice: continuous review as the code is written, shared knowledge across the team and fewer defects.

C. Program increment planning is a component of the Scaled Agile Framework (SAFe), which coordinates many teams on a shared cadence. XP is a single-team method and has no such event.

D. The sprint review is a Scrum event. XP works in short iterations too, but the sprint and its formal review are Scrum's vocabulary, not XP's.

E. Test-driven development is a core XP engineering practice: the test defines the behaviour first, then the code is written to satisfy it and refactored.

A. A shorter timebox is a legitimate Scrum adjustment, but the fixes arrive daily, so even a one-week commitment would still be broken. It treats the symptom by planning more often rather than matching the method to interrupt-driven work.

B. The scrum master is a servant leader who coaches the team and removes impediments; assigning work is not the role. It also leaves the mismatch between fixed sprint commitments and unpredictable arrivals untouched.

C. Kanban's flow model suits work that arrives unpredictably: there is no fixed-scope timebox to break, WIP limits keep the team from overloading, and each item is pulled when someone is free, so fixes and planned items share one visible flow.

D. Protecting the sprint goal is Scrum by the book, and the product owner does decide priority, but production fixes on a live billing system cannot wait for the next timebox. The rule is being applied against the value it exists to protect.

A. Velocity is a planning measure for forecasting how much the team can take on. It varies naturally, and a rising velocity says nothing about whether what was built is usable or valuable.

B. Started work is partially done work. Adaptive approaches count only completed, accepted items as progress; ten half-finished stories deliver no value and cannot be inspected at the review.

C. Spending the budgeted effort is an input measure inherited from predictive tracking. It measures consumption, not the outcome the iteration set out to achieve.

D. Success in adaptive delivery is a done, potentially usable increment that achieves the objective the team committed to, confirmed by the product owner's acceptance at the review. That is the criterion the iteration was planned against.

A. Seniority is not priority. Taking work directly from a stakeholder bypasses the product owner, breaks the sprint's forecast and invites every stakeholder to route requests to whichever developer they know.

B. The product owner is the single point of prioritisation and orders the backlog by value; the developer's job is to route the request there. If the product owner judges it more valuable than current sprint work, the sprint scope can be renegotiated with the developers.

C. A formal change request through a change control board is the predictive reflex. In an adaptive project change is absorbed through the backlog, not a board; the product owner decides, quickly, without a gate.

D. Swapping an item is a legitimate way to adjust a sprint, which makes this tempting, but the scrum master neither orders the backlog nor decides sprint scope. That decision belongs to the product owner with the developers; asking the scrum master to make it misplaces the role.

A. The process manager runs the process day to day, allocates the people and watches its throughput; that is the supervisor in the stem. Operating a process is not the same as being accountable for its design, so this signature is not the one that authorises a redesign.

B. A product manager is accountable for a product's strategy, market fit and roadmap. Loan approval is an internal process, not a product line, so this role has no authority over how the process is designed.

C. The process owner is accountable for the end-to-end design and performance of the process and is the role that approves changes to it. The supervisor's agreement is valuable input, but the redesign is only authorised when the owner signs it off.

D. A product owner orders a product backlog and decides what an adaptive team builds next. The stem is about who can authorise a change to an operating process, which is the process owner's accountability rather than a backlog decision.

A. Finance was affected by the invoicing feature but was never identified, so their needs never entered the requirements. Stakeholder identification and analysis exists precisely to find every group whose needs, influence or acceptance the solution depends on before elicitation begins.

B. Prioritisation orders the requirements that have already been captured. It cannot surface a need from a department that was never consulted, so ranking the sales requirements more carefully would not have added the finance rules.

C. Traceability shows that each captured requirement is covered by design and testing. The finance requirement was never captured, so a complete matrix would still have shown a fully tested feature that was wrong for finance.

D. Prototyping is a strong elicitation and confirmation technique, but a prototype reviewed only with sales would confirm the sales view. The gap was in who was consulted, not in how well their needs were understood.

A. A regulator imposes requirements from outside the organisation and is a classic external stakeholder, however much influence it has over the solution.

B. Co-location and daily contact are tempting cues, but the analyst is employed by a supplier under contract. Where a person sits does not change whose organisation they belong to; a supplier's staff are external stakeholders.

C. End customers are among the most important stakeholders, but they are outside the organisation delivering the solution and are therefore external.

D. The operations manager is employed by the airport authority, the organisation sponsoring and delivering the project. Internal stakeholders are those inside that organisation, regardless of how often the analyst meets them.

A. A status report is the right channel for periodic progress information, but it is one-way and does not support a discussion that must end in a decision. Sending it beforehand may help, yet it does not use the thirty minutes to reach the decision.

B. A decision-focused presentation suits a senior audience with little time: it frames the two options, states the trade-offs and recommendation, and leaves room for the questions the decision makers need answered before they commit. It matches both the audience and the purpose.

C. A workshop is the tool for building consensus or eliciting requirements with many contributors. The options are already analysed and the audience has thirty minutes, so a half-day co-creation session fits neither the purpose nor the time available.

D. A dashboard supports ongoing monitoring by people who track detail over time. Senior decision makers choosing between two funded options need a synthesis and a recommendation, not requirement-level status.

A. Waiting until the review means the team may build for days on an interpretation that the requirement owners never held. The review is for confirming a completed increment, not for discovering that the two groups understood a requirement differently.

B. Nothing has changed yet: the requirement is ambiguous, not altered. Change control comes into play only if clarification reveals that the agreed scope must actually move, and even then after the meaning has been confirmed.

C. The analyst's central communication role is to keep the people who own the need and the people who build the solution working from the same understanding. Clarifying now, at the source, and passing the answer to the team prevents rework and is why the analyst sits between the two groups.

D. Reserving time for rework accepts the misunderstanding rather than removing it. The analyst can eliminate the cause with a short clarification, which is the better use of the moment than planning around the consequence.

A. A user story captures a single need from one role's point of view in a sentence or two. It is deliberately small and does not show a sequence of hand-offs across departments.

B. A process model (a flow diagram with swimlanes) shows the steps, decisions and hand-offs between roles from the start of a process to its end. It is the tool for seeing where work waits, which is exactly what the team wants.

C. A use case describes how an actor interacts with a system to reach a goal, step by step. It centres on one interaction with the solution, not on how work flows between several departments.

D. A prototype makes a proposed solution tangible so stakeholders can react to it. The team is trying to understand the current process, not to try out a future screen or product.

A. Observation shows what people actually do, including the workarounds they would not think to describe. It is the technique for learning how a process really runs today, and a sample of branches makes it feasible within the month.

B. An interview is right for depth with one person, but the sponsor is not the one performing the work and cannot say how forty branches would receive the change. It answers neither of the two questions the analyst has.

C. Brainstorming generates ideas for how something could be done; it does not produce evidence of how nine hundred clerks handle a claim today, and a single head-office group cannot show how forty branches would receive the change.

D. A survey reaches a large, dispersed population quickly and gives a measurable picture of how a proposed change is received. For nine hundred people in forty locations within a month, it is the technique that scales.

E. A focus group gathers the views of a selected group of stakeholders, but the developers neither perform the claims process nor decide whether the approval change is acceptable in the branches. The wrong participants make the technique miss the target.

A. Ranking is the job of prioritisation techniques such as MoSCoW or multivoting. The table in the stem records relationships, not the relative importance of one requirement over another.

B. Those conditions are acceptance criteria, written with the requirement or user story. The linking table may reference the test that checks them, but it does not define them.

C. Effort belongs to estimating and to the schedule or backlog, not to the linking table. Knowing where a requirement came from and what covers it says nothing about how long it takes.

D. That is the requirements traceability matrix: it shows that every requirement has a source and a covering deliverable and test, exposes orphans and gaps, and supports impact analysis when something changes.

A. That is the product backlog: an emergent, ordered inventory of everything that may be built, owned by the product owner, with the items nearest the top refined to a ready state and the rest kept deliberately coarse.

B. A scope baseline belongs to the predictive approach and is changed through change control. The list in the stem is reordered freely as priorities shift, which is the opposite of a baseline.

C. That is the traceability matrix. The backlog may reference acceptance criteria, but its job is to hold and order the work, not to prove coverage between requirements and tests.

D. That is a release plan or product roadmap. The backlog is the ordered pool the releases draw from; it does not itself assign items to dates or releases.

A. A roadmap places themes in broad timeframes, not features on dates. Reading it as a set of date commitments is the most common misuse and the reason product managers stress that it will change.

B. A scope baseline is a controlled, detailed description of what one release contains. The roadmap sits above releases and stays at the level of themes and outcomes.

C. That is what a product roadmap is for: it aligns stakeholders on where the product is heading, why, and roughly when, so that releases and backlog decisions can be judged against a shared intent.

D. A dependency sequence is what a network diagram and the critical path show. The roadmap does not model tasks or their dependencies; it communicates intent at a much higher level.

A. It has clear customer value, but it depends on login, which arrives only in release two. An item cannot ship before the component it depends on, whatever its value.

B. The release goes live before the quarter ends and the banner is a legal obligation from the day after; leaving it out would make the launch non-compliant. It has no dependency on login and is small, so it fits a minimal first release on every criterion: obligation, risk, dependency and size.

C. Sponsor interest is real, but the item serves an internal reporting need with no customer value and no time constraint. It can wait for a later release without cost, which is what a minimal first release requires.

D. Highest desirability is tempting, but an unestimated item cannot be committed to a fixed-date release and is not needed for compliance or for the app to work. It is a strong candidate for release two or three once sized.

A. The analyst elicits and analyses requirements, but ordering the product backlog is the product owner's accountability. Changing the order unilaterally oversteps the role even when the analysis is sound.

B. Escalation is for issues the accountable role cannot resolve. The product owner has not yet seen the analysis, so nothing has been left unresolved; escalating first would bypass the person whose decision it is.

C. Handing the choice to the developers moves a value decision away from the product owner, and detailing both items in full contradicts just-in-time refinement. The developers decide how to build, not which item carries more value.

D. In an adaptive approach the analyst informs the product owner's decisions with evidence and refinement, while the ordering itself stays with the product owner. Sharing the value analysis respects the role and gives the decision maker what they need.

A. In a predictive approach the baseline is protected by change control. The analyst's role is to analyse what the regulator's change touches, across requirements, design, tests and schedule, and to bring that analysis to the change control process for a decision, however certain the outcome seems.

B. This is the informal shortcut: because the change is mandatory, it feels safe to apply it directly. But altering a baselined requirement without change control loses the impact analysis and the approval record that a predictive project depends on.

C. That is the adaptive reflex in a predictive setting. This project has no iteration backlog; it has an approved baseline, and requirements enter or leave it through change control.

D. Implementing first and documenting later bypasses the approval that governs a baseline and leaves the change unassessed. Lessons learned records what the project learned, not what changed in the requirements.

A. "Quickly" and "easy to notice" cannot be tested without someone deciding what they mean. A criterion that two testers could judge differently is not an acceptance criterion yet.

B. It states the condition, the observable result and the point at which it must occur, so a tester can set up the case and see a pass or fail. It is specific, testable and tied directly to the story.

C. This describes an activity of the team, not a property of the product. Acceptance criteria say what the solution must do for the story to be accepted, not what work must be performed.

D. This restates the story at the same level of generality and points to an unstated requirement elsewhere. It adds no condition a tester could check.

A. Finishing the planned work is the team's own completion signal. It shows neither that every requirement is traced to a verified deliverable nor that the stakeholders who own the need have accepted the module against the acceptance criteria.

B. The traceability matrix is the instrument for readiness: when every requirement has a covering deliverable and that deliverable has been verified, nothing has been dropped and nothing is unproven. A gap in the matrix is a gap in the product.

C. Urgency from the sponsor is a constraint on the schedule, not a condition of readiness. Delivering to a date with unmet criteria transfers the problem to the users and to operations.

D. Passing the team's own tests is verification of what the team chose to test. It says nothing about whether every requirement in the traceability matrix is covered, or whether the stakeholders who own the need have validated the result.

E. Validation confirms that the right thing was built, and it belongs to the people whose need the module serves. Their confirmation against the agreed criteria is the second half of readiness alongside a complete, verified traceability matrix.

A. Verification proves the product was built as specified; it is complete here. But acceptance rests on validation, which asks whether the specified product meets the need, and that question has not been put to the people who hold the need.

B. More verification does not answer a validation question. The tests already pass; running them again with other data checks the same thing more thoroughly and still leaves the desk staff unheard.

C. Validation confirms that the solution meets the stakeholders' actual need, and it is done by or with those stakeholders against the agreed criteria. Until the desk staff have done that, the traceability matrix shows a verified product, not an accepted one.

D. The sponsor's signature is the formal act, but signing on test results alone substitutes authority for validation. The sponsor should sign after the owning stakeholders have confirmed the solution against the criteria, not instead of them.