Time is running short and the Must Have requirements for the data entry screen of the web page, as recorded in the Prioritised Requirements List, are not going to be completed on time. What action…

Question

Options

• AChange the end date of the Timebox.
• BEnsure that this issue is escalated to the project level roles.
• CAmend the end date in the Delivery Plan.
• DAccept that the Must Have requirements will not be delivered on time.

• A
  23% (11)
• B
  58% (28)
• C
  6% (3)
• D
  13% (6)

Explanation

In DSDM/AgilePM, a Timebox has a fixed end date - it is sacrosanct and cannot be moved by the Project Manager unilaterally. When Must Have requirements are at risk, this represents a potential project-level threat that must be escalated to roles with the authority to make strategic decisions (such as the Business Sponsor or Project Board), not solved locally.

Why the distractors are wrong:

• A & C both involve changing the Timebox or Delivery Plan end date - this directly violates the DSDM principle that Timebox boundaries are fixed. The PM does not have the authority to do this.
• D is wrong because Must Haves are defined as requirements that the solution cannot be delivered without. Simply accepting they'll be missed is not an acceptable outcome and ignores the proper escalation process.

Memory tip: Think of it this way - Must Haves are non-negotiable by definition, so when they're threatened, the response must also be non-negotiable: escalate up, never move the clock. If "Must" is in trouble, it's above your pay grade to fix silently.

No community discussion yet for this question.