MODULE 4 : SOFTWARE PROJECT MANAGEMENT

Introduction to Software Project Management

Software Project Management is one of the most important areas of Software Engineering.

A software project does not become successful only because of good coding.

A successful software project also requires:

• Proper planning
• Time management
• Cost control
• Team management
• Risk handling
• Resource management

Software Project Management helps organizations:

• Complete projects on time

• Complete projects within budget
• Maintain software quality
• Manage teams properly
• Reduce project risks

Why Software Project Management is

Important?
Suppose a company starts developing a Banking Application.

Without project management:

• Developers may not know deadlines

• Budget may increase
• Team confusion may occur
• Features may remain incomplete
• Testing may become weak

With proper project management:

• Tasks are planned properly

• Resources are controlled
• Risks are managed
• Quality improves
• Customer satisfaction increases

1
Real-Life Example
Suppose a company wants to build a Food Delivery App.

The project manager must decide:

• How many developers are needed?

• How much time is required?
• What will be the total cost?
• What risks may occur?
• Which modules should be completed first?

This complete process is called Software Project Management.

============================================================

1. OVERVIEW OF PROJECT MANAGER

RESPONSIBILITIES
============================================================

Who is a Project Manager?

A Project Manager is the person responsible for:

• Planning the project

• Managing the team
• Controlling cost and schedule
• Handling risks
• Communicating with clients

The project manager acts as the leader of the software project.

Main Responsibilities of Project Manager

1. Project Planning
The project manager prepares:

• Project schedule
• Budget
• Resource allocation
• Development strategy

2
2. Team Management
The project manager:

• Assigns tasks
• Coordinates developers
• Resolves conflicts
• Motivates team members

3. Risk Management
The manager identifies possible risks such as:

• Budget increase
• Delay
• Technical failure
• Security issues

Then plans solutions.

4. Communication Management
The project manager communicates with:

• Clients
• Developers
• Testers
• Stakeholders

5. Quality Management
The manager ensures:

• Proper testing
• Quality standards
• Requirement satisfaction

3
6. Cost Management
The project manager controls:

• Budget
• Expenses
• Resource usage

7. Scheduling
The manager decides:

• Deadlines
• Milestones
• Development phases

8. Requirement Understanding
The project manager must understand:

• User requirements
• Business goals
• Technical needs

Skills Required for Project Manager

A good project manager should have:

Technical Skills
Understanding of software systems.

Communication Skills
Ability to interact with teams and clients.

Leadership Skills
Ability to manage and motivate people.

4
Decision-Making Skills
Ability to make fast and correct decisions.

Problem-Solving Skills
Ability to handle project problems.

Example of Project Manager Responsibilities

Suppose a company is developing an E-Commerce Website.

The project manager:

• Creates project plan

• Assigns frontend work
• Assigns backend work
• Tracks progress
• Conducts meetings
• Handles delays
• Reports to client

============================================================

2. PROJECT PLANNING
============================================================

Definition
Project Planning is the process of deciding:

• What work will be done

• Who will do it
• When it will be completed
• How much it will cost

Project planning is the foundation of software project management.

Importance of Project Planning

Good planning helps:

• Reduce confusion

5
 • Improve coordination
• Reduce project failure
• Improve time management
• Improve cost control

Main Activities in Project Planning

1. Scope Definition
Defines:

• Project boundaries
• Features
• Objectives

2. Resource Planning
Determines:

• Number of developers
• Hardware needs
• Software tools

3. Time Planning
Defines:

• Deadlines
• Milestones
• Development phases

4. Cost Planning
Estimates:

• Development cost
• Resource cost
• Maintenance cost

6
5. Risk Planning
Identifies:

• Technical risks
• Financial risks
• Schedule risks

6. Quality Planning
Defines:

• Testing methods
• Quality standards
• Review process

Project Planning Flow

Requirement Analysis → Estimation → Scheduling → Resource Allocation → Risk Planning →
Development

============================================================

3. SOFTWARE MEASUREMENT AND METRICS

============================================================

Definition
Software Metrics are numerical measurements used to measure:

• Software size
• Complexity
• Quality
• Performance
• Productivity

Metrics help managers make better decisions.

7
Importance of Software Metrics
Metrics help:

• Estimate project cost

• Estimate development time
• Measure productivity
• Measure software quality
• Compare projects

============================================================

4. LINE OF CODE (LOC)

============================================================

Definition
LOC measures software size based on:

• Number of lines of source code

Formula
LOC = Total Number of Source Code Lines

Example
Suppose:

Login Module = 500 lines Payment Module = 700 lines Report Module = 300 lines

Total LOC = 1500 lines

Advantages of LOC
• Simple measurement
• Easy calculation
• Useful for productivity measurement

8
Disadvantages of LOC
• Depends on programming language
• Large code does not always mean better software
• Ignores software quality

Real-Life Problem with LOC

