I85PREP
⌘ K
EXIN Dynamic Project Management Method Foundation study materials
EXIN Dynamic Project Management Method Foundation study resources

EXIN Dynamic Project Management Method Foundation practice questions

One question at a time. Build your EXIN Dynamic Project Management Method Foundation understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Project Goals

In the Dynamic Project Management Method, what is the primary purpose of defining project goals at the start of an initiative?

  1. To estimate the total budget required for every work package
  2. To document the historical background of the organization
  3. To assign individual performance bonuses to team members
  4. To provide a shared direction that guides decisions and prioritization throughout the project Correct answer.

Explanation

Goals give the project a common direction so that choices about scope, effort and priorities can be judged against a shared reference. Budgeting, rewards and organizational history are separate concerns that do not define the goal itself.

Question 2Project Goals

A project team writes its main goal as 'improve the customer portal'. Which revision best fits the Dynamic Project Management Method's emphasis on clear, verifiable goals?

  1. Reduce portal page load time to under two seconds by the end of Q3 Correct answer.
  2. Improve the portal as much as the budget allows
  3. Consider whether the portal might perhaps be modernized
  4. Make the portal better in every possible way

Explanation

A usable goal states a measurable outcome and a time frame so that progress can be verified. Vague aspirations such as 'better' or 'as much as possible' cannot be tested and leave the team without a decision reference.

Question 3Project Goals

Within the Dynamic Project Management Method, how do project goals relate to the project's deliverables?

  1. Goals are derived only after all deliverables are complete
  2. Deliverables replace goals once execution begins
  3. Deliverables are the tangible outputs intended to achieve the goals Correct answer.
  4. Goals and deliverables are identical concepts

Explanation

Goals express the intended outcome, while deliverables are the concrete products or results produced to reach that outcome. Keeping the two distinct lets a team change deliverables without losing sight of the underlying goal.

Question 4Project Goals

A sponsor asks why a project needs an explicitly recorded goal rather than an informal understanding. Which argument is most consistent with the Dynamic Project Management Method?

  1. A recorded goal eliminates all risks during execution
  2. A recorded goal allows scope changes to be assessed against an agreed reference Correct answer.
  3. A recorded goal guarantees the project will finish under budget
  4. A recorded goal removes the need for stakeholder communication

Explanation

An agreed, recorded goal acts as a stable reference against which change requests and trade-offs can be evaluated. It supports communication and risk awareness but cannot guarantee budget outcomes or remove risks.

Question 5Project Goals

A team distinguishes between the project goal and the project objective. In the Dynamic Project Management Method, which statement best captures the difference?

  1. The goal applies only to the sponsor and objectives apply only to developers
  2. The goal states the desired overall outcome, while objectives break it into specific, measurable targets Correct answer.
  3. The goal is short term and the objective is permanent
  4. The goal is optional and objectives are mandatory

Explanation

The goal describes the broader desired end result, and objectives translate it into concrete, measurable targets that guide planning and control. Both are part of steering the project and are not restricted to particular roles.

Question 6Project Goals

During a review, a stakeholder claims the project goal has been met because all planned deliverables were produced. Which response reflects sound goal evaluation in the Dynamic Project Management Method?

  1. The goal is met only if the intended outcome or benefit is actually realized Correct answer.
  2. The goal cannot be evaluated until the next fiscal year
  3. Producing deliverables automatically proves the goal is achieved
  4. Goal achievement is decided solely by the project manager

Explanation

Deliverables are means, not ends; the goal is achieved when the intended outcome or benefit is realized. Completion of outputs alone does not demonstrate that the desired result was obtained.

Question 7Project Goals

What role do success criteria play in relation to project goals in the Dynamic Project Management Method?

  1. They describe the technical architecture of the solution
  2. They define how achievement of the goal will be recognized and measured Correct answer.
  3. They list the team members responsible for each task
  4. They replace the goal with a schedule

Explanation

