A SLA REPORT THIRD YEAR COMPUTER TECHNOLOGY

ON
Tracking and Scheduling Techniques

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

GOVERNMENT POLYTECHNIC SAKOLI
SUBJECT : STE(SOFTWARE ENGINEERING)
SEMESTER : FIFTH
SESSION :2025-2026
SUBMMITED BY :

ROLL NO ENROLLMENT NO NAME

52 24310220179 SHUBHAM R. DAKHORE

GUIDED BY:[Link]

GOVERNMENT POLYTECHNIC SAKOLI

2025-2026

1
 MAHARASHTRA STATE

BOARD OF TECHNICAL EDUCATION

Certificate

This is certify to that Mr /Ms …………… ……………………………………

Roll No .……...... of Fifth Semester of Diploma in ………………
……….………………… of institute, …………………………………...........
……………….. Code: ………..) has completed the term work
satisfactorily in course SOFTWARE ENGINEERING (315323) for the
academic year 2025 To 2026 as prescribed in the curriculum.

Place : Sakoli Enrollment No: 24310220176

Date : ……………. Exam Seat No : ……………..

Subject Teacher Head of the Department Principal

Seal of
institute

2
 GOVERNMENT POLYTECHNIC SAKOLI

MAHARASHTRA

SUBMISSION

I am submitting my SLA (Self Assesment Learning) on TRACKING AND SCHEDULING TECHNIQUES

Under the guidance of [Link]
.

[Link] NAME OF STUDENT ROLL NO. SIGN

1 SHUBHAM R DAKHORE 52

H.O.D Signature

Prof. M.A. Rahman (Guide)

3
 DEPARTMENT OF COMPUTER TECHNOLOGY
GOVERNMENT POLYTECHNIC SAKOLI
MAHARASHTRA
ACADEMIC SESSION 2025-2026

ACKNOWLEDGEMENT

It is with deep sense of gratitude, that I take this opportunity to express my sincere thanks to
MR. M. A. RAHMAN the guide of my project, for his continuous expertise and assistance and co-
operation. I also express my gratitude to HOD, Prof. M. A. Rahman Sir for inspiration and
encouragement.

4
 CONTENT TABLE

[Link] Content Page No

1 Introduction 6

2 Project Tracking 7

3 Timeline Charts 8

4 Gantt Charts 9-10

5 Earned Value Analysis (EVA) 11

6 Critical Path Method (CPM) 12

7 Program Evaluation Review Technique (PERT) 13

8 Comparison of CPM and PERT 14

9 Conclusion & References 15

5
 INTRODUCTION

1. In the modern era of software development, tracking and scheduling techniques play a very
important role in ensuring that projects are completed within time, budget, and quality standards.
Software projects often involve multiple tasks, dependencies, and teams working together. Without
proper tracking and scheduling, projects may face delays, cost overruns, and poor resource utilization.
2. Project tracking refers to the continuous monitoring of project progress against the planned schedule
and objectives. It helps project managers to identify whether the project is moving as expected or if
corrective actions are needed. Different tools such as Timeline Charts, Gantt Charts, and Earned
Value Analysis (EVA) are used to measure and visualize project performance.
3. Scheduling techniques, on the other hand, help in planning and organizing project activities. Methods
like the Critical Path Method (CPM) and Program Evaluation and Review Technique (PERT)
are widely used in software project management to determine the project’s duration, identify critical
activities, and manage uncertainties in task completion.
4. This report focuses on the various project tracking and scheduling techniques used in software project
management. Each technique is explained with suitable examples and diagrams to give a clear
understanding of its application. By learning these techniques, software engineers and managers can
improve their decision-making and ensure successful completion of projects within the given time
frame.

6
 Project Tracking

