Software Project Management

UNIT – I: Software Development Organization and Roles

1. Management Spectrum

Management spectrum in software development refers to the range of managerial activities required
to successfully complete a project.

Key Functions:

• Planning → Defining objectives, timelines, and resources

• Organizing → Structuring teams and assigning tasks

• Staffing → Selecting skilled personnel

• Directing → Leading and motivating the team

• Controlling → Monitoring performance and correcting deviations

It ensures effective coordination and goal achievement.

2. Organizational Structure

Organizational structure defines:

• Authority relationships

• Communication channels

• Roles and responsibilities

It helps avoid confusion and improves workflow efficiency.

3. Types of Organizational Structures

Hierarchical Organizational Structure

• Traditional top-down structure

• Clear authority and reporting

• Advantage: strong control

• Disadvantage: slow communication

Flat Organizational Structure

• Few levels of management

• Faster communication and decision-making

 • Encourages teamwork

• Limitation: lack of clear hierarchy

Matrix Organizational Structure

• Dual reporting system

• Employees report to:

o Project Manager

o Functional Manager

• Advantage: efficient resource use

• Limitation: role conflict

Network Organizational Structure

• Uses external teams or outsourcing

• Flexible and scalable

• Focus on core activities

T-form Organization

• Technology-based structure

• Uses IT tools for communication and coordination

• Promotes knowledge sharing

4. Job Roles in Software Development

Role Description

Project Manager Plans, manages, and controls the project

System Analyst Analyses user requirements

Developer Designs and writes code

Tester/QA Ensures software quality

UI/UX Designer Designs user interface

DevOps Engineer Handles deployment and maintenance

 UNIT – II: Overview of Project Management

1. Project Management – Definition

Project management is:

The application of knowledge, skills, tools, and techniques to achieve project objectives within
constraints (time, cost, scope).

2. Factors Influencing Project Management

Project Manager

• Leader and decision-maker

• Responsible for planning and execution

Project Management Activities

• Planning

• Scheduling

• Monitoring

• Controlling

Stakeholders

• Individuals or groups affected by the project

• Examples: clients, users, sponsors

3. Project Communication

• Essential for coordination and success

Types:

• Formal → Reports, emails

• Informal → Meetings, discussions

4. Project Development Phases

1. Initiation

2. Planning

3. Execution

4. Monitoring & Controlling

5. Closure

Known as the Project Life Cycle

 5. Project Charter

• Official document authorizing the project

• Includes:

o Objectives

o Scope

o Stakeholders

o Project Manager details

6. Statement of Work (SoW)

• Detailed description of project work

Includes:

• Deliverables

• Timeline

• Responsibilities

7. Project Management Associations

• PMI (Project Management Institute)

• IPMA

Provide guidelines, standards, and certifications

 UNIT – III: Project Planning, Estimation and Budgeting

1. Tasks in Project Planning

• Define project scope

• Identify tasks and activities

• Allocate resources

• Estimate time and cost

• Risk planning

2. Work Breakdown Structure (WBS)

• Breaks project into smaller manageable tasks

Example:

Software Project
→ Design
→ Coding
→ Testing

Helps in better control and tracking

3. Planning Methods

• Top-Down Approach → Start from overall plan

• Bottom-Up Approach → Start from detailed tasks

4. Development Life Cycle Models

Waterfall Model

• Linear and sequential

• Each phase completed before next

Agile Model

• Iterative and flexible

• Continuous feedback

Spiral Model

• Focus on risk analysis

Iterative Model

• Repeated development cycles

 5. Generic Project Model

Requirement → Design → Development → Testing → Deployment

6. Software Cost Estimation

• Predicts effort, cost, and duration

• Based on:

o Project size

o Complexity

o Team experience

7. COCOMO Model

Effort estimation formula:

𝐸𝑓𝑓𝑜𝑟𝑡 = 𝑎 × (𝐾𝐿𝑂𝐶)𝑏
• KLOC = Thousands of lines of code

• Constants depend on project type

8. Budgeting

• Allocation of financial resources

Includes:

• Labor cost

• Tools and software

• Infrastructure
 UNIT – IV: Project Scheduling, Monitoring and Controlling

1. Scheduling Techniques

PERT (Program Evaluation and Review Technique)

• Uses three time estimates:

o Optimistic

o Most likely

o Pessimistic

• Handles uncertainty

Gantt Chart

• Bar chart representing project schedule

• Shows start and end dates

CPM (Critical Path Method)

• Identifies longest path in project

• Determines minimum completion time

Automated Tools