Success criteria make a goal assessable by stating the conditions and measures that show whether it has been achieved. They complement the goal rather than replacing it or describing staffing or architecture.

Question 8Project Goals

A project's goal statement mentions only the internal efficiency the team wants to gain, with no reference to the beneficiary. Which improvement aligns best with Dynamic Project Management Method thinking?

  1. Postpone goal definition until the project is nearly finished
  2. Add the intended value for the customer or user the project serves Correct answer.
  3. Replace the goal with a list of software features
  4. Remove all measurable targets to keep the goal flexible

Explanation

Goals should express the value delivered to the beneficiary, not only internal convenience. Linking the goal to user or customer value keeps priorities anchored to the reason the project exists.

Question 9Project Goals

In the Dynamic Project Management Method, why should project goals remain relatively stable while detailed plans may change frequently?

  1. Because plans are never allowed to change once approved
  2. Because stability of goals removes the need for stakeholder input
  3. Because detailed plans are irrelevant to project success
  4. Because goals provide the enduring reference against which changing plans are judged Correct answer.

Explanation

Goals anchor the project and give meaning to plan adjustments, so they tend to be stable while the route to them adapts. Plans do change, and that flexibility is exactly why a stable reference is valuable.

Question 10Project Goals

A team lists 'increase customer satisfaction' as its only goal. What is the main weakness of this goal from a Dynamic Project Management Method perspective?

  1. It lacks a measure, baseline and time frame to make achievement verifiable Correct answer.
  2. It is written as a verb phrase rather than a noun
  3. It refers to customers, who are outside the project scope
  4. It is too specific and leaves no room for creativity

Explanation

A goal without a measure, baseline or time frame cannot be assessed, so the team cannot tell whether it has succeeded. Specificity and beneficiary focus are strengths, not weaknesses.

Question 11Project Goals

Which situation best illustrates a conflict between project goals that a Dynamic Project Management Method practitioner must resolve through prioritization?

  1. The project manager attends a training course
  2. A stakeholder requests a status report on a Friday
  3. Two goals demand the same limited budget, and one must be prioritized Correct answer.
  4. The team agrees on a single measurable goal and a clear deadline

Explanation

When goals compete for the same constrained resources, the team must decide which goal takes precedence, and that decision should be explicit. Routine reporting and training do not constitute goal conflicts.

Question 12Project Goals

A project team is unsure whether a proposed feature belongs in scope. Which goal-related question is most useful for deciding?

  1. Did a competitor implement a similar feature?
  2. Does the feature directly contribute to achieving the agreed project goal? Correct answer.
  3. Is the feature technically interesting to build?
  4. Can the feature be built with the current programming language?

Explanation

Scope decisions should be tested against the agreed goal, since the goal defines the value the project intends to deliver. Technical interest, competitor behavior and tooling are secondary considerations.

Question 13Project Goals

In the Dynamic Project Management Method, what is the relationship between the business case and the project goal?

  1. The business case is written after the goal is achieved
  2. The business case replaces the goal entirely
  3. The goal should reflect the justification and expected value described in the business case Correct answer.
  4. The business case and the goal must contradict each other to allow debate

Explanation

The business case explains why the project is worthwhile, and the goal should express the outcome that delivers that justification. Keeping them aligned ensures the project pursues the value it was approved for.

Question 14Project Goals

A project's goal is expressed only in terms of activities, such as 'hold twelve workshops'. Why is this problematic under the Dynamic Project Management Method?

  1. It makes the goal too measurable
  2. It describes effort rather than the outcome the workshops are meant to achieve Correct answer.
  3. Workshops are always too expensive for projects
  4. Activities cannot be scheduled in a project

Explanation

A goal should state the intended result, not merely the activity performed. Twelve workshops are a means; without an outcome statement the team cannot judge whether the effort produced value.

Question 15Project Goals

