Informatics Project Management

The subject "IT Project Management" will try to make students aware of the essential processes for managing projects from the moment they are conceived as an idea, with the appearance of one or more clients, to the closure of the project with the delivery of its results. Although the vision taught will follow the contents of the PMBOK of the PMI, which reflects a transversal vision of project management to all engineering, the course will focus on software projects. However, the aim of the subject is for the student to know the process areas related to project management and to be able to understand their impact in order to manage and balance them on a specific project.

Topic 01. Introduction to Project Management
- Concept of project
- Project management
- The project life cycle
Topic 02. Scope Management.
- Concepts and project initiation.
- Scope management
- The requirements
Theme 03. Stakeholder and Communications Management
- Stakeholder identification, planning
- Stakeholder management and monitoring
- Information and Communications Planning, Management and Monitoring
Topic 04. Estimation
- Introduction to Estimation
- Estimation methods
- Complexity factors
- An example
Topic 05. Time management. Planning
- Scope Review. The WBS
- Plan schedule management
- Defining, sequencing and estimating activities
- Develop and control the schedule
Topic 06. Human Resource Management
- Introduction and Resource Management Planning
- Estimating and acquiring resources
- Develop and manage the team
- Controlling Resources
Theme 07. Risk Management
- Introducing and Planning Risk Management
- Identifying Risks
- Qualitative and Quantitative Analysis
- Planning and Implementing Risk Response
- Monitoring risk
Theme 08. Cost Management
- Contextualising and planning Cost Management
- Cost Estimation and Budgeting
- Cost Control
Topic 09: Monitoring and Control and Integration
- Project Management Plan
- Integrated Project Management
- Integrated Change Control
- Crisis in IT Projects.

1. Basic Bibliography. Available in electronic format
1.1 Notes and slides of the subject.
1.2. PMBOK: A Guide to the Project Management Body of Knowledge (Pmbok Guide)- Sixth Edition by Project Management Institute, 2017. ISBN: 9781628253900

2. Supplementary Bibliography

2.0. Chrissis, Mary Beth; Konrad, Mike; Shrum, Sandy. "CMMI Para el desarrollo, versión 1.3: Guía para la integración de procesos y la mejora de productos", Editorial Universitaria Ramón Areces. España. 2012 ISBN: 978-8499610788

2.1. Estimation
2.1.1. Jack E. Matson, Bruce E. Barrett, and Joseph M. Mellichamp, "Software Development Cost Estimation using Function Points", IEEE Transactions on Software Engineering, vol 20, no 4, April 1994.
2.1.2. Marcela Varas C, "Modelo de Gestión de Proyectos Software: Estimación del Esfuerzo de Desarrollo", Informe de Habilitación Profesional para optar al Título de Ingeniero Civil Informático, Universidad de Concepción, 1995. http://www.inf.udec.cl/~mvaras/papers/arica/arica.htm
2.1.3. Magne Jørgensen, “Practical Guidelines for Expert-Judgment-Based Software Effort Estimation” IEEE Software. May/June 2005
2.1.4. Barry Boehm ‘Safe and Simple Software Cost Analysis’ IEEE Software Septiembre/Octubre 2000

2.2. Quality Management
2.2.1. ISO 9000:2000 series: Quality management systems. 2000. ISO
2.2.2. ISO 90003: Software engineering -- Guidelines for the application of ISO 9001:2000 to computer software. ISO

2.3. Risk Management
2.3.1. Boehm, B.W., Software Risk Management: Principles and practices, IEEE Software, 32-41, Enero 1991.
2.3.2. Software risks taxonomy. http://www.sei.cmu.edu/risk/main.html
2.3.3. http://www.decisionmetrics.net

2.4. Process Evaluation
2.4.1. ISO/IEC 15504 ISO/IEC Information Technologies – Process assessment (parts 1-5) ISO.
2.4.2. CMM/CMMI Capability Maturity models. Continuous and staged models. www.sei.cmu.edu/CMMI

