Which option is the recommended scope for a work package?

Question

Options

• Athree business capabilities
• Bone technical subsystem
• Cone major business capability
• Dno recommended size

• A
  4% (1)
• C
  91% (21)
• D
  4% (1)

Explanation

Option C is correct because a work package should be scoped to one major business capability, giving it a clear, manageable boundary that ties directly to a single deliverable outcome without becoming too broad or too granular to govern effectively.

• A (three business capabilities) is wrong because spanning multiple capabilities increases complexity, creates cross-team dependencies, and makes it harder to track completion or assign ownership.
• B (one technical subsystem) is wrong because work packages are defined around business outcomes, not technical architecture - framing them around subsystems confuses delivery scope with solution design.
• D (no recommended size) is wrong because the framework does provide sizing guidance; leaving scope undefined leads to inconsistent planning and governance.

Memory tip: Think of a work package as a "one job, one capability" rule - just as a microservice ideally does one thing, a work package targets one major business capability to stay focused and accountable.

No community discussion yet for this question.