Which of the following best describes a 'SMART' style goal as applied to project goal definition in the Dynamic Project Management Method?

  1. A goal that is specific, measurable, achievable, relevant and time-bound Correct answer.
  2. A goal that lists every task the team will perform
  3. A goal that is deliberately vague to allow reinterpretation
  4. A goal that is set only by the project manager without consultation

Explanation

SMART goals state clearly what is to be achieved, how it will be measured, whether it is attainable, why it matters and by when. This structure makes the goal usable for planning and evaluation.

Question 16Project Goals

A project team discovers mid-way that the original goal is no longer relevant because the market has changed. What does the Dynamic Project Management Method suggest?

  1. Review the goal with the sponsor and stakeholders and formally adjust or close the project Correct answer.
  2. Ignore the change and focus on delivering the original deliverables
  3. Continue silently to protect the original plan
  4. Extend the deadline indefinitely without review

Explanation

Goals should be reviewed when significant change occurs, and adjustments should be agreed with those who authorized the project. Silently continuing or unilaterally extending timelines undermines governance.

Question 17Project Goals

What is the main benefit of involving key stakeholders when defining project goals?

  1. It ensures the goal reflects shared expectations and reduces later disputes Correct answer.
  2. It guarantees that the project will need no changes
  3. It removes the need to document the goal in writing
  4. It transfers all accountability for the project to the stakeholders

Explanation

Stakeholder involvement builds a shared understanding of what success means, which reduces misunderstandings and disputes later. Accountability and documentation still remain necessary, and change is never eliminated.

Question 18Project Goals

A goal statement reads: 'Within six months, reduce order-processing errors by 30 percent compared with the current baseline.' Which element is missing if the team also needs to know who benefits?

  1. The beneficiary or user group affected by the improvement Correct answer.
  2. A comparison baseline
  3. A measurable target
  4. A time frame

Explanation

The statement already includes a measure, a time frame and a baseline, but it does not say whose errors or which user group benefits. Naming the beneficiary completes the value orientation of the goal.

Question 19Project Goals

How should a project team treat a goal that is achievable only by compromising a mandatory regulatory requirement?

  1. Ignore the regulation until the audit occurs
  2. Reject or revise the goal so that it remains consistent with mandatory constraints Correct answer.
  3. Accept the compromise because goals always override compliance
  4. Delegate the decision to the least experienced team member

Explanation

Goals must operate within mandatory constraints such as legal and regulatory requirements. A goal that requires breaching them is not acceptable and should be revised or rejected.

Question 20Project Goals

Which statement best explains why a project goal should be communicated to the whole team rather than kept with the sponsor?

  1. So that every team member can align daily decisions with the intended outcome Correct answer.
  2. So that the team can change the goal without approval
  3. So that the goal can be kept secret from other stakeholders
  4. So that the sponsor can avoid attending meetings

Explanation

When the whole team understands the goal, individual decisions and trade-offs can be made consistently with the intended outcome. Communication does not remove approval requirements or justify secrecy.

Question 21Project Context

In the Dynamic Project Management Method, a project is best described as which kind of undertaking?

  1. A personal activity plan owned only by the project manager
  2. A temporary organisation created to deliver an agreed result within constraints of time, cost and scope Correct answer.
  3. An open-ended programme of work with no defined end date
  4. A permanent department responsible for routine operational work

Explanation

Dynamic Project Management treats a project as a temporary organisation: it is set up for a defined purpose, staffed for that purpose, and disbanded once the agreed result is delivered. This distinguishes projects from permanent line functions, which continue after the project ends.

Question 22Project Context

Which statement correctly characterises the relationship between a project and its business case in the Dynamic Project Management Method?

  1. The business case justifies the investment and is reviewed at decision points so the project can be stopped if the justification fails Correct answer.
  2. The business case is only required for projects above a fixed financial threshold
  3. The business case replaces the project plan once the project starts
  4. The business case is written once at initiation and never revisited

Explanation

The business case records why the investment is worthwhile and is used at decision points to confirm the project still deserves its resources. If the justification no longer holds, the method allows the project to be stopped or changed.