• MS Project

• JIRA

• Trello

2. Project Monitoring and Controlling

• Ensures project stays on track

Activities:

• Tracking progress

• Comparing actual vs planned

• Taking corrective actions

 3. Project Status Reporting

• Regular progress reports

• Weekly or monthly updates

4. Project Metrics

• Productivity

• Quality

• Cost and schedule performance

5. Earned Value Analysis (EVA)

Used to measure performance:

𝑆𝑉 = 𝐸𝑉 − 𝑃𝑉
𝐶𝑉 = 𝐸𝑉 − 𝐴𝐶
• SV → Schedule variance

• CV → Cost variance

6. Project Communication Plan & Techniques

• Defines how communication will occur

Tools:

• Meetings

• Emails

• Dashboards

7. Steps for Process Improvement

1. Identify problems

2. Analyze causes

3. Implement solutions

4. Monitor results
UNIT – V: Risk Management, Team Development & SQA

1. Concepts of Risk

• Risk = uncertain event affecting project

2. Risk Management Activities

• Risk Identification

• Risk Analysis

• Risk Mitigation

• Risk Monitoring

3. Effective Risk Management

• Early identification

• Proper planning

• Continuous monitoring

4. Risk Categories

• Technical risks

• Financial risks

• Schedule risks

• Operational risks

5. Aids for Risk Identification

• Brainstorming

• Checklists

• SWOT analysis

6. Potential Risk Treatments

• Avoid

• Reduce (Mitigation)

• Transfer

• Accept
 7. Risk Components and Drivers

• Probability of occurrence

• Impact on project

• Risk exposure

8. Risk Prioritization

• Based on:

o Likelihood

o Severity

9. Team Development

• Building effective team

• Leadership and motivation

• Communication and collaboration

10. Conflict Management

Causes:

• Communication gaps

• Resource conflicts

Techniques:

• Negotiation

• Collaboration

• Compromise
 11. Software Quality Assurance (SQA)

• Ensures software meets quality standards

Activities:

• Testing

• Code reviews

• Audits

• Process improvement
CASE STUDIES-:

UNIT – I: Software Development Organization & Roles

Organizational Structure Diagrams

Hierarchical Structure
Clear chain of command (Top → Bottom)

Flat Structure
Fewer levels → faster communication
Matrix Structure

Dual reporting → flexible but complex

 Case Study (Unit I)

Case: Startup vs MNC Structure

• A startup uses a flat structure → quick decisions, innovation

• A large IT company uses a hierarchical structure → better control

Conclusion: Structure depends on organization size and goals

UNIT – II: Overview of Project Management

Project Life Cycle Diagram

 Flow:
Initiation → Planning → Execution → Monitoring → Closure

Case Study (Unit II)

Case: Mobile App Development

• Charter defines app purpose

• SoW defines features (login, payment, UI)

• Stakeholders: client, developers, users

Learning: Clear planning documents avoid confusion

UNIT – III: Project Planning, Estimation & Budgeting

Work Breakdown Structure (WBS)

Break project into smaller tasks
SDLC Models Overview
 Case Study (Unit III)

Case: College Website Project

• WBS:

o Design

o Development

o Testing

• Estimation:

o 2 developers × 30 days

• Budget:

o Salary + tools

Learning: Proper planning reduces delays

COCOMO Model

𝐸𝑓𝑓𝑜𝑟𝑡 = 𝑎 × (𝐾𝐿𝑂𝐶)𝑏
UNIT – IV: Scheduling, Monitoring & Controlling

Gantt Chart
 PERT & CPM Diagram

Case Study (Unit IV)

Case: Software Project Delay

• Gantt chart shows delay in testing

• CPM identifies critical path

• Manager reallocates resources

Learning: Scheduling tools help control delays

Earned Value Analysis

𝑆𝑉 = 𝐸𝑉 − 𝑃𝑉
𝐶𝑉 = 𝐸𝑉 − 𝐴𝐶

UNIT – V: Risk Management, Team Development & SQA

Risk Management Process

Team Development Cycle
 Case Study (Unit V)

Case: Project Risk Handling

• Risk: Developer leaves project

• Action: Backup resource assigned

• Result: Project continues smoothly

Learning: Risk planning avoids project failure

Case Study (Conflict Management)

Case: Team Conflict

• Issue: Disagreement between developers

• Solution: Manager uses negotiation

• Result: Improved collaboration

Case Study (SQA)

Case: Software Bug Issue

• Product released with bugs

• Testing improved (SQA process added)

• Result: Better quality product