Content:

1. IT-projects and project management
2. Opportunity identification (before the project is initiated)
3. Definition of project objectives (scope) and requirements
4. Project management model selection
5. Estimation and planning
6. Execution, monitoring and control
7. Handover and implementation in the organization
8. Quality, quality standards, contracts and evaluation
9. Operations and maintenance
10. Projects in organizations and project culture
11. Standards and norms for project management
12. The human side of project management

Knowledge

• The aim is to provide knowledge of the scope and business background of projects, objectives and goals, organization and staffing of projects, management of the project team, planning, progress management and follow up, management of cost and benefits, stakeholder management, quality management, communication management, risk management, and managing the evolution and changes of requirements.

Skills

• The student must acquire skills in applying the acquired knowledge to manage projects and thus take responsibility for projects from start to finish
• Through a project study that is part of the course, the students will acquire skills in applying theory, models and tools for project management, reflect on the use, and generalize (exemplify) experience from use for other projects

Competencies

• The student should after the course be qualified to manage projects and thus take responsibility for projects management
• The student should after the course be qualified to participate in and lead a project team
• The student should be able to use awareness of the context and the concrete situation for a project to select the appropriate methods and techniques for that specific project

It is particularly aimed at students who are interested in taking on the role of project manager for change processes involving IT. You should have some experience with project work. It is an advantage if IT was involved in this as most examples in lectures and literature are taken from the IT world, but it is not a prerequisite for participating.

Curriculum:

• Firesmith D. (2003), Specifying Good Requirements, Journal of Object Technology, vol. 2, no. 4, pp. 77-87.

• Kotter J.P. (1995), Leading Change: Why Transformation Efforts Fail, Harvard Business Review, Mar/Apr, pp. 59-70.

• Kousholt, B. (2012). Project Management: Theory and practice. 2. edition. Nyt Teknisk Forlag.

• Lauesen S. (2002), Software Requirements, Style and Techniques, p. 12-30, 376-380. Addison-Wesley.

• Pries-Heje, J. & T.H. Commisso (2011). The Six-C model for IS project teambuilding, In: Timo Leino (Ed.), Proceedings of IRIS 2011, TUCS lecture notes, Turku, Finland.

• Smits H. (2006). 5 Levels of Agile Planning: From Enterprise Product Vision to Team Stand-up. Rally Software Development Corporation.

• Slides and all other material used during the course.

Every Thursday at 8.30 - 12.45 a.m. in the period from 3 September - 12 November 2015.

Lectures and exercises.

Evaluation:

Excellent fulfillment of the aim of the course implies that the student demonstrates:

• high level of knowledge, insight and breadth of view wrt. theories, concepts, models and tools in IT project management,

• high level command, independent argumentation and critical reflection wrt. choice and application of models and tools based on and in accordance with own project examples and experiences,

• independent and clear layout, proficient and precise presentation of concepts wrt. structure and content during the exam (including both the final report and the oral presentation).

Good fulfillment of the aim of the course implies that the student demonstrates:

• clear knowledge and breadth of view wrt. theories, concepts, models and tools in IT project management,

• clear command, argumentation and critical reflection wrt. choice and application of models and tools based on and in accordance with own project examples,

• clear layout and clear presentation wrt. structure and content during the exam (including both the final report and the oral presentation).

Adequate fulfillment of the aim of the course implies that the student demonstrates:

• adequate, but limited knowledge of theories, concepts, models and tools in IT project management,

• adequate command and some degree of argumentation for choice and application of models and tools,

• some degree of layout and adequate presentation wrt. structure and content during the exam (including both the final report and the oral presentation).

20 min. individual oral exam based on a written assignment incl. grading.

External examiner and 7 step scale.

Thursday 21 January 2016

20 min. individual oral exam based on a written assignment incl. grading.

External examiner and 7 step scale.

Before end of February 2016.