Question 23Project Context

A sponsor asks who is accountable for ensuring that the project delivers the agreed benefits. Which role in the Dynamic Project Management Method carries this accountability?

  1. The external supplier delivering the work package
  2. The project owner, who represents the business interest Correct answer.
  3. The project support officer
  4. The team member with the longest tenure

Explanation

The project owner represents the business interest and is accountable for the project's justification and benefits, while the project manager handles day-to-day delivery. This separation keeps business accountability with the party that owns the investment.

Question 24Project Context

Which element belongs to the project context rather than to the project result itself?

  1. The test script used to verify a deliverable
  2. The acceptance criteria of the final deliverable
  3. The organisational strategy the project is meant to support Correct answer.
  4. The specification of a work package product

Explanation

The project context covers the surrounding organisational and strategic setting in which the project exists, including the strategy it supports. Deliverable specifications, acceptance criteria and test scripts belong to the result and its quality control.

Question 25Project Context

What is the main purpose of defining the project scope boundary at the start of a project?

  1. To state what the project will and will not deliver, so expectations and change requests can be judged against it Correct answer.
  2. To fix the final cost before any design work begins
  3. To record the names of all stakeholders who may be affected
  4. To list every activity the team will perform in sequence

Explanation

A scope boundary states both what is included and what is excluded, giving a reference against which later change requests and expectations can be assessed. It is not a schedule, a stakeholder register, or a cost estimate.

Question 26Project Context

Which of the following is an example of an external factor in the project context that the project manager should analyse?

  1. The team's agreed working hours
  2. The availability of internal subject-matter experts
  3. A change in relevant legislation affecting the deliverable Correct answer.
  4. The organisation's internal approval procedure

Explanation

External factors originate outside the organisation, such as legislation, market conditions or technology shifts, and can affect the project's viability. Internal staffing, procedures and working arrangements are internal context factors.

Question 27Project Context

A project is part of a larger programme. What does the Dynamic Project Management Method expect the project manager to do with programme-level decisions?

  1. Ignore them because the project has its own business case
  2. Align the project's objectives, dependencies and reporting with the programme so the wider benefits remain achievable Correct answer.
  3. Replace the project plan with the programme plan
  4. Escalate every project decision to the programme board for approval

Explanation

When a project sits inside a programme, its objectives and dependencies must fit the wider programme so that combined benefits can be realised. The project still keeps its own plan and management, but reports and aligns where the programme requires it.

Question 28Project Context

During context analysis the team identifies a key customer group that will be strongly affected but has not been involved. What is the most appropriate response in the method?

  1. Add the group to the stakeholder analysis and plan engagement proportionate to its influence and interest Correct answer.
  2. Wait until the deliverable is complete and then inform the group
  3. Delegate contact with the group to the supplier
  4. Remove the group from consideration because it has not asked to be involved

Explanation

Stakeholder analysis identifies who is affected and how much influence and interest they have, and engagement is then planned accordingly. Early, proportionate engagement reduces the risk of late resistance or rejected results.

Question 29Project Context

A project manager is deciding how much governance a small, low-risk project needs. Which approach is consistent with the method's principle of proportionality?

  1. Apply the same full set of reports and boards used on the largest projects
  2. Scale decision points, reporting and documentation to the size, risk and complexity of the project Correct answer.
  3. Remove all decision points so the team can move faster
  4. Rely only on informal conversations with no recorded decisions

Explanation

The method applies management effort in proportion to the size, risk and complexity of the undertaking, so lighter governance suits smaller, lower-risk projects. Decision points and records are still kept, simply at a scale that fits.

Question 30Project Context

Why does the Dynamic Project Management Method place the project in its organisational context before detailed planning begins?

  1. Because understanding strategy, stakeholders and constraints shapes what the plan must achieve and what it must respect Correct answer.
  2. Because planning tools cannot be used until the context document is signed
  3. Because the context analysis replaces the need for a business case
  4. Because context analysis fixes the final schedule baseline

