Software Project Management

Lecturer (Coordinator):
Ana María Moreno
ammoreno@fi.upm.es
Lecturer:
Tomás San Feliu
tsanfe@fi.upm.es

Semester

First semester

Credits

4 ECTS

Outline

This subject covers the different activities to be performed by a software project manager to successfully drive a software project. For that aim, both workshops and theoretical lectures will be provided.

Syllabus

  1. Introduction to Software Project Management
    1. Psychological Model of Software Engineers
    2. Leadership versus Management
    3. The Basic Functions of Project Management
    4. Developing the Business Case
  2. Developing and Motivating the Project Team
    1. What it Takes for a Team to be Effective
    2. The Basics of Personalities
    3. Motivating Software Engineers
  3. Strategic Approach to Project Planning
    1. The Balanced Scorecard (BSC)
    2. Using SWOT to Develop the BSC
    3. Tracking Progress
  4. Estimating Project Size, Cost, Schedule
  5. Project Risk Management
    1. What Risk is/is not
    2. Strategies for Mitigating Risk
    3. Risk Management Methods
  6. Tracking the Progress of a Software Project
    1. Earned Value Management
    2. Time Value

Recommended reading

Lecture Theatre

A-6305

Tuition language

English

Subject-Specific Competences

Code, description and proficiency level for each subject-specific competence
Code Competence Proficiency Level
CEM4 Analysis and evaluation of several software-based systems construction and management engineering paradigms and approaches A

Learning Outcomes

Code, description and proficiency level for each subject learning outcome
Code Learning Outcome Associated competences Proficiency level
RA-IS-129 Communication Skills. Development and improvement of the ability to share information with others, both oral as written communication. CEM4 A
RA-IS-130 Identify the elements of a risk management plan and its rationale. Create a risk management plan for a project, identifying the risk elements, their impact and corrective actions. CEM4 A
RA-IS-131 Development of a business case for a software project. Creation of a business case for a software project with the proper knowledge and detail level. CEM4 A
RA-IS-132 Development of a project plan at different granularity levels. Identification of the different granularity levels for a project plan, with the corresponding components and structure. CEM3 A
RA-IS-133 Development of a communication plan for a software project. Creation of a communication plan for a software project, indicating communication activities inside the project and with the external stakeholders. CEM3 A

Learning Guide

Learning Guide: Software Project Management