Project Systemsadvanced

Networks and Activities: Scheduling, Relationships and Milestones

Key takeaway

Use networks to model executable project work with activities, relationships, work centers, external services, dates and milestones, while keeping the WBS as the control hierarchy.

Explanation

📌 KEY POINTS
✅ WBS says WHAT is controlled; the network says HOW and WHEN work executes.
⚠️ Over-constraining a network with too many fixed dates makes scheduling mathematically "correct" but operationally useless.
💡 Milestones can trigger follow-on functions, including billing integration in customer scenarios.

━━━━━━━━━━━━━━━━━━━━
▶ 1. ACTIVITIES

Internal, external, or other execution types depending on configuration
Carry duration, work, work center, cost, and scheduling information

━━━━━━━━━━━━━━━━━━━━
▶ 2. RELATIONSHIPS

Precedence logic — finish-start or overlapping relationships
Enables forward/backward scheduling to calculate earliest and latest dates
Constraints and floats expose schedule risk

━━━━━━━━━━━━━━━━━━━━
▶ 3. MILESTONES

Mark significant project events
Can trigger or influence follow-on functions, including milestone billing integration

━━━━━━━━━━━━━━━━━━━━
▶ 4. WBS ↔ NETWORK LINK

Activities assign to WBS elements so execution cost and schedule roll up to the control structure
WBS = what is controlled; network = how and when work executes

━━━━━━━━━━━━━━━━━━━━
⚠️ 5. THE OVER-CONSTRAINT TRAP

Too many fixed dates = mathematically correct, operationally useless — the system has no flexibility to calculate realistic dates

✅ CHECKPOINT: state the WBS-vs-network distinction in one sentence.

Real project scenario

A project manually fixed start and finish dates on nearly every activity. When one design task slipped, the network could not reschedule logically and downstream dates remained misleading. Removing unnecessary hard constraints restored useful critical-path behavior.

Common mistakes

Using WBS as detailed schedule instead of networks.
Fixing every activity date manually.
Creating relationships that contradict real work sequence.
Ignoring work-center capacity implications.
Creating milestones with no governance.

Best practices

Use relationships to express real precedence.
Minimize hard constraints.
Assign activities to WBS for cost rollup.
Use milestones for genuine business events.
Review critical path/float regularly.

Interview angle

Explain WBS versus network activities, relationship scheduling and milestones.

Practice this lesson

Quick check

1. Scenario — A project manually fixed start and finish dates on nearly every activity. For the lesson "Networks and Activities: Scheduling, Relationships and Milestones", which response shows the strongest architecture and production judgment?

2. A project manager enters a fixed basic start date for a network and the system calculates the earliest possible dates for all subsequent activities based on durations and relationships. Which scheduling scenario does this describe?

3. When defining a relationship between two network activities where the successor activity cannot begin until the predecessor activity is fully completed, which relationship type is used?

Interview questions

1. You are the senior consultant/architect responsible for Networks and Activities: Scheduling, Relationships and Milestones. The project situation is: A project manually fixed start and finish dates on nearly every activity. How would you assess the design, identify the highest-risk failure modes, and define the evidence required before approving it for production?

Answer it in your own words first, then compare.

2. Explain the distinct roles of a Work Breakdown Structure (WBS) and a Network within SAP Project System. How do they interact to facilitate project control and execution?