Front Page

Course Timeline

This page summarizes the course, in timeline form. If a change must be done during the course, there will be a relevant announcement about the change here in Canvas.

Most important links: Course memo (kurs-PM) 2024, Practices and Tools, Things You Need To Know, Last Sprint Demo and more, Expo: Instructions for Teams, Expo 2024.

Useful links: Current and Finished Projects, Documents, Individual Project Reflection, Scrum Videos.

Schedule: Schedule for II1305.

To join the course evaluation board (kursnämnd), please e-mail flu@kth.se.

Contact: e-mail flu@kth.se

Part 0: Advance preparation

Even before the course starts, you can begin to discuss product ideas. For an external project, making contact early is particularly important. Please register for the course as soon as possible. Registration opens 2024-03-14.

Part 1: Preparation

Summary: learn Scrum, learn Git, get your team together, get your product idea approved.

  • Get the course book. Start reading it.
  • Install Git on your computer. Git is a command-line system for version management of source-code for programs and other stuff.
  • Course start and introductory lecture, Wednesday, 2024-03-20 at 13:15-15:00.
  • Watch the first video seminar on the Git version-management system. Link: Git Seminars 
  • Try Git yourself.
  • Watch the second video seminar on the Git version-management system. Link: Git Seminars 
  • Lecture on Scrum and other agile methods. Monday, 25 March at 15:15-17:00.
  • Go through the slides from a seminar on testing. Link: Git Seminars
  • Teamwork Exercise and Scrum Exercise. Tuesday, 26 March at 10:15-12:00.
  • First meeting with the teachers, to discuss product ideas. Held separately for each team. 26-28 March. Highly recommended, but not obligatory.
  • Finish reading the whole course book.
  • Finish all quizzes, with no more than one incorrect answer on each quiz. Deadline: 2024-04-02 for all quizzes.
  • Second meeting with the teachers, to get a product idea approved. Held separately for each team. 9-11 April. Very important, but not obligatory.
  • Project Start. Monday, 2024-04-15, at 08:01 exactly (not fifteen minutes later). Obligatory attendance.

Part 2: Sprints

Summary: develop product. Attendance is obligatory during all sprints.

Sprint 1: 15-19 April. Sprint 2: 22-26 April. Sprint 3: 29 April through 3 May. Sprint 4: 6-15 May.

During the sprints, you work every day (Monday through Friday), from 8:00 to 17:00, with a one-hour lunch break.

  • Before first sprint: backlog refinement meeting, preferably with product owner.
  • Morning of first day of first sprint: sprint planning.
  • Afternoon of first day of first sprint, and three days more: product design and implementation.
  • Last day of first sprint: sprint demo. Times announced separately.
  • Last day of first sprint: sprint retrospective (one hour, time booked separately).
  • The second, third, and fourth sprint look like the first one, only better!

Part 3: Expo and Reflection

Summary: show product, reflect on project to improve your ways of working.

  • At the end of the fourth sprint: create an exhibition of your project, open to the general public.
  • The exhibition is open on Thursday, 2024-05-16 at 9:00-16:00. Further instructions will come. Obligatory attendance.
  • Each group compiles their questions, answers and feedback from the exhibition into a document. The document is submitted in Canvas. Deadline: 2024-05-20.
  • After the project weeks: each student submits an Individual Project Reflection. Deadline: 2024-05-31.

Links that were once useful, but is now somewhat obsolete: External Projects, First Sprint Demo and Retrospective, Second Sprint Demo and Retrospective, Third Sprint Demo and Retrospective.