Explanation

Context analysis reveals the strategic intent, affected parties and constraints that the plan must satisfy, so it informs planning rather than replacing it. Doing it first prevents a technically sound plan that ignores organisational reality.

Question 31Project Context

A stakeholder has high influence over the project but low interest in its details. How should the project manager treat this stakeholder in the engagement approach?

  1. Exclude the stakeholder from all communication to save time
  2. Send full weekly progress reports with all technical detail
  3. Ask the stakeholder to join the daily team meetings
  4. Keep the stakeholder satisfied with concise, outcome-focused information at key decision points Correct answer.

Explanation

High influence with low interest calls for a strategy of keeping the stakeholder satisfied through brief, outcome-level updates at decision points. Detailed reporting would waste attention the stakeholder is unwilling to give.

Question 32Project Context

Which pair correctly matches a context factor with the type of constraint it typically creates for a project?

  1. Company logo and the project's benefit measure
  2. Regulatory approval requirement and a mandatory compliance gate before release Correct answer.
  3. Team motivation and a fixed price contract
  4. Office location and the number of deliverable features

Explanation

A regulatory requirement is a genuine constraint because it imposes a mandatory step, such as a compliance gate, that the project cannot skip. Constraints restrict the freedom of the project in a way the plan must respect.

Question 33Project Context

An organisation runs several projects that share one specialist team. What context issue should the project manager address in the plan?

  1. The dependency can be ignored because each project has its own budget
  2. The shared resource creates a dependency that must be scheduled and agreed with the other projects Correct answer.
  3. The specialist team should report only to the largest project
  4. The shared team should be duplicated for each project to avoid discussion

Explanation

Shared resources create inter-project dependencies that must be identified, scheduled and agreed so that competing demands do not cause unexpected delay. Recognising this dependency is part of analysing the organisational context.

Question 34Project Context

What distinguishes a project from a programme in the Dynamic Project Management Method?

  1. A project always lasts longer than a programme
  2. A programme has no business justification
  3. A programme is managed only by the project support office
  4. A programme coordinates related projects and change activities to achieve benefits that the individual projects could not deliver alone Correct answer.

Explanation

A programme groups related projects and other change activities so that combined outcomes and benefits exceed what each project delivers separately. Projects remain temporary undertakings with their own results and justification.

Question 35Project Context

A project manager learns that the organisation's strategy has shifted and the project's original benefit is now less valuable. What is the appropriate action within the method?

  1. Continue unchanged because the plan was already approved
  2. Raise the change at the next decision point so the business case and project can be re-evaluated Correct answer.
  3. Quietly reduce the team size without informing the owner
  4. Change the deliverable specification without recording the decision

Explanation

Decision points exist so that the continuing justification of the project can be reviewed against current circumstances. Raising the strategic shift there lets the owner decide whether to continue, change or stop the project.

Question 36Project Context

Which statement best explains why the project context includes the organisation's culture and informal power structures?

  1. Because culture determines the accounting rules for the project budget
  2. Because informal structures are always hostile to projects
  3. Because informal influence affects how decisions are made, accepted and resisted, and therefore how the project must engage Correct answer.
  4. Because culture replaces the need for formal governance

Explanation

Informal power and culture shape how decisions gain acceptance and where resistance may arise, so engagement and communication must take them into account. Formal governance still exists, but it operates within that cultural reality.

Question 37Project Context

A project has a fixed regulatory deadline and a scope that could expand indefinitely. Which combination of context constraints should drive the project manager's planning approach?

  1. Treat the date as a hard constraint and manage scope through prioritisation and controlled change Correct answer.
  2. Fix the scope and let the deadline and cost vary
  3. Increase the team size whenever a new requirement appears
  4. Ignore the deadline until the design is complete

Explanation

