โ† All Project Management Flashcard Decks

Project Scope and WBS Flashcards

7 cards from real Project Management practice questions. Tap to flip, then mark Knew It or Still Learning โ€” missed cards come back until you master them.

Read the first 7 Project Scope and WBS flashcards as text
  1. The 100% rule in WBS development states that:

    Answer: The WBS must capture 100% of the work, including project management work

    The 100% rule requires that the WBS captures all deliverables and work, including project management activities, without overlap.

  2. Gold plating in project management refers to:

    Answer: Adding features beyond the agreed scope without a change request

    Gold plating is adding extra scope or features not requested by the client, which consumes resources without formal authorization.

  3. What differentiates a project scope statement from a product scope statement?

    Answer: Product scope describes project deliverables; project scope describes the work to produce them

    Product scope describes the features of the product or service, while project scope describes the work required to deliver it.

  4. During Validate Scope, a key deliverable is reviewed and accepted by the customer. This acceptance is documented in:

    Answer: Accepted deliverables and change requests if rework is needed

    Accepted deliverables are the primary output of Validate Scope, along with change requests for items requiring rework.

  5. A project manager is working with SMEs to break down a high-level deliverable into smaller components. This technique is called:

    Answer: Decomposition

    Decomposition is the technique of breaking down project deliverables and work into smaller, more manageable components.

  6. When scope definition is poor at project initiation, the most likely consequence is:

    Answer: Frequent scope creep and cost overruns

    Poorly defined scope leads to uncontrolled changes, rework, and budget and schedule overruns throughout the project.

  7. Which output of the Collect Requirements process is used as a key input to Define Scope?

    Answer: Requirements documentation

    Requirements documentation, which captures stakeholder needs, is a primary input to the Define Scope process.