The Marketing Director has insisted that detailed requirements for the new coffee bar insurance web pages should be clearly defined in the early phases of the project. What action should the Project…

Question

Options

• BAgree to document the finite details of each requirement to ensure the
• CHold an early discussion to the level of detail necessary to establish a
• DCapture the Marketing Director's requirements in detail but leave the

• B
  13% (2)
• C
  69% (11)
• D
  19% (3)

Explanation

Option C is correct because effective project management calls for progressive elaboration - requirements should be discussed and documented only to the level of detail needed to move forward at that stage, not exhaustively defined upfront. Locking in granular details too early wastes time, since requirements naturally evolve and premature specificity creates unnecessary rework.

Option B is wrong because agreeing to document finite details of every requirement early is an over-commitment - it frontloads analysis effort before enough is known and implies a rigid, waterfall-style approach that resists change.

Option D is wrong because it introduces an inconsistency: capturing the Marketing Director's requirements in detail but leaving something undefined suggests a selective or incomplete approach that doesn't reflect sound requirements management practice - it's a partial solution that typically leads to gaps or conflicts later.

Memory tip: Think "just enough, just in time." The PM's job early on is to establish sufficient clarity to proceed, not to nail down every pixel of a webpage before the project has even scoped the work. When you see a stakeholder pushing for premature detail, the right answer is always the one that reframes the level of detail, not blindly agrees or refuses.

No community discussion yet for this question.