Nyhetsflöde

Things you'll want to know from the middle-of-the-course meeting

Dear Teams,

Today, I and the student-representatives had a very productive middle-of-the-course meeting.

One suggestion from the meeting is, to have clearer instructions on how flexible (or inflexible) the working hours really are. Therefore, the project rules have been updated with additional details.

Specifically, when a methodology lecture is cancelled, it is perfectly okay to work eight hours that day (and also work eight hours the nearest Wednesday, instead of nine hours). It's also okay to take 5-10 minutes each day to fill in the daily report for the methodology course.

If you have any questions (or worries), please contact me directly. E-mail: flu@kth.se

Other points of discussion from the middle-of-the-course meeting:

• Teams are happy, motivated, and find the project-course interesting, new, and exciting.
• The freedom of choice in technical matters is very positive.
• Some team-members struggle with taking in the instructions for the course, and with finding out what is expected. If you have such struggles, first try to find the answers in Kniberg's book. If this fails, please contact me directly. E-mail: flu@kth.se
• The absence of clear instructions is, in some cases, intentional. Teams should organize themselves, and use the sprint-retrospective to reflect on (and maybe update) the team's organizational choices. During the course, I will be present in (at least) one sprint-retrospective for each team.
• The rooms are too small. Next year, group sizes should be reconsidered, taking room-sizes into account.

Thank you student representatives, and all other team-members, for your help in making the project-course successful!

Best regards, F Lundevall

Tuesday 18 April

Dear Project Teams,

Tuesday 18 April is your last day of planning before going ahead with your respective projects.

I will be available during the day, for coaching when necessary. To reach me, post a comment to this message, indicating a suggested time and the precise geographical location of your team.

The following schedule is suggested. Your team may agree on a different schedule.

• 10-12: The team prepares a tentative release plan, and a backlog of user-stories. Make sure that the team and the product-owner (or proxy) agree on the scope and how-to-demo of each user-story. Use planning poker to get estimates for the stories that are expected to get the highest priority.
• 12-13: Lunch break. To get the most out of the lunch break, I suggest you discuss fantasy literature, fencing, funicular railways, and/or anything else to take your minds off the upcoming project.
• 13-15: First sprint planning. Follow the guidelines given by the book. If planning is not near-ready by 14:45, take an extra look at the section "Where to draw the line", in the book chapter "How we do sprint planning". Finish the meeting at 15:00 precisely.

Best regards, F Lundevall

Reshuffling of project groups

Dear students,

There will be some changes in the group assignments this week. I will contact those involved via e-mail, so please check your e-mail during this period. I expect all changes to be finished on Wednesday 29 March.

Best regards, F Lundevall

Groups are assigned, but we need Student Representatives

Dear IT Project students,

All registered participants have now been assigned to groups. Please check your group membership in Daisy.

Another thing - we need two student representatives for the course.

• The student course representatives are elected or otherwise identified among the students by the students;
• two formal meetings are suggested between teacher and course representatives, one in the middle of the course and one after the end of the course.

If you would like to be a student representative, please announce this in a comment to this post. There can be more than two representatives.

Best regards, F Lundevall