1-4

Course Outline
Title Information Technology Project Management
Code IT-425
Credit Hours 3
Theory/week:
Weight 3 Cr. Hrs.
Contact Hours 3 Hrs.
Lectures: 2
Duration 1.5 Hrs.
Lab/week:
Weight 0 Cr. Hrs.
Contact Hours 0 Hrs.
Labs. 0
Duration 0 Hrs.
Prerequisite
Follow Up
Category
Aims and Objectives The purpose of the ITPM course is to develop the skills of the Project Manager to enable him/her to manage a software project to a successful conclusion. This
course includes the following modules:
• Identify the Process
• Document the Plans
• Track the Progress
• Control the Products
• Cultivate Teamwork.

Learning Outcomes This course will enable students to initiate Software projects, do the project scheduling, plan the resources, carry out the staffing, track the progress, apply software
metrics, manage and motivate the team, and manage the crisis situation.

Syllabus Topics: Definition of an project, Project parameters, Classification of project types, Scope triangle, Software Project risk Vs business value, The S curve, Definition
of software project management, Five phases of project management life cycle: Defining, planning, executing, controlling, closing, Joint Project Planning Sessions
(JPP), Project Overview Statement (POS), Software Project Work Breakdown Structure (WBS), Estimate activity duration: Causes of variation in activity duration,
five methods of Estimating Activity Duration, Elapsed Time Vs Productive time, Project Networks: Critical Path Method (CPM), Build the project network,
Analysis of the project network, Program Evaluation Review Technique (PERT), Activity on Arrow, Activity on Node, GANTT Chart, Using MS-Project to draw
GANTT chart and project Networks, Prepare project Proposal: Purpose of the project proposal, Contents of the project proposal, Format of the Project Proposal,
Software Project Metrics: Measures, Metrics & Indicators, Project indicators, Software measurement: Size Oriented Metrics, Function-Oriented Metrics, Software
Project Estimation: Decomposition Techniques, Software Sizing, Problem-Based Estimation: LOC-Based Estimation, FP-Based Estimation, Process Based
Estimation, Empirical Model Estimation: Cost Estimation, Size Estimation: CoCoMo Model, Staffing and Personnel Planning: Personnel Plan, Team structures:
Democratic decentralized, Controlled Decentralized, Controlled Centralized, Coordination and communication issues, Maslow’s need theory of motivation,
Software Project Team Roles and Responsibilities, Risk Identification, Analysis and Management, SEI risk Model, Configuration Management: Change
Management and Control, baselines, Version Control, IT Project Monitoring and Control: Timesheets, Cost-Milestones-Time charts, Earned Value Analysis for
Project Monitoring and Control. Examples of Earned Value Analysis, Effort Estimation using COCOMO II model: Application Composition, Early Design and
Post Architecture model, Personal Software Process (PSP) Process Script, PSP Project Plan Summary, Using Defect Recording Logs using PSP, Software Project
Quality Assurance Plans, SQA Process
Software Project Quality Standards, Project Documents
 2-4

Text Book/s A. Roger S. Pressman “Software Engineering- A practitioner’s approach”, 5th Ed.
B. Effective Project Management by Robert K Wysocki
C. Integrated Approach to Software Engineering by Punkaj Jalote
D. Introduction to the Personal Software Porcess by Watts. S. Humphrey
E. Information Technology Project Management: Providing measurable organizational value by Jack Marchewka, John Wiley & Sons
Reference Material 1. Ian Sommerville “Software Engineering”, 5th Ed.
2. http://www.columbia.edu/~jm2217/
3. http://www.sei-cmu.edu

Instructional Aids/Resources
 Class facilities to Instructor and students for Lectures per Room
o 1 Network enabled PC
o 1 Multimedia
o 1 Whiteboard
o 1 Rostrum
o 1 Board marker/Month i.e. 4 Week Lectures (eight sessions)
o Max 45 students sitting facility
 Photocopy facility for different Handouts
o Subject description document that includes student version of course outline, prerequisite test and its solution should be distributed in first class.
o Weekend Handout: - A hand out is due after each week at weekend (carrying summary of contents delivered, Terminology, Common Programming
errors, Good programming practice, Performance tips, Software engineering observation, Self review exercise, answer to self review exercise,
programming self checks, case studies, pointers to additional resources and reference materials etc.).
o Testzes and Solution: - Testzes and their standard solution to must be provided to students in handout form after each Test.
o Case Studies and Tutorials: - Description of case study and handout of each tutorial should be provided.

Assessment Criteria Sessional 15% Mid 35% Final 50% Total 100%
Project and Presentations 10
Assignment 05
Paper 35 Paper 50

Recommendations