Two developers create the same feature.

Developer A writes 100 lines. Developer B writes 40 efficient lines.

LOC suggests Developer A did more work, but Developer B may have written better code.

Therefore, LOC has limitations.

============================================================

5. FUNCTION POINT (FP) BASED MEASURES

============================================================

Introduction
Function Point measures software size based on:

• Functionality provided to users

Unlike LOC, FP does not depend on programming language.

Main Components of Function Point

1. Inputs
Data entered into the system.

Example:

• Login form
• Registration form

9
2. Outputs
Data produced by the system.

Example:

• Reports
• Invoices

3. Inquiries
User requests information.

Example:

• Search operation

4. Files
Logical data storage.

Example:

• Customer database

5. External Interfaces
Connection with external systems.

Example:

• Payment gateway

Formula
FP = Count Total × Complexity Adjustment Factor

10
Example
Suppose: Inputs = 10 Outputs = 5 Files = 4

After adjustment: FP = 120

Advantages of FP
• Language independent
• Better productivity measurement
• Better estimation accuracy

Disadvantages of FP
• Complex calculation
• Requires expert analysis

============================================================

6. VARIOUS SIZE ORIENTED MEASURES

============================================================

Introduction
Size-oriented measures estimate software based on:

• Code size
• Complexity
• Effort

One important measure is: Halstead’s Software Science.

============================================================

7. HALSTEAD'S SOFTWARE SCIENCE

============================================================

11
Introduction
Maurice Halstead introduced software measurement formulas based on:

• Operators
• Operands

The theory measures:

• Program complexity
• Development effort
• Program difficulty

Basic Terms

Operators
Symbols or keywords performing operations.

Examples:

•+
•-
•*
• if
• while

Operands
Variables and constants.

Examples:

•x
•y
• total

Main Halstead Metrics

1. Program Length
Measures total operators and operands.

12
Formula: N = N1 + N2

Where: N1 = Total operators N2 = Total operands

2. Program Vocabulary
Formula: n = n1 + n2

Where: n1 = Unique operators n2 = Unique operands

3. Program Volume
Measures program size.

Formula: V = N log2 n

4. Difficulty
Measures program difficulty.

Formula: D = (n1/2) × (N2/n2)

5. Effort
Measures development effort.

Formula: E = D × V

Advantages of Halstead Metrics

• Measures complexity mathematically
• Useful for effort estimation
• Useful for maintenance analysis

Disadvantages
• Complex formulas
• Ignores logical complexity

13
 • Difficult for large systems

============================================================

8. PROJECT SIZE ESTIMATION METRICS

============================================================

Definition
Project Size Estimation predicts:

• Software size
• Required effort
• Development time

Importance
Size estimation helps:

• Budget estimation
• Staffing estimation
• Scheduling

Common Metrics
• LOC
• Function Point
• Halstead Metrics

============================================================

9. PROJECT ESTIMATION TECHNIQUES

============================================================

Definition
Project estimation predicts:

• Cost
• Time
• Effort

14
 • Resources

before development starts.

Importance
Good estimation helps:

• Avoid delays
• Avoid budget overrun
• Improve planning

Main Estimation Techniques

1. Expert Judgment
Experienced experts estimate project values.

2. Estimation by Analogy
Uses data from similar previous projects.

Example
If a previous banking app took:

• 6 months
• 10 developers

A similar project may require similar effort.

3. Algorithmic Estimation
Uses mathematical formulas.

Example: COCOMO Model

============================================================

15
10. COCOMO MODEL
============================================================

Introduction
COCOMO stands for: Constructive Cost Model

It was developed by: Barry Boehm

COCOMO estimates:

• Effort
• Cost
• Development time

based on software size.

Basic Formula
Effort = a × (KLOC)^b

Where: KLOC = Thousands of Lines of Code

a and b are constants.

Types of COCOMO Models

1. Basic COCOMO
Uses only software size.

2. Intermediate COCOMO
Uses:

• Software size
• Cost drivers

16
3. Detailed COCOMO
Uses:

• Detailed phase analysis

• Individual project factors

Categories of Software Projects

1. Organic Projects
Small and simple projects.

Example:

• Student management system

2. Semi-Detached Projects
Medium complexity projects.

Example:

• Compiler systems

3. Embedded Projects
Very complex projects.

Example:

• Aircraft control system

• Banking network systems

Example of Basic COCOMO

Suppose: KLOC = 50

Formula: Effort = 2.4 × (50)^1.05

17
The result gives estimated person-month effort.

Advantages of COCOMO
• Scientific estimation
• Better planning
• Widely used

Disadvantages
• Depends on accurate size estimation
• Difficult for changing requirements

============================================================

11. STAFFING LEVEL ESTIMATION

============================================================

Definition
Staffing estimation determines:

• Number of developers needed

• Team structure
• Resource allocation

Factors Affecting Staffing

