Project Management Laboratory

Code:

EIC0106

Acronym:

LGPR

Keywords
Classification	Keyword
OFICIAL	Software Engineering
OFICIAL	Multidisciplinary Themes

Instance: 2012/2013 - 2S

Active?	Yes
Web Page:	https://moodle.fe.up.pt/1213/course/view.php?id=442
E-learning page:	http://moodle.up.pt/
Responsible unit:	Department of Informatics Engineering
Course/CS Responsible:	Master in Informatics and Computing Engineering

Cycles of Study/Courses

Acronym	No. of Students	Study Plan	Curricular Years	Credits UCN	Credits ECTS	Contact hours	Total Time
MIEIC	125	Syllabus since 2009/2010	4	-	7	70	189

Teaching language

Suitable for English-speaking students

Objectives

1 - BACKGROUND
The success of projects and software products depends not only on the field of technical skills necessary to perform the various activities of the life cycle of software development, but also, increasingly, a set of skills and management skills, behavioral and communication, such as project management skills (in its various variables of time, budget, scope, quality, resources, etc..), capacity for teamwork, relationship skills with customers and communication skills and marketing.

2 - SPECIFIC OBJECTIVES
At the end of the course students should be able to:
1.Identify the need for use of project management as well as the importance of its strategic framework;
2.Identify the different frameworks and methodologies for project management;
3. Identify and define the process areas and variables involved in project management;
4. Apply methodologies and tools for project management and teamwork;
5. Apply concepts and tools of quality management ;
6. Identify and manage project risks.

3 - PREVIOUS KNOWLEDGE
Mastery of technical skills needed to develop software projects.
Having attended the Software Development Laboratory (LDSO).

4 - PERCENTAGE DISTRIBUTION
Scientific Component: 50%
Component Technology 50%

5 - LEARNING OUTCOMES
This course unit aims to develop students’ software project management skills and team work skills in software projects. Students will be capable of solving a vast diversity of problems, which may happen in these projects. This course unit will also stimulate students’ entrepreneurship.

Working method

Presencial

Program

1. PROJECT MANAGEMENT: Starting a project; planning a project (hierarchical decomposition of a project; setting dependencies; resources assignment; time allocation; diagrams; project plan document; Program Evaluation and Review Technique (PERT) and Critical Path Method (CPM); project control and monitoring (project progress, earned value management, periodic report, re-planning); finishing a project (report, outcomes).
Areas of knowledge: project integration management, scope management, time management, cost management, quality management, human resources management, communication management, risk management, provisions procurement management.

2. TEAM WORK
Team work, management styles and team organisation, team building, leadership and coaching, personal communication, meetings management, negotiation and conflict management, logbooks.

3. METHODOLOGIES AND TOOLS
Project management methodologies and organisation of software teams: Team Software Process (TSP); Scrum; Rational Unified Process (RUP).
Project management tools and team work.

4. EXPERIMENTATION
Application in real projects developed by medium-sized teams; application of methodologies and techniques.

Mandatory literature

Tom DeMarco & Timothy Lister; Peopleware. ISBN: 0-932633-43-9
S. McConnell; Software Project Survival Guide: How to Be Sure Your First Important Project Isn’t Your Last, Microsoft Press, 1997
C. Jones; Software Engineering Best Practices, McGraw-Hill, 2010
W. Humphrey; TSP: Leading a Development Team, Addison-Wesley, 2006
Cópias de acetatos e textos fornecidos
IEEE Guide Adoption of PMI Standard A Guide to the Project Management Body of Knowledge , IEEE Press, 2004
W. Humphrey; PSP: A Self-Improvement Process for Software Engineers, Addison-Wesley, 2005
Revistas técnicas e websites
Alexander Osterwalder, Yves Pigneur; Business Model Generation: A Handbook for Visionaries, Game Changers, and Challengers, Wiley, 2010. ISBN: 978-0470876411

Teaching methods and learning activities

The theoretical component of this course unit is based on the presentation and discussion of some themes covered in Software Engineering, namely the ones related to Project Management.
Practical classes will be based on the development of projects, where students will be organised in medium-sized groups.

Evaluation Type

Distributed evaluation without final exam

Eligibility for exams

Students have to actively participate in the development of projects. Besides they cannot miss more classes than allowed by the rules.

Calculation formula of final grade

Final Mark will be based on the assessment of groups’ participation and discussion in theoretical classes and on the work develop in practical classes. The assessment will be focused on the following aspects:
- Communication, image and marketing (presentations, client communication, promotion of ideas and products);
- Project management (goals accomplishment, individual and team dynamic)
- Attendance and participation in class and meetings (it will be kept a record and it will be assessed students’ performance)
- Results (quality)

These aspects contribute to the Final Mark in the following percentages:
- Communication, image and marketing: 15% of the Final Mark
- Project management and team work: 45% of the Final Mark
- Attendance and participation in class and meetings: 10% of the Final Mark
- Results: 30% of the Final Mark
As for the individual assessment, it will be based on the final mark of the team, professors’ opinion and team self-assessment.

Special assessment (TE, DA, ...)

It is the same as for ordinary students.

Classification improvement

Students can only improve their marks in the following year by doing a new project, since this course unit does not comprise a final exam.

Observations

Importantes datas: - 15.02.2013: First class; Presentation of the curricular unit; team and project presentation - 22.02.2013: Project Kick-off meeting and first meeting with the client - 5.04.2013: Intermidiate presentations - 5.06.2012: Project completion - 07.06.2012: Final presentations and project closure