Syllabus
Unit 1
Introduction to Software Project Management- Software Projects – ways of categorizing software projects – problems with software projects – Project Life Cycle– Management -Setting objectives –Stakeholders – Project Team- Step-wise
: An overview of project planning -project Evaluation –Selection Of Appropriate Project Objectives- Software Effort Estimation Techniques, Function Point Analysis-Object Point-COCOMO.
Unit 2
Activity planning– project schedules – sequencing and scheduling projects – Network planning model – AON and AOA-identifying critical activities-Crashing And Fast Tracking-,Risk management—Categories , Risk planning, Management and Control – Evaluating risks to the schedule. PERT- Resource Allocation, Monitoring and Tracking – Monitoring and control – allocation – identifying resource requirements – scheduling resources – creating critical paths
- publishing schedule – cost schedules- sequence
Unit 3
Monitoring and control – Visualizing Progress, Earned value analysis, managing people and organizing teams- organizational structures- Planning for small projects. Case Study: PMBOK , Agile Development
Objectives and Outcomes
Course Objectives
- This course describes the key aspects of a software
- It introduces the basic principles of Engineering Software Projects. Most, if not all, students’ complete projects as part of assignments in various courses undertaken. These projects range in size, subject and complexity but there are basic project essentials that need to be understood and practiced for successful team project
- The course provides an understanding of the purpose, methods and benefits of process management by exposing the student to the concepts, practices, processes, tools and techniques used in process management for software
Course Outcomes
CO 1: To understand the basic concepts, terminologies and issues of software project management.
CO 2: To apply appropriate methods and models for the development of solutions.
CO 3: To analyze the cost-benefits of calculations so as to optimize the selection strategy CO 4: To evaluate methods, models and technologies towards achieving project success CO 5: To design and evaluate network planning models with criticality
CO-PO Mapping
PO/PSO |
PO1 |
PO2 |
PO3 |
PO4 |
PO5 |
PO6 |
PO7 |
PO8 |
PO9 |
PO10 |
PO11 |
PO12 |
PSO1 |
PSO2 |
CO |
CO1 |
3 |
1 |
1 |
|
|
|
|
|
|
|
1 |
|
3 |
2 |
CO2 |
3 |
2 |
3 |
|
|
|
|
|
3 |
3 |
|
2 |
3 |
2 |
CO3 |
3 |
2 |
2 |
3 |
2 |
2 |
2 |
2 |
3 |
3 |
2 |
2 |
3 |
2 |
CO4 |
2 |
2 |
2 |
1 |
3 |
2 |
2 |
2 |
3 |
3 |
|
2 |
3 |
2 |
CO5 |
3 |
2 |
3 |
3 |
3 |
2 |
2 |
2 |
3 |
3 |
|
2 |
3 |
2 |
Text Books / References
TEXT BOOK(S)
Mike Cotterell, Bob Hughes. Software Project Management, Fifth Edition, Tata McGraw-Hill; 2012.
REFERENCE(S)
- Roger Pressman. Software Engineering – A Practioner’s Approach, Eighth Edition, Tata McGraw- Hill publishers; 2014.
- Jalote Software Project Management in practice, Second edition, Person Education; 2003.