The course trains the students in methods for design of a technical system containing information and communication technology under resource and time constraints. The methods are among others development process, project planning, reflection methods and design methods for technical systems .

After passing the course, the student should be able to

• in groups and with a structured developmental methodology carry out a project for development of a system with information and communication technology
• reflect on the project as a basis for improvements of the working method.

The course runs in three phases.

The first phase of the course is preparation. You read up on the project methodology we use (Scrum), and the version management tool we use (Git). Also during the preparation phase, teams are formed, and the teams suggest and discuss product-ideas with the teachers. The teachers approves one of the team's product ideas.

The second phase is project work. Your team will design and implement the product in three so-called sprints. The length of each sprint is five working days. Only Wednesdays, Thursdays and Fridays are working days; therefore, it takes nearly two weeks to finish a sprint. On working days, students work full office-hours: from 8:00 to 17:00, with a lunch hour from 12:00 to 13:00. At the end of each sprint, the team reflects on which project-methods worked well, and which didn't, in order to improve the next sprint.

The third phase is for final reflection. The product (or prototype) that your team developed is now ready. All products are shown to the public at a project expo. You also submit a written individual reflection, which documents the experience you gained in the course.

Teams are formed by the examiner one week before the first lecture. In the time between the forming of teams and the first lecture, each team is encouraged to meet, discuss a social contract, and do brainstorming to find project ideas. This enable the team to make a running start with the project.

Henrik Kniberg: Scrum and XP from the trenches, 2nd edition, available at
http://www.infoq.com/minibooks/scrum-xp-from-the-trenches-2
Downloading the book requires a zero-cost registration.

Ken Schwaber och Jeff Sutherlans: The 2020 Scrum Guide, available at
https://scrumguides.org/scrum-guide.html

A personal computer is used for the project work. Using the computer rooms at KTH instead is not practical.

Students at KTH with a permanent disability can get support during studies from Funka:

Funka - compensatory support for students with disabilities

P, F

• PRO1 - Project, 7.5 credits, Grading scale: P, F

Based on recommendation from KTH’s coordinator for disabilities, the examiner will decide how to adapt an examination for students with documented disability.

The examiner may apply another examination format when re-examining individual students.

In the first phase, each student must complete all quizzes in Canvas, before the deadline given for each quiz. There must be at most one incorrect answer on each quiz. Furthermore, each student must do preparatory work in the assigned project group, and the project must be approved by the examiner.

In the second phase, attendance is obligatory on working days. All students work full office-hours: from 8:00 to 17:00, with a lunch hour from 12:00 to 13:00. Furthermore, each student must participate actively at no less than two of the sprint retrospectives.

In the third phase, each team must participate in the product expo. A list of requirements for the product expo is given separately. Furthermore, each student must submit an Individual Project Reflection. A list of requirements for the Individual Project Reflection is given separately.

Attendance and active participation require that students are physically present on campus. Any exception requires a written permission by the examiner.

Quizzes in the first phase may be completed late, as long as all quizzes are completed no more than five days after the start of the second phase.

In the second phase, attendance is obligatory. All absence is treated equally - the reasons for absence do not matter.

Submissions in the third phase may be completed late, but always before the start of the next academic year.

The following rules apply to absence in the second phase.

• If you are absent up to 8 hours (1 day), in total during the whole project, you and your group should agree on how you can work extra time to compensate.
• If you are absent 8-32 hours (1-4 days), in total during the whole project, you must notify the teachers immediately by emailing F Lundevall. "Immediately" means as soon as you realize that you need to be absent (preferably well before the first time you are absent). You will perform extra work of some kind to compensate - see below.
• If you are absent more than 32 hours (more than 4 working days), in total during the whole project, you fail the course and must take the course again next year.
• You also fail the course if you are assigned extra work, or an individual task, but do not complete that work or task satisfactorily and timely.

Extra work to compensate for 1-4 days of absence can be either directly related to the team's project, or an individual task to be performed in early June. Tasks related to the team's project must be agreed on by the whole team and the examiner. An individual task to be performed in June is decided on in agreement between the examiner and the student (but the examiner will have the last word, of course).

An individual task to be performed in June, is typically to write a short report. The content of this report should be potentially useful to other people after the course. The task is designed so that the expected amount of work approximately equals the amount of absence from the project. The deadline for the task is normally in the re-examination period in June. Late submissions may be accepted before the start of the next academic year.

During the course, intermediate results are available in Canvas.

Final grades are reported after the course, in June.

• All members of a group are responsible for the group's work.
• In any assessment, every student shall honestly disclose any help received and sources used.
• In an oral assessment, every student shall be able to present and answer questions about the entire assignment and solution.

For Spring, 2025, the course has been redesigned to use only Wednesdays, Thursdays and Fridays as working days. This enables participants to take another course on Mondays and Tuesdays. A further result of this redesign is, that the redesigned course in 2025 has a compressed preparation phase, and a stretched-out project phase. The reasons for the redesign are outlined below.

In 2024 and earlier, II1305 was taken together with a companion course: IV1303 Modern Software Development. The second phase of II1305 (project weeks) was then four weeks of full-time work, with five working days per week (Mondays through Fridays). This created a realistic simulation of a developer's work. From 2025 and on, however, the companion course is no longer available.

The companion course, IV1303 Modern Software Development, was designed together with II1305, and the total workload of the two courses was roughly the same every week. During the first phase (preparation) of II1305, the workload in II1305 was light, while the workload in IV1303 was high. In the second phase (project work) of II1305, these workloads were reversed, with full-time work in II1305 and a minimum of work in IV1303. In the third phase (reflection) of II1305, the workloads were again reversed, with each student writing a short reflection in II1305, and a larger report in IV1303.