Project Tracking is the process of continuously monitoring and controlling the progress of a project to
ensure it is completed as per the planned schedule, cost, and quality. In software development, projects
involve multiple tasks and dependencies, making tracking essential to avoid delays and overruns.
2.1 Importance of Project Tracking
• Monitor Progress: Helps managers know if tasks are being completed on time.
• Identify Bottlenecks: Early detection of delays allows corrective actions.
• Resource Management: Ensures proper allocation and utilization of resources.
• Cost Control: Helps in keeping the project within budget.
• Quality Assurance: Ensures project deliverables meet the required standards.
2.2 Techniques Used for Project Tracking
1. Timeline Charts: Simple visual representation of milestones and key events along a time axis.
2. Gantt Charts: Shows tasks as horizontal bars along a schedule; highlights dependencies and
overlaps.
3. Earned Value Analysis (EVA): Compares planned work, actual progress, and cost to measure
performance.
By using these techniques, project managers can maintain control over the project, make informed
decisions, and e

7
 Timeline Charts

3.1 Concept of Timeline Charts

A Timeline Chart is a simple graphical representation that shows key events, milestones, or tasks along a
horizontal time axis. It is widely used in project management to provide a quick overview of project
progress and major deadlines. Timeline charts are easy to understand and help stakeholders visualize the
sequence and duration of activities.
Features of Timeline Charts:
• Displays project milestones in chronological order.
• Shows start and end dates for each milestone.
• Helps in tracking the overall progress of the project.
• Useful for presentations and stakeholder updates.

3.2 Example of a Timeline Chart

Suppose a software project has the following milestones:
Milestone Day
Project Start 0
Requirements Complete 10
Prototype Ready 25
Final Delivery 40
Explanation:
• The project starts on Day 0.
• Requirements are completed by Day 10.
• Prototype is ready by Day 25.
• Final product delivery is scheduled on Day 40.
This can be visualized as a simple timeline:
0 10 25 40
|-------|--------|--------|
Start Req Done Prototype Final Delivery
Advantages of Timeline Charts:
• Provides a clear visual overview of milestones.
• Helps track progress at a glance.
• Simple and easy to communicate with team and management.
8
 4. Gantt Charts

4.1 Definition and Importance

A Gantt Chart is a type of bar chart that represents a project schedule. Each task is shown as a horizontal
bar, with the length of the bar representing the task duration. Gantt Charts are widely used in project
management to plan, coordinate, and track specific tasks in a project.
Importance of Gantt Charts:
• Visual representation of tasks and their durations.
• Shows task dependencies (which task depends on which).
• Helps in identifying overlapping tasks and parallel activities.
• Useful for monitoring progress and adjusting schedules if needed.

4.2 Example of a Gantt Chart

Project Tasks and Schedule:
Task Duration (days) Start Finish Predecessor
A 4 0 4 —
B 6 4 10 A
C 5 4 9 A
D 3 10 13 B
E 4 9 13 C
Explanation:
• Task A starts at day 0 and finishes at day 4.
• Tasks B and C start after A is completed.
• Task D starts after B, and task E starts after C.
• Tasks B and C run in parallel, and tasks D and E overlap partially.

9
Simple Visual Representation:

Advantages of Gantt Charts:

• Clear visual of all project tasks and their durations.
• Easy identification of parallel tasks and dependencies.
• Useful for team communication and progress tracking.

10
 Earned Value Analysis (EVA)
5.1 Definition
Earned Value Analysis (EVA) is a project tracking technique used to measure project performance in
terms of cost and schedule. It compares the planned progress with the actual progress and tells whether the
project is ahead/behind schedule or under/over budget.

5.2 Key Terms

• Planned Value (PV): Budgeted cost of the work scheduled.
• Earned Value (EV): Budgeted cost of the work actually performed.
• Actual Cost (AC): Actual cost incurred for the work performed.
From these, we calculate:
• Schedule Variance (SV) = EV – PV
• Cost Variance (CV) = EV – AC
• Schedule Performance Index (SPI) = EV ÷ PV
• Cost Performance Index (CPI) = EV ÷ AC

5.3 Numerical Example

Suppose a software project has a total budget of ₹1,00,000 and is planned to be completed in 10 weeks.
After 5 weeks, the following data is available:
• Planned work (PV) = 50% of project = ₹50,000
• Earned work completed (EV) = 40% of project = ₹40,000
• Actual cost incurred (AC) = ₹60,000
Step 1 – Calculate Variances
• SV = EV – PV = 40,000 – 50,000 = –₹10,000 (Project is behind schedule)
• CV = EV – AC = 40,000 – 60,000 = –₹20,000 (Project is over budget)
Step 2 – Calculate Performance Indexes
• SPI = EV ÷ PV = 40,000 ÷ 50,000 = 0.8 (<1 means delay)
• CPI = EV ÷ AC = 40,000 ÷ 60,000 = 0.67 (<1 means cost overrun)

