Monitoring, Control and Closure: Change Control, Reporting, Documentation, Lessons Learned and Agile Overview Questions

Question 1

Define monitoring and control.

Accepted Answer

**Monitoring and control** is tracking project performance and taking corrective action to meet objectives.

Question 2

What is a baseline?

Accepted Answer

A **baseline** is an approved plan used as a reference to measure performance.

Question 3

What is change control?

Accepted Answer

**Change control** is a formal process to evaluate and approve/reject changes to baselines.

Question 4

Expand CCB.

Accepted Answer

**Change Control Board**.

Question 5

What is project closure?

Accepted Answer

**Project closure** is formal completion with acceptance, handover and documentation.

Question 6

What is Agile (one line)?

Accepted Answer

**Agile** is an iterative approach with frequent delivery and feedback.

Question 7

Explain why monitoring and control is required.

Accepted Answer

Monitoring and control helps track progress against baselines, detect variances early, manage risks/issues, and take corrective actions. It prevents delays and cost overruns and improves transparency.

Question 8

Explain contents of a status report (any three).

Accepted Answer

Status report may include: progress summary, schedule/cost variance, key risks/issues, change requests summary, and next steps/help needed. This keeps stakeholders informed and supports decisions.

Question 9

Explain change control and its benefit.

Accepted Answer

Change control evaluates change requests, analyzes impacts (scope/time/cost/risk), and gets approval before implementation. Benefit: prevents **scope creep**, controls budget/schedule, and ensures only justified changes are made.

Question 10

What is CCB and what decisions can it take?

Accepted Answer

CCB (Change Control Board) reviews change requests. It can approve, reject, defer, or request more information, based on project impact and priorities.

Question 11

Explain key steps in project closure.

Accepted Answer

Closure includes acceptance sign-off, handover, closing contracts/payments, releasing resources, archiving documents, and recording lessons learned. It formally ends the project.

Question 12

Differentiate Agile and Waterfall (brief).

Accepted Answer

**Waterfall** is sequential (phase-by-phase) and change is harder. **Agile** is iterative with frequent releases and adapts to feedback and change more easily.

Question 13

Explain monitoring and control with baselines using a flowchart.

Accepted Answer

### **Explain monitoring and control with baselines (exam format)**

**Monitoring and control** tracks project performance and takes corrective action to meet objectives.

**Baselines** used:
- **Scope baseline**
- **Schedule baseline**
- **Cost baseline**

Process:
- measure actual progress/cost
- compare with baseline
- identify variances and root causes
- take corrective/preventive actions

```text
Measure → Compare with baseline → Variance analysis → Corrective action → Update reports
```

Thus monitoring and control keeps the project aligned with plan.

Question 14

Explain change control process with flow and table.

Accepted Answer

### **Explain change control process with flow and table**

**Change control** is a formal process to evaluate and approve/reject changes.

Flow:

```text
Change request → Log → Impact analysis (scope/time/cost/risk)
→ CCB decision (approve/reject/defer) → Update baseline → Implement → Verify → Close
```

| Step | Output |
|---|---|
| Impact analysis | change impact summary |
| CCB decision | approval/rejection |
| Baseline update | revised plan |

This prevents scope creep and ensures controlled changes.

Question 15

Explain project closure and lessons learned with steps/flowchart.

Accepted Answer

### **Explain project closure and lessons learned (with steps)**

**Project closure** formally completes the project.

Steps:
- confirm deliverables and get **acceptance sign-off**
- handover to operations/support
- close contracts and payments
- release resources
- archive documents
- record **lessons learned**

```text
Acceptance → Handover → Close contracts → Release resources → Archive → Lessons learned
```

Lessons learned improve future projects by capturing best practices and mistakes to avoid.

Monitoring, Control and Closure: Change Control, Reporting, Documentation, Lessons Learned and Agile Overview

8 more questions to unlock