When a date is externally imposed, it becomes a hard constraint, so the plan must protect it by prioritising scope and controlling change. Allowing scope to expand freely would put the regulatory deadline at risk.

Question 38Project Context

Two influential stakeholders hold conflicting expectations about what the project will deliver. What does sound context management require the project manager to do first?

  1. Delay all delivery work until the conflict disappears on its own
  2. Choose the expectation of the more senior stakeholder without discussion
  3. Record both expectations in the plan and deliver neither
  4. Document the conflict and bring the parties together to agree the scope boundary and acceptance criteria Correct answer.

Explanation

Conflicting expectations are a context risk that must be surfaced and resolved through agreed scope and acceptance criteria, not left to seniority or to chance. A recorded, jointly agreed boundary gives a reference for later decisions.

Question 39Project Context

A sponsoring director wants the project to proceed because it is visible and prestigious, although the business case shows weak benefits. How should the project manager respond within the method?

  1. Proceed and record the weak benefits as a minor risk
  2. Rewrite the business case to show stronger benefits
  3. Present the benefit analysis at the decision point so the owner can make an informed go/no-go judgement Correct answer.
  4. Refuse to work on the project and withdraw from the organisation

Explanation

The decision point is the proper forum for weighing the business case against the investment, and the project manager's duty is to present the evidence honestly. The owner, who carries business accountability, then decides whether to continue.

Question 40Project Context

Which action best demonstrates that a project manager has translated context analysis into practical project arrangements?

  1. Repeating the context analysis at every team meeting
  2. Filing the context analysis in the project archive without further use
  3. Copying the context analysis from a previous project unchanged
  4. Using identified constraints and stakeholder needs to shape the plan, decision points and communication approach Correct answer.

Explanation

Context analysis has value only when its findings shape concrete arrangements such as the plan, the timing of decision points and the communication approach. That translation is what connects the project to its environment.

Question 41DPMM® Principles

In DPMM®, which statement best describes the role of principles in guiding a project?

  1. They provide direction for behaviour and decision-making that teams apply in context. Correct answer.
  2. They are optional suggestions used only when a project falls behind schedule.
  3. They are contractual obligations agreed with the customer at project start.
  4. They are fixed procedures that must be executed in a prescribed sequence.

Explanation

DPMM® principles are behavioural guidelines that steer how people decide and act across a project, rather than step-by-step procedures. Because they are applied with judgement, the same principle can look different from one project to another. Procedures, by contrast, prescribe a fixed sequence of activities.

Question 42DPMM® Principles

A DPMM® team must decide how much documentation to produce for a small, low-risk project. Which application of the principles fits best?

  1. Let each team member choose documentation format individually without coordination.
  2. Skip documentation entirely because the project is small and low risk.
  3. Tailor the documentation to what adds value for this project and its stakeholders. Correct answer.
  4. Produce the full document set defined for large projects to stay consistent.

Explanation

Tailoring is central to DPMM®: the approach, including documentation, is scaled to the size, risk and context of the work. The aim is to add value rather than to follow a uniform template. Skipping documentation altogether ignores stakeholder needs and traceability.

Question 43DPMM® Principles

What does the DPMM® principle of stakeholder involvement primarily require from a project team?

  1. Informing stakeholders only after each major decision has been finalised.
  2. Identifying relevant stakeholders and engaging them appropriately throughout the project. Correct answer.
  3. Delegating all decisions to the most senior stakeholder available.
  4. Limiting contact with stakeholders to formal contractual milestones.

Explanation

The principle calls for identifying who is affected by or can influence the project, and engaging them in a purposeful way across its life. Engagement is continuous and adapted to each stakeholder's interest and influence. One-way information after the fact is not engagement.

Question 44DPMM® Principles

A project sponsor wants certainty on scope before any work begins. How should a DPMM® team respond, consistent with its principles?

  1. Acknowledge uncertainty and manage it progressively through short cycles and feedback. Correct answer.
  2. Freeze the full scope at the outset and refuse any later change.
  3. Accept that uncertainty cannot be managed and wait for it to resolve itself.
  4. Expand the scope early so that later reductions are easier to justify.

