Unit 6: Network Diagram View

INT416 — Software Project Management Laboratory 10 min read

I. Orientation

The Network Diagram view in Microsoft Project is a graphical representation of project logic. It displays tasks as nodes or boxes and dependencies as connecting link lines, allowing the scheduler to inspect sequence, branching, convergence, summary structure, and the critical path without relying only on dates in a table.

Node: A box representing one task; its fields may include task name, ID, duration, start, finish, and resource names.
Link line: A connector representing a dependency between predecessor and successor tasks.
Direction: Project flow is normally read from left to right, following arrowheads between nodes.
Dependency logic: Links define when a successor may start or finish relative to its predecessor.
Summary structure: Summary tasks group subtasks and derive their dates from those subtasks.
Formatting convention: Colors, borders, and templates distinguish critical, noncritical, milestone, completed, and summary nodes.
Scheduling principle: Moving a box changes only its visual position; changing its link, duration, or constraint can change the schedule.

II. Network Diagram Fundamentals

A. Understanding The Network Diagram View

The view emphasizes logical relationships among tasks rather than the calendar-oriented bars used in a Gantt Chart.

Purpose: It reveals paths such as Design -> Build -> Test, including parallel work and merge points.
Reading order: A predecessor appears before its successor, while an arrow indicates the direction of dependency.
Critical tasks: Critical nodes commonly receive distinctive formatting because delay on the critical path can delay project completion.
Scope: The view can show tasks, milestones, summary tasks, and dependency lines, but large projects may require filtering or zooming.

B. Examining A Network Diagram

Examining the diagram means tracing links systematically and checking whether the displayed logic matches the intended work sequence.

Start points: Identify nodes with no predecessors; these represent entry points into the displayed network.
Paths: Follow arrows through each branch and note where parallel paths converge on one successor.
End points: Locate tasks with no successors and verify that they represent legitimate project outcomes.
Checks: Look for isolated nodes, unintended loops, excessive constraints, missing links, and implausible dependency types.
Schedule evidence: Compare node dates and slack values to distinguish critical from noncritical paths.

C. Understanding Summary Tasks In Network Design view

Summary tasks represent grouped phases and roll up information from their indented subtasks rather than behaving like ordinary work packages.

Roll-up dates: A summary starts at its earliest subtask start and finishes at its latest subtask finish.
Duration: Summary duration spans the working-time interval covered by its subtasks; it is not normally entered independently.
Links: Linking summary tasks can create broad dependencies affecting every task within a phase, so direct links between detailed tasks are usually clearer.
Display: Summary nodes may be hidden, shown as standard boxes, or given a distinct shape and border through box styles.

D. To change to Network Diagram view

Changing views replaces the current presentation while preserving the underlying project data and schedule.

Modern ribbon: Select View, then choose Network Diagram from the task-view options.
Alternative route: Use the view selector or More Views, select Network Diagram, and choose Apply.
Result: Microsoft Project redraws visible tasks as linked nodes; active filters and outline settings may determine which tasks appear.
Return: Choose Gantt Chart from View when date bars and the task table are needed again.

E. To ZOOM and see the whole of the project

Zooming changes diagram magnification so that more or fewer nodes fit in the workspace without changing project data.

Whole project: Use the Zoom command and select the option that fits the entire project or all displayed boxes.
Detail trade-off: At low magnification, overall paths become visible but field text may be reduced or suppressed.
Navigation: Increase zoom for editing individual nodes; decrease it for spotting disconnected branches and overall flow.
Print preview: Check page breaks after fitting because an on-screen fit does not guarantee a readable printed diagram.

III. Node Editing and Arrangement

A. To open a node for editing

Opening a node provides the complete task dialog for changing scheduling and descriptive information.

Method: Double-click the required node to open Task Information.
Available fields: Depending on the tab, edit name, duration, dates, predecessors, resources, notes, constraints, and custom fields.
Confirmation: Choose OK to apply changes; Project recalculates dependent dates when scheduling data changes.
Caution: A typed start date may introduce a constraint, whereas changing dependency logic often produces a more flexible schedule.

B. To edit a node directly in Network Diagram view

Direct editing is useful for a quick change to a field already displayed inside a node.

Selection: Click the node and then select the displayed field or use the available in-place editing command.
Typical edits: Task names and other enabled fields can be changed without leaving the diagram.
Validation: Press Enter or click outside the field to commit the value and trigger recalculation.
Limitation: Direct editing depends on the Project version and box template; use Task Information when a field is unavailable.

C. To Layout the boxes

Automatic layout arranges nodes and routes link lines according to Project’s current layout rules.

Command: Open the Network Diagram layout command, choose the required options, and apply them to the diagram.
Placement: Project organizes boxes into rows and columns based mainly on dependency order.
Routing: Link lines are redrawn to reduce ambiguity, although dense networks can still contain crossings.
Use case: Run layout after adding, deleting, or substantially relinking tasks to restore a readable flow.

D. To control the layout

Layout controls determine spacing, alignment, link routing, and whether manually positioned boxes remain fixed.

