---
description: Project Scope Definition — mendefinisikan In Scope dan Out of Scope secara eksplisit untuk mencegah scope creep
---

# /define_scope - In/Out Scope Definition

**Sumber:** TOPIC_004 > 05_project_blueprint.md (§5.3 Project Scope Statement)

---

## 📋 Kapan Menggunakan Workflow Ini

- Bagian dari **Project Charter** creation
- Saat perlu **manage expectations** stakeholders
- Untuk **prevent scope creep**
- Saat terjadi **scope change request**

---

## 🎯 Scope Statement Structure

```
+-----------------------------------------------------------------+
|                    PROJECT SCOPE STATEMENT                       |
+-----------------------------------------------------------------|
|                                                                  |
|  +---------------------------------------------------------+     |
|  |                    IN SCOPE ✓                           |     |
|  |                                                         |     |
|  |  Features, functionalities, deliverables that          |     |
|  |  WILL be included in this project                       |     |
|  +---------------------------------------------------------+     |
|                                                                  |
|  +---------------------------------------------------------+     |
|  |                   OUT OF SCOPE ✗                        |     |
|  |                                                         |     |
|  |  Features, functionalities, deliverables that          |     |
|  |  will NOT be included (may be future phases)           |     |
|  +---------------------------------------------------------+     |
|                                                                  |
|  WHY DEFINE OUT OF SCOPE?                                        |
|  • Prevents scope creep                                          |
|  • Manages stakeholder expectations                              |
|  • Provides clear project boundaries                             |
|  • Enables focused development                                   |
|                                                                  |
+-----------------------------------------------------------------+
```

---

## 🛠️ STEP-BY-STEP WORKFLOW

### STEP 1: Project Description (5 min)

**Brief overview of what the project will deliver:**

---

### STEP 2: Define IN SCOPE (15 min)

**What WILL be included:**

**2.1 Core Features:**

- [ ] Feature 1: \_\_\_
- [ ] Feature 2: \_\_\_
- [ ] Feature 3: \_\_\_

**2.2 Platforms:**

- [ ] Web Application
- [ ] API
- [ ] Admin Portal

**2.3 Integrations:**

- [ ] Payment: \_\_\_
- [ ] Auth: \_\_\_

**2.4 Deliverables:**

- [ ] Working application
- [ ] Source code
- [ ] Documentation
- [ ] Deployment to production

**2.5 Support:**

- [ ] 30-day bug fix warranty
- [ ] Handover training

---

### STEP 3: Define OUT OF SCOPE (15 min)

**What will NOT be included:**

**3.1 Features NOT Included:**

- ✗ **\_** (planned for Phase 2)
- ✗ **\_**
- ✗ **\_**

**3.2 Platforms NOT Included:**

- ✗ Mobile application (future phase)

**3.3 Integrations NOT Included:**

- ✗ Legacy system integration

**3.4 Support NOT Included:**

- ✗ Ongoing maintenance (separate contract)

---

## 💡 In Scope vs Out of Scope Examples

| Category        | ✓ In Scope                   | ✗ Out of Scope         |
| --------------- | ---------------------------- | ---------------------- |
| **Platform**    | Web application              | Mobile apps (Phase 2)  |
| **Features**    | User registration, Dashboard | AI recommendations     |
| **Integration** | Payment gateway              | ERP integration        |
| **Users**       | Customer portal              | Admin portal (Phase 2) |
| **Data**        | New data entry               | Legacy data migration  |
| **Support**     | 30-day warranty              | Ongoing maintenance    |
| **Docs**        | User manual                  | Developer training     |

---

## 📋 SCOPE STATEMENT TEMPLATE

```markdown
## PROJECT SCOPE STATEMENT

### Project Name: \***\*\_\_\*\***

### Version: **\_ | Date: **\_\_\_\_\*\*\*\*

---

## 1. PROJECT DESCRIPTION

[Brief overview of what the project will deliver]

---

## 2. IN SCOPE ✓

### 2.1 Core Features

- [ ] Feature 1: \_\_\_
- [ ] Feature 2: \_\_\_
- [ ] Feature 3: \_\_\_

### 2.2 Platforms

- [ ] Web Application
- [ ] API

### 2.3 Integrations

- [ ] Payment: \_\_\_
- [ ] Auth: \_\_\_

### 2.4 Deliverables

- [ ] Working application
- [ ] Source code
- [ ] Documentation

### 2.5 Support

- [ ] 30-day bug fix warranty

---

## 3. OUT OF SCOPE ✗

### 3.1 Features NOT Included

- ✗ \_\_\_ (Phase 2)
- ✗ \_\_\_
- ✗ \_\_\_

### 3.2 Platforms NOT Included

- ✗ Mobile application

### 3.3 Support NOT Included

- ✗ Ongoing maintenance

---

## 4. ASSUMPTIONS

-

## 5. CONSTRAINTS

- ***

  **Approved by:** \***\*\_\_\*\*** Date: \***\*\_\_\*\***
```

---

## 📝 Output File

**Setelah workflow selesai, AI WAJIB generate file markdown:**

**Path:** `AI-Agent/Output/Planning/[ProjectName]/10_scope_statement.md`

**Template Output:**

```markdown
# [Project Name] - Scope Statement

**Version:** 1.0
**Date:** [YYYY-MM-DD]
**Approved By:** [Name]

---

## Project Description

[Brief overview of what the project will deliver]

---

## IN SCOPE ✓

### Core Features

- [ ] [Feature 1]: [Description]
- [ ] [Feature 2]: [Description]
- [ ] [Feature 3]: [Description]

### Platforms

- [ ] [Platform 1]
- [ ] [Platform 2]

### Integrations

- [ ] [Integration 1]
- [ ] [Integration 2]

### Deliverables

- [ ] Working application
- [ ] Source code
- [ ] Documentation
- [ ] Deployment

### Support

- [ ] [Support item]

---

## OUT OF SCOPE ✗

### Features NOT Included

- ✗ [Feature 1] — [Reason/Phase]
- ✗ [Feature 2] — [Reason/Phase]
- ✗ [Feature 3] — [Reason/Phase]

### Platforms NOT Included

- ✗ [Platform] — [Reason/Phase]

### Integrations NOT Included

- ✗ [Integration] — [Reason/Phase]

### Support NOT Included

- ✗ [Support item] — [Reason]

---

## Assumptions

1. [Assumption 1]
2. [Assumption 2]
3. [Assumption 3]

---

## Constraints

1. [Constraint 1]
2. [Constraint 2]
3. [Constraint 3]

---

## Scope Change Process

Any change to this scope must be:

1. Documented in writing
2. Reviewed for impact (time, cost, quality)
3. Approved by [Role]

---

## Approval

**Approved by:** [Name] | **Date:** [YYYY-MM-DD]

---

## Next Steps

- [ ] Proceed to /risk_register (identify project risks)
- [ ] Complete /raci_matrix (if team project)
- [ ] **Final:** Run /compile_blueprint (compile all -> 1 master document)
```

---

## 📚 Referensi

- Smartsheet, ProjectManager.com
- TOPIC_004/05_project_blueprint.md (Lines 140-250)