Project Introduction 2014
The first project meeting will take place 2014-09-04 at 13.15 in A2, house A. At this first meeting you will get information about what company you belong to (by lottery) and more detailed information about what the project is all about. The consulting supervisors will present themselves and there will be time for questions. This is the official start of the project and from this moment it is your task to deliver the right product, with the good quality, within budget at the right time!
Note that this meeting is compulsory. If you do not attend or do not send an email before the meeting explaining why you cannot attend, we cannot guarantee that you can be part of the project part of the course.
Company MeetingsAt the company meetings all employees in the company meets. The meetings take approximately one hour and the agenda is defined by the department managers. Depending on where in the project we are, different issues will be discussed. Typically plans for iterations, review of iteration (status of what has been produced in the iteration) and reflection (what went well/what went bad) is discussed. Note that these meetings are compulsory.
Status ReportsThe day before a meeting, short status reports should be sent via email to the CEO, the consulting supervisors, and to the employees of the company. One report should be sent in from each department. These reports should be fairly short and contain:
- What has been done since the last meeting?
- What is planned to be done to the next meeting?
- Which problems exist? Which risks exist for future problems?
- Time report - time spent in the project for each employee.
The contract that was signed between the Customer and our company consisted of two parts. The Customer initially pays for a pre-study, where the project teams should collect requirements, create a realistic time schedule, build necessary prototypes and form an initial design of the product. This pre-study period ends with a tollgate meeting, where the project teams shall present in a convincing way what the product will look like and that they will be able to develop it in time. After this meeting, the Customer will decide if he wants to proceed and order the whole product. Hence, this meeting is very critical for the whole project to be successful! Note that this meeting is compulsory.
The CEO has not specified that one specific software process should be followed. Instead, it is the tasks for the employees in the departments to self organize and discuss how they want to work, e.g. if they want to follow a specific process or not. However, one requirement is that the work shall be iterative, i.e., a working system should be released and tested at specific milestones, so that the reference customer can test the system and give feedback.
Release of version 1.0
In December, the reference customer will decide which system they will buy. At the VSSE'14 - Valla Software and System Expo, which takes place in December, all companies will present their product.
The schedule for these meetings in Ht1 are listed in the Schedule at Google Drive
Page responsible: Kristian Sandahl
Last updated: 2014-08-20