Language of instruction : English |
Credits: 3,0 | | | Period: semester 1 (3sp) | | | 2nd Chance Exam1: Yes | | | Final grade2: Numerical |
Sequentiality
|
|
No sequentiality
|
|
Work within a company can be divided into daily operations and projects. The first type of work is based on routine and uses, among other things, business process management for organizational optimization. The second type of work includes assignments that are finite in time and where routine plays a less important role. To optimally organize and manage project work, various project management methodologies have been developed and introduced in recent decades that can be divided into 2 major paradigms, classical vs agile project management.
The purpose of this course is to familiarize students with the principles and goals of project management. We study various phases that occur in most projects, such as the project discovery phase, the project planning phase and the project execution phase. Furthermore, we study the classical and agile project management paradigms and what the differences are between them.
|
|
|
|
|
|
|
Lecture ✔
|
|
|
Response lecture ✔
|
|
|
Small group session ✔
|
|
|
|
|
|
Discussion/debate ✔
|
|
|
Exercises ✔
|
|
|
Homework ✔
|
|
|
|
Period 1 Credits 3,00 Second examination period
Evaluation second examination opportunity different from first examination opprt | |
|
|
|
 
|
Compulsory textbooks (bookshop) |
|
Handboek 1:
Effective Project Management: Traditional, Agile, Extreme, Hybrid, Robert K. Wysocki, 8, Wiley
ISBN: 9781119562801 |
|
 
|
Remarks |
|
Computer Science students who wish to take the course “Projectmanagement” should submit an application via email to Prof. dr. Marijke Swennen by September 20 of the current academic year at the latest, with a motivation as to why they wish to take this course unit. A limited number of students will be selected based on the submitted motivation. |
|
|
Learning outcomes Bachelor of Computer Science
|
- EC
| The Bachelor of Computer Science graduate values the technical quality of the final product result, works meticulously and systematically, and can correctly translate the related specifications into software. | | - DC
| | | - DC
| | | - DC
| |
|
|
|
Bachelor of Business and Information Systems Engineering
|
- EC
| EC 10: The holder of the degree identifies stakeholders and their interests and takes them into account when making decisions. (Stakeholder awareness) | - EC
| EC 13: The holder of the degree applies insights from business science and relevant supporting/related disciplines in the analysis of business and information technology problems. (Problem-solving capacity) |
|
|
|
| EC = learning outcomes DC = partial outcomes BC = evaluation criteria |
Offered in | Tolerance3 |
3de bachelorjaar in de informatica keuze selectie
|
J
|
3rd Bachelor of Business and Information Systems Engineering
|
J
|
Exchange Programme Business Economics
|
J
|
|
|
1 Education, Examination and Legal Position Regulations art.12.2, section 2. |
2 Education, Examination and Legal Position Regulations art.15.1, section 3. |
3 Education, Examination and Legal Position Regulations art.16.9, section 2.
|
|