2.5. Human Resources
2.5.1. J. Fernando Naveda, Stephen B. Seidman “Professional Certification of Software Engineers: The CSDP Program” IEEE Software September/October 2005

At the end of the course, students should have mastered the following aspects:

1. Know, analyse and enhance the factors that influence the success of a project.
2. Estimate the effort required to carry out a project.
3. Set the schedule of milestones and deliverables and establish the planning of a project.
4. Know and carry out the monitoring and control tasks of a project.
5. Perform a risk analysis and take the appropriate preventive and/or mitigating measures.
6. Understand the concepts and methods associated with quality management and customer satisfaction.
7. Manage changes in the requirements of a project.
8. Manage configuration management, being able to maintain adequate version control.
9. Manage the budget of a project, making a good control of expenses.
10. Manage the human resources of a project, enabling their participation in other projects.

Students must have developed the basic and general competences CB3, CG1, CG2, CG3, CG5, CG6, CG8, CG9, CG12. Students will also work on the transversal competences in particular with regard to analysis and synthesis skills, organisation and planning skills, oral and written communication, information management skills, problem solving and decision making, teamwork and motivation for quality.

As part of the Organisation and Management module, the subject also develops the basic training competences: FB5, FB6; the IT-related competences: RI1, RI2, RI3, RI8 and RI16; and the IT-related competences TI1, TI2 and TI5. In addition to which the subject also covers the last of the module competences, i.e.: Understanding how to develop a comprehensive IT project within a company.

The contents of the subject will be taught indistinctly in lectures and interactive classes. Theoretical and practical units will be taught alternately throughout the four-month period, with the aim of reinforcing the concepts taught in them and using theory as the real basis for the practical units.

The completion of all the practicals is necessary, as is class attendance, in order to pass the subject, since theory and practicals complement each other and are taught indistinctly in lectures and interactive classes.

The resources required for the subject are as follows:
a) Copies of the subject notes.
b) Student access to the bibliography in the library or on the Internet.
c) Access to MS Project© or ProjectLibre tools.
d) MS Office or LibreOffice for the preparation of the documentation of the practicals.

The section on assessment summarises how the competences are addressed through the theoretical and practical content of the subject. The following is a summary of the typology of the classes and how the competences of the subject are addressed with their contents and activities throughout the course.

The expository hours must be complemented with one hour of autonomous study by the students and the iterative hours will require up to a maximum of 3 hours distributed between writing, revision and correction of the work according to the evolution of the project and the knowledge and abilities of each student.

Week: 1
Type: Expository
Content: Topic 01. Introduction to project management.
Weeks: 2 - 3
Type: Expository
Content: Topic 02. Scope Management
Typology: Interactive
Content: Case Study 1. Scope of a project and requirements catalogue.
Week: 4
Typology: Expository
Content: Topic 03. Stakeholder and communication management.
Typology: Interactive
Content: Case Study 2. Stakeholders and Communications.
Week: 5
Typology: Expository
Content: Topic 04. Estimation
Typology: Interactive
Content: Case Study 3: Estimating project requirements.
Week: 6 - 7
Typology: Expository
Content: Topic 05. Time management. Planning
Typology: Interactive
Content: Practical Case Study 4. Drawing up a project timetable.
Week: 8
Typology: Expository
Content: Topic 06. Human Resources Management
Typology: Interactive
Content: Case Study 5. Elaboration of the HR plan for a project.
Week: 9
Typology: Expository
Content: Topic 07. Risk Management
Typology: Interactive
Content: Case Study 6. Elaboration of a project risk plan.
Week: 10 - 11
Typology: Expository
Content: Topic 08. Cost Management
Typology: Interactive
Content: Case Study 7. Cost estimation and budgeting.
Week: 12 - 13
Typology: Expository
Content: Topic 09. Monitoring and Control and Integration
Typology: Interactive
Content: Case Study 8: Project Integration and Monitoring
Week: 14
Typology: Interactive
Content: Case Study 9. Integration of plans. Final document.

In order to pass the subject, students must pass both the theory and the practical part of the course separately.

