Software Project Management

Paper Code: 
MCA 524B
Credits: 
04
Periods/week: 
04
Max. Marks: 
100.00
Objective: 
  • To understand the fundamental principles of Software Project management
  • To get familiar with the different methods and techniques used for project management.
12.00
Unit I: 
Project Management:

The management spectrum, the people, the product, the process, the project, the W5HH principle, critical practices Metrics for Process and Project: Metrics in the process and project Domains, software measurements, metrics for software quality, integrating metrics within software process, metrics for small organizations, establishing a software metrics program.

10.00
Unit II: 
Estimation

Observations, Project planning Process, software scope and feasibility, resources, software project estimation, decomposition techniques, empirical estimation models, estimation for object oriented projects, estimation for Agile development and web engineering projects, the make/buy decision.

14.00
Unit III: 
Project Scheduling:

Basic concepts, project scheduling, defining a task set and task network, scheduling, earned value analysis.

Risk Management: Reactive V/S proactive Risk Strategies, software risks, Risk identification, Risk projection, risk refinement, risk mitigation, monitoring and management, the RMMM plan Quality Planning: Quality Concepts, Procedural Approach to Quality Management, Quantitative Approaches to Quality Management, Quantitative Quality Management Planning, Setting the Quality Goal, Estimating Defects for Other Stages, Quality Process Planning, Defect Prevention Planning.

12.00
Unit IV: 
Quality Management

 Quality Concepts, Software Quality assurances, software reviews, formal technical reviews, Formal approaches to SQA, Statistical Software Quality assurances, Change Management: software Configuration Management, The SCM repository, SCM Process, Configuration Management for Web Engineering

12.00
Unit V: 
Project Execution And Closure

Reviews. The Review Process, Planning, Overview and Preparation, Group Review Meeting, Rework and Follow-up, One-Person Review, Guidelines for Reviews in Projects, Data Collection, Analysis and Control Guidelines, Introduction of Reviews and the NAH Syndrome.

Project Monitoring and Control: Project Tracking, Activities Tracking, Defect Tracking, Issues Tracking, Status Reports, Milestone Analysis, Actual Versus Estimated Analysis of Effort and Schedule, Monitoring Quality, Risk-Related Monitoring. Project Closure: Project Closure Analysis, The Role of Closure Analysis, Performing Closure Analysis.

ESSENTIAL READINGS: 
  • Sanjay Mohapatra, “ Software Project Management” , Cengage Learning, 2011
  • Pankaj Jalote, “Software project management in practice” , Addison-Wesley, 2002
REFERENCES: 
  • Roger S. Pressman , “Software Engineering: A practical Approach”, , McGraw-Hill, 1997
  • B. Hughes & M. Cotterell, “Software Project Management”, TMH, 2011
Academic Year: 
2017-18
  • Printer-friendly version