Framework
Week Lecture Topic Source Recommendations for Learning Activities
(Book-Chapter No. (Mention Assignments, Test, Quizzes, Practical, Case Study,
Section No.) Projects, Lab Work or Reading Assignments)
1 1 Software Project : Definition of a Software Project, Software Project
parameters, Classification of project types, Scope triangle, Project B- Chapter No. 4
risk Vs business value, The S curve
2 Five phases of project management life cycle: Defining, planning,
executing, controlling, closing, B- Chapter No. 5
2 3 Joint Project Planning Sessions (JPP)
4 Scope of the Software Project, Project Overview Statement (POS)  Case Study
with a POS example B- Chapter No. 5
3 5 WBS: Work Breakdown Structure with example of Cofnecco Coffee  Case Study
Shop B- Chapter No. 5
 3-4

6 Estimate activity duration: Causes of variation in activity duration,

five methods of Estimating Activity Duration, Elapsed Time Vs B- Chapter No. 9
Productive time
4 7 Project Networks: Critical Path Method (CPM), Build the project  Case Study
network, Analysis of the project network B- Chapter No. 11  Test 1
8 Network Analysis with Activity on Arrow (AOA) example Handouts  Project Assignment 1
5 9 Network Analysis with Activity on Node (AON) example Handouts  Case Study
10 Critical Path Analysis with Dummy Activities Handouts
6 11 PERT: Program Estimation and Review Technique Handouts
12 GANTT Chart, Using MS-Project to draw GANTT chart and project B- Chapter No. 12  Lab Assignment 1 with Case Study
Networks
7 13 Prepare project Proposal: Purpose of the project proposal, Contents B- Chapter No. 12
of the project proposal, Format of the Project Proposal
14 Software Project Metrics: Measures, Metrics & Indicators, Project A- 4.1, 4.3,4.3.1, 4.3.2
indicators, Software measurement: Size Oriented Metrics, Function-
Oriented Metrics
8 15 Software Project Estimation: Decomposition Techniques, Software A-5.1, 5.2, 5.5, 5.6.2,  Project Phase 2
Sizing, Problem-Based Estimation: LOC-Based Estimation, FP- 5.6.3, 5.6.4, 5.7
Based Estimation, Process Based Estimation, Empirical Model C-3.1, 3.2
Estimation: Cost Estimation, Size Estimation: COCOMO Model
16 Pre Mid Term review  Test 2
9 17 Project Staffing and Personnel Planning: Personnel Plan, Maslow’s C-4.3
need theory of Motivation Handouts
18 Software project Team Types and Team Structures: Chief A-3.1, 3.2, 3.2.1, 3.2.2,
Programmer Team, Democratic Team, Democratic decentralized, 3.2.3
Controlled Decentralized, Controlled Centralized, Coordination and C-3.4
communication issues
10 19 Software Project Team Roles and Responsibilities Handouts 
20 Managing IT project Teams (article by Paul Glenn from MicroSoft Handouts  Case Study
Solution Framework)
11 21 Risk Identification, Analysis and Management, SEI risk Model A-6.1, 6.2, 6.3, 6.3.1,
6.3.2, 6.4, 6.6, 6.8
22 Configuration Management: Change Management and Control, A-9.1, 9.1.2, 9.2, 9.4,  Project Assignment 2
baselines, Version Control 9.5, 9.6, 9.7
12 23 Software Project Monitoring and Control: Timesheets, Cost- C-3.7
Milestones-Time charts.
24 Earned Value Analysis for Project Monitoring and Control. A- 7.8  Case Study
Examples of Earned Value Analysis C-3.7.4  Test 3
Handouts
13 25 Effort Estimation using COCOMO II model: Application A- 5.7.2,  Assignment 2
Composition, Early Design and Post Architecture model. Handouts  Project Assignment 3
26 Personal Software Process (PSP) Process Script, PSP Project Plan D-11.1, 11.2,  Case Study
Summary
14 27 A planning example using PSP Project Plan Summary D-11.3, 11.4, 11.5, 11.6,  Case Study
11.7
28 Defect Recording Logs using PSP D-12.1, 12.2, 12.3, 12.4,  Case Study
12.5, 12.6, 12.7, 12.8,
12.9, 12.10
 4-4

15 29 Software Project Quality Assurance Plans, SQA Process A-8.1, 8.2, 8.3, 8.4, 8.5,
Software Project Quality Standards 8.8, 8.10, 8.11
30 Software Project Quality Standard, Project Documents Handouts
16 31 Final Project Presentations
32 Final Project Presentations

Recommendations:
Following books must be available in the library for the students:
 Text Book
 Effective Project Management by Robert K. Wysoki
 Roger S. Pressman “Software Engineering- A practitioner’s approach”, 5th Ed.
 Integrated Approach to Software Engineering by Punkaj Jalote
 Introduction to the Personal Software Porcess by Watts. S. Humphrey

 Reference Books
 Software Engineering By Ian Sommerville 6th Edition
 Fundamentals of Software Engineering By Carlo Ghezzi
 Software Engineering Principles and Practices By Hans Van Vliet