• Project size
• Complexity
• Development time
• Budget
• Technology

Example
Small Website:

• 3 developers

18
Large Banking System:

• 50 developers
• Multiple teams

Problems with Excessive Staffing

Adding too many people may:

• Increase communication problems

• Reduce efficiency
• Increase confusion

This idea relates to: Brooks’ Law

Brooks’ Law
"Adding more people to a late project makes it later."

Reason: New members need:

• Training
• Coordination
• Communication

============================================================

12. SCHEDULING
============================================================

Definition
Scheduling determines:

• Task sequence
• Deadlines
• Project timeline

Importance of Scheduling
Scheduling helps:

• Manage time

19
 • Track progress
• Meet deadlines

Main Scheduling Techniques

1. Gantt Chart
A graphical chart showing:

• Tasks
• Duration
• Timeline

Example
Task Week Requirement 1-2 Design 3-4 Coding 5-8 Testing 9-10

2. PERT Chart
PERT stands for: Program Evaluation and Review Technique

It represents:

• Activities
• Dependencies
• Critical path

Advantages of Scheduling
• Better time management
• Better coordination
• Improved tracking

============================================================

13. ORGANIZATION AND TEAM STRUCTURES

============================================================

20
Introduction
Software projects require proper team organization.

A good team structure improves:

• Coordination
• Communication
• Productivity

Types of Team Structures

1. Democratic Team Structure

All members participate equally.

Features:

• Open communication
• Shared decisions

Advantages
• Better creativity
• Better teamwork

Disadvantages
• Slow decision-making

2. Controlled Centralized Structure

One leader controls the project.

Features:

• Strong leadership
• Centralized decisions

21
Advantages
• Fast decisions
• Better control

Disadvantages
• Lower creativity

3. Controlled Decentralized Structure

Combines:

• Team communication
• Leadership control

Advantages
• Balanced coordination
• Better communication

============================================================

14. STAFFING
============================================================

Definition
Staffing means:

• Recruiting
• Assigning
• Managing project personnel

Staffing Activities
• Recruitment
• Training
• Task assignment

22
 • Performance evaluation

Important Factors
• Technical skills
• Experience
• Team compatibility
• Communication ability

============================================================

15. RISK MANAGEMENT

============================================================

Introduction
Risk Management is the process of:

• Identifying risks
• Analyzing risks
• Reducing risks

Software projects always contain uncertainty.

What is Risk?
A risk is a possible future problem that may affect:

• Cost
• Time
• Quality
• Performance

Types of Risks

1. Technical Risks
Examples:

• Technology failure
• Integration problems

23
 • Security vulnerabilities

2. Project Risks
Examples:

• Delay
• Budget increase
• Resource shortage

3. Business Risks
Examples:

• Market competition
• Customer dissatisfaction
• Financial loss

============================================================

RISK MANAGEMENT PROCESS

============================================================

Step 1: Risk Identification

Possible risks are identified.

Step 2: Risk Analysis

The impact and probability of risks are analyzed.

Step 3: Risk Prioritization

Important risks receive higher priority.

24
Step 4: Risk Planning
Solutions are prepared.

Step 5: Risk Monitoring

Risks are continuously monitored.

============================================================

EXAMPLE OF RISK MANAGEMENT

============================================================

Suppose a company is creating an Online Banking System.

Possible risks:

• Server failure
• Data theft
• Project delay
• Budget overrun

Solutions:

• Backup servers
• Encryption
• Additional testing
• Better scheduling

============================================================

RELATION WITH PREVIOUS MODULES

============================================================

Relation with Requirement Analysis

Poor requirements create:

• Wrong estimation
• Wrong planning
• Increased project risk

Therefore, Requirement Engineering directly affects Project Management.

25
Relation with Software Design
Poor design increases:

• Development cost
• Complexity
• Maintenance effort

Good software design helps:

• Better scheduling
• Better estimation
• Reduced risk

============================================================

HISTORY AND EVOLUTION OF SOFTWARE

PROJECT MANAGEMENT
============================================================

Early Software Development Problems

During the 1960s and 1970s:

• Software projects frequently failed

• Budgets increased
• Deadlines were missed
• Maintenance became difficult

This situation created: Software Crisis

Solution
Software Engineering introduced:

• SDLC models
• Requirement Engineering
• Software Design
• Project Management
• Risk Management

to solve these problems.

26
Modern Software Project Management
Today project management uses:

• Agile methods
• Automated tracking tools
• AI-based estimation
• Cloud collaboration
• DevOps practices

============================================================

FINAL CONCLUSION
============================================================

Software Project Management is essential for successful software development.

It helps organizations:

• Complete projects on time

• Reduce development cost
• Improve quality
• Manage risks
• Coordinate teams effectively

Modern project management combines:

• Planning
• Estimation
• Scheduling
• Staffing
• Risk Management

for building efficient and reliable software systems.

27