Scribd
Upload
10 views7 pages

Highlighting Critical Path in MS Project

The lab report focuses on software project scheduling using Microsoft Project, emphasizing the development of a Work Breakdown Structure (WBS) and the application of the Critical Path Method (CPM). Key tasks included breaking down the project into phases, defining milestones, allocating resources, and visualizing task dependencies through network diagrams and Gantt charts. The exercise enhanced practical knowledge of project planning and highlighted the importance of critical path analysis for timely project completion.

Uploaded by

purposestudy144
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
10 views7 pages

Highlighting Critical Path in MS Project

The lab report focuses on software project scheduling using Microsoft Project, emphasizing the development of a Work Breakdown Structure (WBS) and the application of the Critical Path Method (CPM). Key tasks included breaking down the project into phases, defining milestones, allocating resources, and visualizing task dependencies through network diagrams and Gantt charts. The exercise enhanced practical knowledge of project planning and highlighted the importance of critical path analysis for timely project completion.

Uploaded by

purposestudy144
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Hetauda School of Management & Social Sciences

Hetauda-4, Makawanpur

Lab Report 2
Software Project Scheduling
Software Project management

Submitted By: Submitted To:

Reeya Ramudamu Sameer Gautam

Roll no:15 Lecturer

BCA 7th Semester Department of IT


Lab 2: Software Project Scheduling

Objective

The objective of this lab is to develop detailed project schedules and understand network
models using Microsoft Project. The focus is on creating a Work Breakdown Structure
(WBS) and identifying the Critical Path using the Critical Path Method (CPM).

Task 1:

Develop a Work Breakdown Structure (WBS) for a given software project.

Steps Performed

Step 1: Break Down the Project into Phases and Tasks

Divided the software project into major phases: Analysis, Design, Development, Testing,
Implementation, and Support. Added logical subtasks under each phase.

Step 2: Create Milestones and Define Task Dependencies

Assigned milestones for key phase completions like "Analysis Finished", "Design Finished",
and "Testing Finished". Dependencies were configured for each task to establish logical task
flow.

Step 3: Allocate Resources


Assigned appropriate roles such as Business Analyst, System Analyst, Software Architect,
Software Developer, QA Testers, Deployment Team, and IT Support Team. Each resource
was mapped to corresponding tasks for effective project execution
Task 2:
Apply Critical Path Method (CPM) to determine the critical path for a project.

Step 4: Visualize with Network Diagram

Used the Network Diagram view in MS Project to visualize task flow and dependencies.

Figure 1: NetworkDiagram_Part1
Figure 2: NetworkDiagram_Part 2
Figure 3: NetworkDiagram_Part3

Figure 4: NetworkDiagram_Part4
Step 5: Highlight Critical Path

Created a Gantt Chart to display the project schedule and timeline. Enabled the Critical Tasks
view to highlight tasks that directly affect the project deadline. Using the Format tab in Gantt
Chart view, enabled the “Critical Tasks” checkbox. Tasks on the critical path were
automatically highlighted in red by MS Project.

Figure 5: CriticalPath_Part 1

Figure 6: CriticalPath_Part2
Results and Observations

The lab exercise led to the successful creation of a structured and detailed project schedule.
Using MS Project, all major project phases were clearly defined and organized into a
hierarchical Work Breakdown Structure. Dependencies among tasks were properly
established, and the Gantt Chart provided a visual representation of the entire project
timeline. Additionally, the Critical Path was highlighted, helping identify tasks that are vital
for timely project completion. This visualization improved understanding of project
sequencing and time management.

Conclusion

This lab enhanced practical knowledge of software project scheduling and critical path
analysis using MS Project. By breaking the project into manageable tasks, assigning
resources, and setting logical dependencies, an effective plan was created. Highlighting the
critical path helped identify the sequence of tasks that directly influence the project’s end
date. Overall, the lab provided hands-on experience with tools and techniques that are
essential for effective project planning and execution.

You might also like