Schedule

Posted on
General issues

This schedule contains course deadlines for basic project documents and links to the corresponding templates. Lecture times are also mentioned in the schedule. Activities marked with SPM are for project managers (TIETS19 students). All other activities are group-related or personal for all course participants.

All projects define their own schedule (milestones, reviews and inspections, etc.) in the project plan, so most of the deadlines mentioned in this general schedule can be earlier in each project’s own schedule.

All projects must have five meetings with the course staff (project plan inspection, three reviews, and a final meeting. Teams document in the project plan how they are going to manage requirements, do software design and implementation, and testing.

Schedule for 2019S projects (draft)

January

  • Initial lecture:
  • Check proposed projects in the Moodle and fill a form (link can be found from the Moodle) on projects you like to participate (form opens 10.1 and closes 14.1).
  • Course staff tries to form groups by Thu 17.1 and inform managers and teams about their project.
  • Friday, 18.1.2019, 10-12, A3111 (lecture (in Finnish, but material is in English) and meet your team starting at 11.00).
  • SPM: Check guidelines for first meeting with your team.
  • Friday, 25.1.2011, 10-12, A3111 (tools, in Finnish).
  • ALL: Start to maintain your personal working hours (a simple text-file with day, activity and hours is enough. Project manager gives guidelines). After X.1, hours can be logged directly to the Metrics Monitoring Tool. (Wait instructions from Pekka Mäkiaho, Pekka creates MMT projects and gives more information on user accounts etc.). All working hours so far can then be logged to the Metrics Monitoring Tool.
  • SPM: If everything is ok with your team’s MMT account, you can send the first weekly report using Metrics Monitoring Tool on Sunday 27.1 or Monday 28.1. Otherwise send the first report next week (3.2 or 4.2).
  • Start writing the project plan.
  • Requirements gathering and analysis begins.

February

March

  • Organise the 1st review meeting, deadline 1.3.
  • Follow your project’s schedule.
  • Organise the 2nd review meeting, deadline 29.3
  • Answer Personal report I questions in the Moodle (1.3-14.3).

April

  • Organise the 3rd review meeting, deadline 19.4.
  • In the end of April, programming work should be almost ready.

May

  • Return the project poster before the presentation to the lecturer in .pdf-format.
  • Final presentations are on Wed, 15.5.2019, 10-13, Pinni B3116.
  • Finish your project before Fri 17.5.2019. If your project has scheduling problems, contact the project supervisor.
  • Product delivery to the customers.
  • Return the final report and test report 48 hours before the final meeting.
  • Reserve 60 minutes meeting time for the final meeting.
  • Give the project CD to the supervisor and client.
  • Answer personal report II questions in the Moodle after your project.
  • If you made a project video, send a link to the lecturer.
  • If you published your project outcomes, send a link to the lecturer.
  • After the project the course supervisor sends a feedback questionnaire to the clients.
  • Answer university’s course feedback questions (you should get a notification email from the feedback system).
  • Credits will be given about 2-3 weeks after the final meeting. If you need to get your credits earlier, send an email to the lecturer.

June

  • Your project is behind schedule.
Schedule for 2018F projects

September

  • Initial lecture:
  • Friday, 14.9.2018, 10-12, B1096 (lecture (in Finnish, but material is in English) and meet your team starting at 11.00).
  • Friday, 21.9.2018, 10-12, B3107 (tools, in Finnish).
  • Friday, 28.9.2018, 10.00-12.00, B1097 (short project presentations).
  • Course staff tries to form groups by Wed 12.9 and informs managers and teams about their project.
  • Course staff add all participant to the course’s Moodle forum.
  • SPM: Organise first meeting with your team after you get team information.
  • ALL: Start to maintain your personal working hours (simple text-file with day, activity and hours is enough. Project manager gives guidelines). After 21.9, hours can be logged directly to the Metrics Monitoring Tool. (Wait instructions from Pekka Mäkiaho, Pekka creates MMT projects and gives more information on user accounts etc.). All working hours so far can then be logged to the Metrics Monitoring Tool.
  • SPM: Send first weekly report using Metrics Monitoring Tool on Sunday 30.9 or Monday 1.10.
  • Start writing the project plan.
  • Requirements gathering and analysis begins.

October

November

  • Follow your project’s schedule.
  • Organise the 2nd review meeting, deadline 16.11.
  • Answer Personal report I questions in the Moodle (1.11-12.11).

December

  • Organise the 3rd review meeting, deadline 14.12.
  • In the end of December, programming work should be almost ready.

January

  • Return the project poster before the presentation to the lecturer in .pdf-format.
  • Final presentations are on Thu, 17.1.2019, 10-14, SimSpace.
  • Finish your project before 18.1.2019. If your project has scheduling problems, contact the project supervisor.
  • Product delivery to the customers.
  • Return the final report and test report 48 hours before the final meeting.
  • Reserve 60 minutes meeting time for the final meeting.
  • Give the project CD to the supervisor and client.
  • Answer personal report II questions in the Moodle after your project.
  • If you made a project video, send a link to the lecturer.
  • If you published your project outcomes, send a link to the lecturer.
  • After the project the course supervisor sends a feedback questionnaire to the clients.
  • Answer university’s course feedback questions (you should get a notification email from the feedback system).
  • Credits will be given about 2-3 weeks after the final meeting. If you need to get your credits earlier, send an email to the lecturer.

February

  • Your project is badly behind schedule.