Arrangement: Choose automatic positioning when dependency logic should govern placement.
Spacing: Adjust horizontal and vertical distances to balance readability against the number of visible nodes.
Links: Select an appropriate routing style so arrow direction and intersections remain distinguishable.
Manual option: Enable manual positioning where available when a presentation requires specific grouping.
Risk: Reapplying automatic layout may replace carefully chosen manual positions.

E. To move a node

Moving a node changes the visual arrangement only and does not alter its dates or dependencies.

Procedure: Select the box and drag it to the required location when manual layout is enabled.
Feedback: Link lines stretch or reroute while remaining attached to the same task relationships.
Constraint: Under automatic layout, Project may prevent movement or restore the node’s calculated position.
Good practice: Move nodes to clarify crossings or emphasize branches, not to imply logic that the links do not contain.

F. To copy a node and link to it

Copying creates another task from an existing node’s data, after which a dependency can be established with the copied task.

Copy: Select the source node, use Copy, then Paste to create a separate task record.
Identity: The pasted node receives its own task ID; verify its name, duration, resources, constraints, and notes.
Link: Select predecessor and successor in sequence and use Link Tasks, or draw a link where manual linking is supported.
Caution: Copying may duplicate assignments or unwanted scheduling attributes, so inspect Task Information before relying on it.

IV. Node Content and Appearance

A. To change the content of the nodes

Node content is controlled through data templates that specify which task fields appear and how they are arranged.

Template: Open the box-style or data-template settings and select an existing template or define one.
Fields: Include useful values such as Name, ID, Duration, Start, Finish, Total Slack, and Resource Names.
Association: Assign templates to categories such as critical tasks, milestones, or summary tasks.
Design rule: Show only decision-relevant fields; excessive text enlarges boxes and makes the network harder to scan.

B. To change border color and style

Border formatting visually separates task categories without changing their scheduling behavior.

Access: Open Box Styles or the equivalent formatting dialog for Network Diagram nodes.
Attributes: Choose border color, line pattern, line width, and sometimes background or shape settings.
Category formatting: Apply a style to a defined class, such as critical or completed tasks, for consistent interpretation.
Accessibility: Combine color with line style or shape so meaning is not dependent on color alone.

C. To change the way a summary task is displayed

Summary-task formatting can make project phases visually distinct from executable subtasks.

Target: In Box Styles, select the summary-task category rather than formatting unrelated nodes individually.
Options: Assign a different template, border, background, shape, or display behavior.
Hierarchy: A strong but restrained summary style helps readers distinguish phase roll-ups from tasks where work is performed.
Consistency: Use one summary convention throughout the project so identical visual treatment carries identical meaning.

V. Task Relationships

A. To view the type of relationship

Viewing relationship type identifies the scheduling rule represented by a link line.

Inspection: Double-click a link line, or inspect the predecessor information for the successor task.
Types: FS means Finish-to-Start, SS Start-to-Start, FF Finish-to-Finish, and SF Start-to-Finish.
Lag: A relationship may include delay or overlap, such as 5FS+2d for task ID 5 with two working days of lag.
Interpretation: The line shows connection direction, while the dialog or predecessor field gives the exact type and lag.

B. To change the relationship type

Changing relationship type modifies the rule by which the successor is scheduled relative to its predecessor.

Procedure: Open the link or successor’s predecessor details, choose FS, SS, FF, or SF, set lag if required, and confirm.
Comparison: FS delays successor start until predecessor finish; SS permits both tasks to progress concurrently after their starts are linked.
Recalculation: Project immediately updates affected dates and may alter total slack and the critical path.
Control: Use dependencies to model real work logic; do not select a type merely to force a preferred date.

C. To remove a link line

Removing a line deletes the dependency but leaves both task nodes in the project.

Method: Select or double-click the link and choose the delete-link option, or remove the predecessor entry from Task Information.
Effect: The former successor may move earlier because it is no longer controlled by that predecessor.
Verification: Check whether other predecessors, constraints, or resource limits still govern its date.
Distinction: Deleting a link is different from deleting either connected task.

D. To manually add a link line

A manual link line establishes a dependency by connecting a predecessor node to a successor node.

Drawing: Point to the predecessor, drag from its link area to the intended successor, and release when the target is identified.
Default: Project commonly creates a Finish-to-Start relationship unless another type is selected afterward.
Alternative: Select tasks in predecessor-to-successor order and choose Link Tasks.
Validation: Open the resulting link to verify its direction, type, and lag, especially where nodes are close together.

VI. Final Diagram Organization

A. Reform the layout

Reforming the layout redraws the network after structural or formatting changes so the final diagram remains coherent.

Trigger: Reapply layout after changing links, inserting copied tasks, exposing summary tasks, or changing node templates.
Sequence: Set layout rules, run automatic arrangement, inspect arrow direction, and then make limited manual adjustments.
Quality checks: Confirm that no important node is hidden, link crossings are manageable, labels remain readable, and critical formatting is consistent.
Output: Recheck zoom and page setup before printing or exporting because node dimensions and spacing affect pagination.