Study Guide

Objective

After completing the course the student is able to:
- Work as a member of a project team and describe how ICT projects are managed.
- Document and report project results.
- Use Information technology tools when working in project.

Content

Introduction to Project Management
Introduction to Version Control
Practical project work

Materials

Material available via the learning environment (ITS).

Teaching methods

Mainly team working.
Every week, there is 1-2 hours theory followed by practical work with teachers (2-3 hours).
Additionally, 2 hours per week independent project working.
At the end of the project, students need to complete peer review for their project team.

Exam schedules

-

International connections

The course includes approximately 10 weekly theory sessions followed by practice.
Students work in maximum 5 member teams where they complete project work using SCRUM method.
Additionally, students need to complete personal assignments relate to to the project work.

All the material related to the projects are stored in Teams channels for the projects.
Only electronic materials are used in the implementation. In addition, project reporting is also carried out online in Teams to reduce the carbon footprint caused by movement.

Completion alternatives

-

Student workload

Contact hours
- week 36: 2h theory: 2h
- week 37 - 38: 2h theory + 3h team work : 2 x 5h = 10h
- week 39 -46: 1h theory + 4h team work: 7 x 5h = 35h
- week 47: 3h team work + 2h project presentations: 5h
Home work: approximately 30 hours
Total: approximately: 80 hours

Content scheduling

Week 36
- Course introduction
- Introduction to project management
- Project Communication
- Roles in projects
Week 37 - 38
- Project Planning and Risk Management
- Introduction to SCRUM
- Team building
- Project work introduction: Creation of web site for a fictive organization
Week 39 - 46
- Project working using SCRUM
- Topics related to project management and R&D work (SCRUM principles, project steering & control, immaterial rights, testing, project closure, ...)
Week 47:
- Presentation of final version of project work

Further information

ITS, Teams and Trello.
Additionally, ViLLE is used to follow-up of participation, time reporting, and for project team peer reviews, and for the SCRUM tutorial.

Evaluation scale

H-5

Assessment methods and criteria

Participation in 11 contact days.
Time reporting for project planning and 4 Sprints
Role and activity in Project work.
Peer review within team.
Test in SCRUM tutorial.

Assessment criteria, fail (0)

The student does not complete the project work or does not participate in it actively.
Student participates less than 6 contact days.

Assessment criteria, satisfactory (1-2)

The student participates in the project work and operates according to the method (SCRUM) used in the project.
Student gets at least 50% points in the test of the SCRUM tutorial.
Student participates in 6 - 7 contact days.

Assessment criteria, good (3-4)

The student participates in the project work, where the project team performs the required tasks according to the schedule and knows how to operate in a project using SCRUM.
Student gets at least 80% points in the test of the SCRUM tutorial.
Student is available in 85% of contact sessions.

Assessment criteria, excellent (5)

The student participates in the project work and acts in a key role in the project (e.g., SCRUM Master), ensuring that the project team performs the required tasks and documentation according to the schedule. The student knows how to use version control (GIT) in project work.
Student gets 100% points in the test of the SCRUM tutorial.
Student participates in 10 contact days.