Project Scope and Work Breakdown Structure (WBS): Scope Baseline, WBS, Responsibility Matrix Questions

Question 1

Define project scope.

Accepted Answer

**Project scope** is the work that must be done to deliver the required product/service/result.

Question 2

What is WBS?

Accepted Answer

**WBS** is a hierarchical breakdown of project scope into smaller components.

Question 3

What is a work package?

Accepted Answer

A **work package** is the lowest-level WBS component that can be assigned and estimated.

Question 4

State the 100% rule.

Accepted Answer

WBS should include **100% of the work** defined by the scope (no missing work).

Question 5

What is WBS dictionary?

Accepted Answer

A **WBS dictionary** provides detailed info about WBS components/work packages.

Question 6

Expand RACI.

Accepted Answer

**Responsible, Accountable, Consulted, Informed**.

Question 7

Differentiate between product scope and project scope.

Accepted Answer

**Product scope** refers to features/functions of the product. **Project scope** refers to all the work needed to deliver that product (requirements, design, development, testing, deployment). Clear distinction avoids confusion in planning.

Question 8

Explain scope baseline and its components.

Accepted Answer

Scope baseline is the approved scope used for control. It includes **scope statement**, **WBS**, and **WBS dictionary**. Changes to scope should be managed through change control.

Question 9

Explain WBS and mention any three benefits.

Accepted Answer

WBS decomposes project scope into manageable parts. Benefits (any three): ensures completeness (100% rule), improves estimation of time/cost, helps assign responsibilities, supports scheduling and risk identification.

Question 10

Explain work package and why it is important.

Accepted Answer

Work package is the lowest-level WBS element used for assignment and estimation. It is important because it is the unit for scheduling, costing, tracking progress, and assigning responsibility.

Question 11

Explain WBS dictionary and what information it contains.

Accepted Answer

WBS dictionary gives details of each work package: description, owner, acceptance criteria, resources, duration and cost estimates. It removes ambiguity and supports execution.

Question 12

Explain RACI and its benefit.

Accepted Answer

RACI assigns **Responsible**, **Accountable**, **Consulted**, **Informed** for each work package. Benefit: clarity of roles, better communication, and reduced delays due to confusion.

Question 13

Explain WBS and its benefits with a flowchart.

Accepted Answer

### **Explain WBS and its benefits with a flowchart**

A **Work Breakdown Structure (WBS)** is a hierarchical decomposition of total project scope into smaller, manageable components.

**Benefits**:
- ensures **completeness** of work (supports **100% rule**)
- improves estimation of time and cost
- helps assign responsibilities
- supports scheduling, budgeting and risk planning

```text
Scope statement → Identify deliverables → Decompose → Work packages → Verify 100% rule
```

Thus WBS is a foundation for planning and control.

Question 14

Explain scope baseline and its components with a table.

Accepted Answer

### **Explain scope baseline and its components (with table)**

A **scope baseline** is the approved scope used to measure and control scope performance.

| Component | Purpose |
|---|---|
| **Scope statement** | defines deliverables and boundaries |
| **WBS** | breaks down total work |
| **WBS dictionary** | details each work package |

Once baseline is approved, scope changes should follow formal change control.

Therefore scope baseline prevents scope creep and supports project control.

Question 15

Explain RACI / responsibility matrix with example table and flow.

Accepted Answer

### **Explain RACI / Responsibility Assignment Matrix with example**

A **Responsibility Assignment Matrix (RAM)** maps work packages to roles.

**RACI** meaning:
- **R** Responsible: does the work
- **A** Accountable: final owner/approver
- **C** Consulted: provides input
- **I** Informed: kept updated

Example (mini):

| Work package | PM | Dev | QA | Client |
|---|---|---|---|---|
| Requirements | A | R | C | C |
| Testing | C | C | R | I |

```text
WBS work packages → assign R/A/C/I → clarity → less confusion and delays
```

Thus RACI improves accountability and communication.

Project Scope and Work Breakdown Structure (WBS): Scope Baseline, WBS, Responsibility Matrix

8 more questions to unlock