Explanation

DPMM® recognises that uncertainty is inherent in projects and should be addressed progressively rather than denied. Short cycles, feedback and incremental decisions reduce uncertainty over time. Pretending that scope can be fully frozen upfront simply hides risk.

Question 45DPMM® Principles

Which behaviour most clearly reflects the DPMM® principle of team empowerment?

  1. The project manager approves every task assignment and technical decision.
  2. Empowerment is granted only after the team has completed all planned deliverables.
  3. The team is given clear boundaries and authority to decide how to do its work. Correct answer.
  4. Decision rights are kept undefined so the team can interpret them flexibly.

Explanation

Empowerment means giving the team real authority to make decisions within agreed boundaries and goals. Clear boundaries make autonomy safe and aligned with project objectives. Autonomy without defined limits is not empowerment but ambiguity.

Question 46DPMM® Principles

A DPMM® team reviews progress every two weeks and adjusts its plan based on what it learned. Which principle does this behaviour most directly express?

  1. Maximising the number of deliverables produced per cycle.
  2. Centralised control of all information by the project manager.
  3. Learning and continuous improvement through regular reflection. Correct answer.
  4. Strict adherence to the original baseline regardless of new information.

Explanation

Regular review and adjustment is the practical expression of learning and continuous improvement. The team uses feedback to refine both the product and the way it works. Holding to a baseline regardless of new information is the opposite behaviour.

Question 47DPMM® Principles

What is the intended relationship between DPMM® principles and the method's practices and techniques?

  1. Principles and practices are unrelated and chosen independently.
  2. Principles give the rationale, and practices are ways of putting them into effect. Correct answer.
  3. Practices replace principles once a team becomes experienced.
  4. Practices are mandatory, and principles are only used for audits.

Explanation

Principles express the underlying intent, while practices and techniques are concrete means of realising that intent. Teams select and adapt practices so that they serve the principles in their context. Principles are not an audit-only artefact.

Question 48DPMM® Principles

A DPMM® project faces a choice between delivering a narrow, valuable increment soon and a broad increment much later. Which principle-informed reasoning is most appropriate?

  1. Deliver value early and often so that feedback can shape later increments. Correct answer.
  2. Always choose the broad increment because it demonstrates greater ambition.
  3. Let the customer decide alone, without the team's advice on feasibility.
  4. Delay all delivery until the complete scope is finished and tested.

Explanation

Delivering value early and frequently allows stakeholders to see results and provide feedback that improves later work. It also reduces the risk of building the wrong thing for a long time. Ambition of scope is not itself a reason to postpone all value.

Question 49DPMM® Principles

How should a DPMM® team treat a principle when applying it seems to conflict with another principle in a specific situation?

  1. Ignore both principles until the conflict disappears on its own.
  2. Follow whichever principle appears first in the method's documentation.
  3. Escalate every conflict to the sponsor for a binding ruling.
  4. Weigh the principles in context and make a reasoned, transparent trade-off. Correct answer.

Explanation

Principles can pull in different directions, and DPMM® expects teams to balance them using judgement rather than mechanical rules. A reasoned trade-off, made transparent to stakeholders, keeps decisions defensible. The order in which principles are listed carries no priority.

Question 50DPMM® Principles

Which statement best captures the DPMM® view of the customer or user in guiding project decisions?

  1. Customer opinions matter only for acceptance testing at the end.
  2. Customer involvement should be minimised to protect the team's focus.
  3. Customer feedback is a primary source of direction for shaping the product. Correct answer.
  4. Customer needs are fixed at kick-off and should not be revisited.

Explanation

DPMM® treats the customer or user as a continuous source of direction, so feedback shapes the product throughout. Needs are explored and refined rather than frozen once at kick-off. Restricting customer input to final acceptance loses the benefit of early learning.