Software Project Management

(Dr. Seema Bawa)

Professor, Computer Science and Engineering,
Professor In Charge, Nava Nalanda Central Library
Former Dean (Student Affairs),
Former Head, Computer Science and Engineering Department
Email: seema@thapar.edu, Mobile: 9815604297
PCS111:
Software Project Management

L T P Cr
3 0 2 4.0
 Software Project Management : Syllabus
Course Objectives: Learn and Explore SPM activities
through knowledge of software project management and
project planning.
Introduction to Project Management: The characteristics of
software projects, Objectives of project management: time, cost
and quality, Basics of Project Management, Stakeholders, Stages
of Project, The Feasibility Study, Cost-benefit Analysis, Planning,
Project Execution, Project and Product Life Cycles, Project
Management Knowledge areas, Project Management Tools
&Techniques, Project success factors, role of project manager.
 Software Project Management : Syllabus
Project Management and Planning: System view of project
management, Understanding organizations, stakeholder’s
management, project phases and project’s life cycles.
Introduction to Agile software, Why planning is necessary,
Iterative steps for planning, Project Plan
documentation methods, Software Requirement Specification.
Measurement and Control: Measurements for project monitoring,
what and when to measure,
Plan versus Control, managing the plan, The Deadline Effect.
Reviews, feedback and reporting mechanisms, revisiting the plan.
 Software Project Management : Syllabus
Project Scope Management: Scope Planning & Scope
management plans, Function point calculation, Scope definitions
& project scope statement, Work Breakdown Structure (WBS),
WBS dictionary, scope verification, scope control.
Time Management: Project time management, activities
sequencing, network diagrams, activity
recourse estimation, activity duration estimation, schedule
development, Gantt Charts, Critical
path method, Programme evaluation & review technique (PERT)
and CPM, concept of slack time, schedule control.
 Software Project Management : Syllabus
Project Cost management: Basis principles of cost
management, Cost estimating, type of cost estimate, cost
estimate tools & techniques, COCOMO, Putnam/ SLIM model
Estimating by Analogy, cost budgeting, cost control, earned
value management, project portfolio management
Project Quality Management: Quality Planning, quality
Assurance, Quality control, Tool &techniques for quality control,
Pareto Analysis, Six Sigma, CMM, ISO Standards, Juran
Methodology
 Software Project Management : Syllabus
Project Human Resource Management: Human resource
planning, project organizational charts, responsibility assignment
metrics, acquiring project team, resource assignment, resource
loading, resource levelling, Different team structures developing
project teams.
Project Communication Management: Communication Planning,
Performance reporting, managing stakeholders, improving
project communication Project risk management: Risk
Management planning, common sources of risk, risk
identification, risk register, qualitative risk analysis, using
probability impact matrixes, expert judgement, qualitative risk
 Software Project Management : Syllabus
analysis, decision trees & expected monetary value, simulation,
sensitivity analysis, risk response planning, risk monitoring &
control.
Project procurement management: Procurement management
plans, contract statement of work, planning contracts, requesting
seller responses, selecting sellers, administrating the contract,
closing the contract
Software Configuration Management: Why versions exist, why
retain versions, SCI, Releases vs. version. Change Control and
Management.
 Software Project Management : Syllabus
Laboratory work:
Using Function Point calculation tools for estimation, comparing
with COCOMO estimates, Implementation of various exercises
using PERT, CPM methods, preparing schedule, resource
allocation etc. using MS Project or Fissure. sim or VENSIM can
also be used,
Preparing an RMMM Plan for a case study, Preparing Project
Plan for a Software Project for Lab Project or case study.
Exploring about PMBOK (Project Management Body of
Knowledge) and
 Software Project Management : Syllabus
Laboratory work:
SWEBOK(Software Engineering Body of Knowledge) from
related website, Implementation of
software project management concepts using related tools and
technologies.
…
 Software Project Management : Books

Text Books:
1. Hughes B. and Cotterell M. and Mall R., Software Project
Management, Tata McGraw Hill (2011) 5th Ed.
2. Pressman R., A practitioner’s Guide to Software
Engineering, Tata McGraw Hill (2014) 7th Ed.
Reference Books:
1. Stellman A., Greene J., Applied Software Project
Management, O'Reilly Media, Inc. (2008).
2. Futrell T. R., Shafer F. D. and Shafer I. L., Quality Software
Project Management, Prentice Hall (2002).
 PCS111: Assessment
Terminal Assessment: 64 Marks
•Mid Term Test: 24
•End Semester Test
Internal Assessment: 16 marks
 Quiz1: 8 Marks,
 Quiz2: 8 Marks

Lab Assessment: 24 marks (through)

Projects :
Poster :
Reflective Diary :

Slight changes in assessment units are expected as per

new guidelines of the university...
Lecture-1
Concepts and Overview…
 Topics to be covered
Why Software Project Management is needed?
What constitutes SPM
Characteristics of Software Projects
SPM Mainly includes

– Planning
– Organising
– Control
 Project Management: Need
The “Software crisis” of the 1960s and 1970s was so
called because of a string of high profile software project
failures: over budget, overdue, etc.

The crisis arose in part because the greater power

available in computers meant that larger software
projects were tackled with techniques developed on much
smaller projects.

Techniques were needed for “Software project

Management.
 Project Management: An Introduction

Did you know

Good project management (only) cannot
guarantee success,
but
poor management on significant projects
always leads to failure.
 Project Management: An Introduction

Did you know

Projects advance quickly till they are 90%

complete
and then …
 Project Management: An Introduction

Did you know

Projects advance quickly till they are 90%

complete
and then they remain at 90% forever.
 Project Management: An Introduction

Did you know

Projects advance quickly till they are 90% complete

and then they remain at 90% forever.

…… They are never 100% complete

Why it is so???
Project Management: An Introduction

Did you know

In a software project
Coding is: ? %
of total work needed to be done
 Project Management: An Introduction

Did you know

In a software project
Coding is: %

Coding is only 20%

Other activities (80%) need to be carried out
properly and managed as well.
 A Software Project is different…
Software projects have several properties that make them
very different to other kinds of engineering project.
– The product is intangible.

Its hard to claim a bridge is 90% complete if there is not

90% of the bridge there.
but
It is easy to claim that a software project is 90%
complete, even if there are no visible outcomes.
 A Software Project is different….
- We don’t have much experience.
Software engineering is a new discipline, and so we
simply don’t have much understanding of how to
engineer large scale software projects.
– Large software projects are often “bespoke”.
Most large software systems are one-off, with
experience gained in one project being of little
help in another.
 A Software Project is different
-Here the ‘technology’ changes very quickly.

Most large software projects employ new

technology; for many projects, this is the
raison d’etre..
 Software Project
Characteristics
is logical in nature (not physical),
difficult to measure, visualize
is product of human intelligence,
which is difficult to predict
newer discipline
less standardization of development process

…
 Successful Project

Is the one
that is completed
in time,
within budget,
performs the required function
and also meets all the quality requirements.
 SPM includes

– Estimation
– Planning
– Organising
– Control
– Risk Management
– Software Quality Management
– Configuration Management …
 Why S/w Project Management??

We have observed

Projects advance quickly till they are 90%

complete
and then they remain at 90% forever.

Why???