5.4 Interpretation
• The project has completed less work than planned in 5 weeks.
• The project has spent more money than budgeted for the work completed.
• Corrective measures are required to bring the project back on track.
.
11
 Critical Path Method (CPM)

6.1 Introduction
The Critical Path Method (CPM) is a scheduling technique used to identify the longest path of
dependent tasks in a project. The longest path is called the critical path, and it decides the minimum
project completion time. Any delay in critical activities delays the whole project.

6.2 Example
Activity Predecessor Duration (days)
A — 3
B A 2
C A 4
D B, C 2
E C 3
Paths:
• A → B → D = 3 + 2 + 2 = 7 days
• A → C → E = 3 + 4 + 3 = 10 days (Critical Path)
Result:
• Critical Path = A → C → E
• Minimum Project Duration = 10 days

6.3 Key Point

• CPM gives a deterministic schedule (fixed times).
• Helps managers identify critical tasks and focus on them.

12
 Program Evaluation and Review Technique (PERT)

7.1 Introduction
The Program Evaluation and Review Technique (PERT) is a project scheduling method that considers
uncertainty in task durations. Unlike CPM, which uses fixed times, PERT uses three time estimates:
• Optimistic (O) – Best case time
• Most Likely (M) – Normal expected time
• Pessimistic (P) – Worst case time
The expected time is calculated as:
TE=O+4M+P6TE = \frac{O + 4M + P}{6}TE=6O+4M+P

7.2 Example
For a small project:
Activity Predecessor O M P TE
A — 2 4 6 4.0
B A 1 2 3 2.0
C A 2 3 8 3.7
D B, C 3 5 7 5.0
Possible Paths:
• A → B → D = 11 days
• A → C → D = 12.7 days (Critical Path)
So, project expected duration = 12.7 days.

7.3 Key Point

• PERT shows both expected duration and uncertainty.
• More useful than CPM when project tasks have uncertain times.

13
 Comparison of CPM and PERT

Feature CPM (Critical Path Method) PERT (Program Evaluation and

Review Technique)
Type of Uses deterministic (fixed) time values Uses probabilistic (O, M, P) time
Estimates estimates
Best Use Projects with well-known activities & Projects with uncertainty in activity
durations (e.g., construction, manufacturing) times (e.g., research, software R&D)
Focus Focuses on time-cost trade-off Focuses on time estimation & risk
analysis
Critical Path Clearly defined, determines exact project Gives expected project duration with
duration risk factor
Application Suitable for repetitive projects Suitable for non-repetitive, innovative
projects

Key Point:
• CPM is useful when activities are predictable and stable.
• PERT is useful when uncertainty and risk need to be considered.

14
 10. Conclusion
Project tracking and scheduling techniques are essential tools in software development. Techniques like
Timeline Charts, Gantt Charts, Earned Value Analysis (EVA), Critical Path Method (CPM), and PERT
help managers and developers monitor progress, control costs, allocate resources, and manage risks.

By applying these techniques:

• Projects can be completed on time and within budget.

• Critical tasks are easily identified, and delays can be prevented.

• Uncertainty in task durations can be analyzed and mitigated (using PERT).

• Stakeholders and teams can clearly understand the project status.

In short, mastering tracking and scheduling ensures successful project delivery, better planning, and
improved decision-making in the software development life cycle.

11. References

1. Sommerville, I. (2016). Software Engineering, 10th Edition. Pearson.

2. Project Management Institute (PMI). A Guide to the Project Management Body of Knowledge
(PMBOK Guide), 7th Edition.
3. TutorialsPoint. Project Management Concepts and Tools.
4. GeeksforGeeks. Project Scheduling Techniques – CPM & PERT.
5. Online resources: [Link] [Link]

15