Practicals are not made up in July; except in those cases in which the student reaches 40% of the maximum mark for practicals and is then allowed to do all the practicals with respect to a new practical case study specifically designed for a possible make-up. In this case, the new practical case will be uploaded to the virtual platform two weeks before the theoretical exam of the subject. In the assessment of the work submitted by the students, the degree of achievement of the competences will be assessed, in particular the implementation of the contents provided by the course to these competences. In addition, the transversal competences will be assessed insofar as they are required for the development of these assignments.

The questions in the theory exam will focus on the specific contents, which have been developed in the subject, in relation to their competences and which may have been acquired in both the expository and interactive parts. The average duration of the exam is approximately 2 hours and may consist of multiple-choice questions, short questions and case study problems. The exam will assess the degree of assimilation of the teaching objectives established in the syllabus of the subject.

There will be no partial exam.

Once both parts have been passed separately, the exam will be 40% of the final mark and the practical will be 60%.

In order to be assessed as NOT PRESENTED, one of the following circumstances must be met:

1. Not having attended at least 85% of the practicals of the subject.
2. Not having taken the theoretical exam of the subject despite having passed the practicals of the subject.
3. Not having taken the theoretical exam of the subject and having communicated explicitly and in writing to the person in charge of the subject that the subject has been abandoned when, despite having taken at least 80% of the practical exercises of the subject, the practical exercises have not been passed.

Weighting of the continuous assessment in the extraordinary opportunity of recovery (July exams):
1. The mark obtained in the practicals during the course is maintained, as well as its weight in the final mark.

In cases of fraudulent performance of exercises or tests, the provisions of the Regulations on the evaluation of students' academic performance and revision of grades will apply.

The distribution of competences in the activities and syllabus of the subject is summarised below. However, the marks obtained by the students in the practicals will correspond to those obtained in Practical Case Study 9. This is due to the fact that all the practical cases are related to a single project whose final documentation corresponds to this practical case study. In it, students will have to hand in all the previous work with the corrections linked to the learning acquired throughout the course. For this reason, those competences that are developed in all the activities will be linked to this case study and others will be left out only when they are particularly relevant to the acquisition of the said competence.
Mat 1: Practical Case Study 9, Topic 1
Mat 2: Case Study 3, Case Study 7, Topic 4, Topic 8
Mat 3: Case Study 4, Topic 5
Mat 4: Case Study 8, Topic 9
Mat 5: Case Study 6, Topic 7
Mat 6: Case Study 1, Case Study 2, Topic 3
Mat 7: Case Study 9, Topic 1
Mat 8: Case Study 9, Topic 2
Mat 9: Case Study 7, Topic 8
Mat 10: Case Study 5, Topic 6
CB3: Case Study 1, Case Study 5, Subject 7, Subject 6
GC1: Case Study 9
GC2: Case Study 8, Case Study 9
GC3: Case Study 9, Topic 9
GC5: Case Study 9
GC6: Case Study 9
GC8: Topic 1
GC9: Case Study 9
GC12: Topic 5, Topic 8, Topic 6
FB5: Topic 1
FB6: Topic 1
RI1: Case Study 1
RI2: Case Study 1, Case Study 4, Case Study 7, Case Study 8
RI3: Case Study 5, Case Study 2
RI8: Case Study 1, Case Study 9
RI16: Topic 1
TI1: Case Study 1
TI2: Case Study 7, Case Study 8, Case Study 9
TI5: Case Study 1, Case Study 8, Case Study 9

The total study time and the student's personal work is 90 hours, divided approximately as follows:

1. Self-study: 5 hours
2. Writing exercises, conclusions or other work: 20 hours.
3. Programming/experimentation or other computer/laboratory work: 40 hours.
4. Evaluation of work, projects, exams, ...: 25 hours.

Other activities may be proposed (problem solving, reading of texts and case studies, etc.). In the case of compulsory activities, they will not imply an increase of total work (in this case, the hours of activities 2 and 4 would be reduced).

Class material should be complemented with the recommended bibliography; especially with the CMMI and PMP documentation.

This subject will be taugh in Spanish