Build the project network

📘 Build the Project Network (Software Project Management)

---

🔹 1. Definition

A Project Network is a graphical representation of project activities and their dependencies, showing the sequence in which tasks must be performed to complete the project.

👉 In simple words: It is a flow diagram of tasks that shows what comes before and after each activity.

---

🔹 2. Purpose of Project Network

• Shows logical order of activities
• Helps in scheduling and planning
• Identifies critical path and delays
• Improves coordination among tasks
• Supports techniques like CPM and PERT

---

🔹 3. Key Components

🔸 1. Activities

• Tasks required to complete the project 👉 Example: Design, Coding, Testing

---

🔸 2. Events (Milestones)

• Start or completion points of activities

---

🔸 3. Dependencies

• Relationship between tasks 👉 Example: Testing cannot start before Coding is finished

---

🔹 4. Types of Project Network Diagrams

---

🔸 1. AON (Activity on Node) ⭐

• Activities are shown in nodes (boxes)
• Arrows show dependencies

👉 Most commonly used in software projects

---

🔸 2. AOA (Activity on Arrow)

• Activities are shown on arrows
• Nodes represent events

---

🔹 5. Steps to Build a Project Network

---

🔸 Step 1: Identify Activities

Break project into tasks (from WBS)

👉 Example:

• A = Requirement Analysis
• B = Design
• C = Coding
• D = Testing

---

🔸 Step 2: Determine Dependencies

Find which task depends on others

👉 Example:

• Design depends on Requirement
• Coding depends on Design
• Testing depends on Coding

---

🔸 Step 3: Arrange Activities in Sequence

Order tasks logically based on dependencies

---

🔸 Step 4: Draw Network Diagram

Represent activities using AON or AOA format

---

🔸 Step 5: Assign Time Estimates

Add duration to each activity

---

🔸 Step 6: Verify Logic

Ensure:

• No missing tasks
• No circular dependencies
• Proper flow from start to end

---

🔹 6. Example Project Network

📌 Activities:

Activity	Description	Depends On
A	Requirement	—
B	Design	A
C	Coding	B
D	Testing	C

---

📊 Network Diagram (AON Style):

A → B → C → D

👉 Flow: Requirement → Design → Coding → Testing

---

🔹 7. Key Rules for Building Network

• Each activity must have clear start and end
• Dependencies must be logical
• No task should be left disconnected
• Use left-to-right flow
• Avoid loops (circular dependencies)

---

🔹 8. Importance of Project Network

• Helps in Critical Path Method (CPM)
• Improves project scheduling accuracy
• Identifies bottlenecks and delays
• Supports resource allocation
• Enhances project visibility

---

🔹 9. Common Mistakes

❌ Missing dependencies ❌ Wrong sequence of tasks ❌ Not defining start/end clearly ❌ Overcomplicated diagrams

---

🔹 10. Short Summary

• A project network shows activities and their dependencies
• Built using steps: identify → sequence → draw → assign time
• Two types: AON (preferred) and AOA
• Used for planning, scheduling, and CPM analysis

---

🔹 11. Quick Exam Answer (2–3 lines)

A project network is a graphical representation of project activities and their dependencies. It is built by identifying tasks, defining their sequence, and drawing a diagram that shows the flow of work from start to finish.

---

🔹 12. Likely Exam Questions

1. Define project network.
2. Explain steps to build a project network.
3. Differentiate between AON and AOA diagrams.
4. What are dependencies in project networks?
5. Why is a project network important?
6. Draw a simple project network for a given example.