Project Game

1 The Project

Welcome to the eScooter project! To make a long story short - just watch the video.

1.1 The Team

The project team consists of four responsible persons - Isabelle, Roxanna, Omar and Wastl. Each team member is responsible for more than one project modul. The work in the modules are performed by employees in the several departments.

1.2 Targets

The cool looking eScooter is powered by a rechargeable battery. The scooter has to achieve a maximum speed of 20km/h. The driver gets informed by an onboard-display. The status of the scooter can also displayed by an app on a smartphone.

1.3 Project Milestones (Overview)

The following table presents the major project milestones only. For a detailed list see Project Milestones (Details).

Milestone name description
M1 - Project Definition
  • The project requirement document (PRD) is generated
  • Risk evaluation
  • Milestone plan
  • Project data is based on a rough estimation
  • Project requirement document
  • Project decision go/no-go
M2 - Project Planning
  • Detailed technical description of the modules
  • Detailed project plan (schedule) with aligned resource usage
  • All concept tasks are done
M3 - Project Execution
  • Working demonstrator with almost all features integrated
  • Some features might need further work
  • Project status reports with trend diagrams
  • All prototype tasks are done
M4 - Project Closing
  • All product features work as defined
  • Acceptance test by the customer passed
  • Lessons learned performed
  • Final project analysis performed
  • All final tasks are done

2 The Game

Within the project game you are undertaking all the necessary steps of a project manager. Because it is a game, there will be also a winner! The project with the highest score wins. For some tasks according the project milestones (see Project Milestones (Details)) you can earn points - or loose points. Your gaming partner is ProBot. ProBot generates your project data, donates points and sometime makes your project managers life a little bit challenging.

ProBot

As been seen in the following table (see Project Milestones (Details)) ProBot donates points for achieved milestones, wherever your activity is required (see red text in the table). For those milestones ProBot donates 10 points to your project. It you miss such a milestone deadline, ProBot will take away 10 points from your project. Whenever questions have to be answered, ProBot will donate 1 point in addition for every correct answer (max. 9 points). Please take care, that every project has different project data.

2.1 Project Milestones (Details)

The project milestones are your guideline. A step-by-step approach helps you to perform all necessary tasks. For every Milestone a deadline exists (see Schedule).

Table 2: Detailed Project Milestones
Milestone Description Student ProBot
M1
Project definition
M1.1
- Register your project in ProMaSi (see Register project).
- Get familiar with the deadlines of the Project Game Milestones (see Schedule)
Isabelle
M1.2
ProBot searches for registered projects and donates points.
X
M1.3
ProBot generates for all registered projects the predefined project modules and the estimated effort
X
M1.4
- see the list of modules within your project and the get the estimated work in ManDays for every module.
- Calculate the estimated total project effort and the estimated project end and enter them into ProMaSi
  (see Answer question).
Isabelle
M1.5
ProBot checks your answers and donates points.
X
M2
Project planning
M2.1
ProBot assigns tasks (concept, prototype, final) to all generated project modules (see Structure).
X
M2.2
Assign resources to all your project tasks (see Assign resource).
Wastl
M2.3
ProBot checks your resource assignments and donates points.
X
M2.4
- Balance your resources using the department load function (see Department load).
- Export the project data to a csv-File, for further processing (see Export project data)
- Calculate your project milestone dates (M2,M3,M4) and enter them into ProMaSi.
Wastl
M2.5
ProBot checks your answers and donates points.
X
M3
Project execution
M3.1
ProBot generates for all concept tasks the actual start, actual effort and actual finish data.
X
M3.2
- Export the project data to a csv-File, for further processing (see Export project data)
- Calculate the actual project milestone M2 based on the actual concept task data.
- Calculate the delay between planned M2 (see Milestone M2.4) and actual M2 and enter them into ProMaSi.
Roxanna
M3.3
ProBot checks your answers and donates points.
X
M3.4
ProBot deletes resources in the electrical development department because of illness and company leave.
X
M3.5
- Reassign resources to the newly unassigned modules in the electrical development department
  (see Assign resource).
- Balance your resources using the department load function (see Department load).
Roxanna
M3.6
ProBot checks your resource assignments, resource balance and donates points.
X
M3.7
ProBot generates for all prototype tasks the actual start, actual effort and actual finish data.
X
M3.8
- Export the project data to a csv-File, for further processing (see Export project data)
- Calculate the actual project milestone M3 based on the actual prototype task data.
- Calculate the delay between planned M3 (see Milestone M2.4) and actual M3 and enter them into ProMaSi.
Omar
M3.9
ProBot checks your answers and donates points.
X
M4
Project closing
M4.1
ProBot generates for all final tasks the actual start, actual effort and actual finish data.
X
M4.2
- Export the project data to a csv-File, for further processing (see Export project data)
- Calculate the actual project milestone M4 based on the actual final task data.
- Calculate the delay between planned M4 (see Milestone M2.4) and actual M4 and enter them into ProMaSi.
- Calculate the planned total project effort based on the planned task efforts.
- Calculate the actual total project effort based on the actual task efforts.
- Calculate the difference between the actual and the planned total project efforts in ManDays
  and enter them into ProMaSi.
Omar
M4.3
ProBot checks your answers and donates points.
X

2.2 Schedule

The participation within the project game follows a fixed schedule. Keeping the milestone deadlines is of utmost importance due to the fact, that ProBot don’t care about your excuses! In order to view the milestone deadlines enter ProMaSi, find your course and select show milestones form the left-sided menu. All student deadlines end at the time of 22:00 (10pm).

3 ProMaSi

ProMaSi - PROject MAnagement SImulation - is a web-based simulation software. ProMaSi provides a real-life simulation of the project management tasks, as defining the schedule, assigning resources, balancing resource load and react on unpredictable changes in the schedule.

3.1 Structure

The following picture presents the structure of ProMaSi - the simulation software .

ProMaSi structure

3.2 Department List

department name responsible
test management Isabelle
sales and marketing Isabelle
software development Omar
electrical development Roxanna
mechanical development Wastl

3.3 Module List

module name responsible department
sales and marketing strategy Isabelle sales and marketing
acceptance test management Isabelle test management
sales strategy Isabelle sales and marketing
system control Omar software development
connectivity and app development Omar software development
on-board display Omar software development
drive control Roxanna electrical development
on-board management Roxanna electrical development
battery charger Roxanna electrical development
chassis Wastl mechanical development
steering Wastl mechanical development
powertrain Wastl mechanical development

3.4 Register project

Hello students,

your first action within ProMaSi is to register your project. Please follow the necessary steps listed below:

Perfect!

3.5 Answer question

Sometimes you're asked to answer questions regarding Milestone dates, delays and project effort (see Project Milestones (Details)). Whenever a Milestone requests to answer a question, a left-sided menu item answer question is activated within your project view within ProMaSi. The project view is the page where you can see all modules for your project and is available after passing Milestone M1.3 (see Project Milestones (Details)).

3.6 Assign resource

Every module within your project (see Structure and Module List) has to be assigned to a resource (company employee). The resources are organized within departments. Also your modules are bound to a department. To assign a resource to your module you have to enter the module view (select course -> project -> module) and select the menu item assign resource from the left-sided menu. Now select a resource from the presented list by a click to the resource ID.

Note: It is recommended to agree with students of the other projects within the same company, who assigns which resource. In the next Milestone you get asked to balance the resource load. This task is much more easier if not all projects using the same resources.

3.7 Department load

Department load means to balance the resources. The goal of balancing a resource is not to over- or underload a resource. A resource has to have one ManDay effort per working day. So no parallel task are allowed. To balance a resource you need an overview, which other project is using this resource at the same time. Therefore the department load menu item on the left-sided menus within the tasks view (course -> project -> module -> tasks) exists.

Within the department load page you can see on the horizontal axis the weeks and working days. On the vertical axis you can see the resources and the assigned tasks. By changing the start time of a task (see Edit planned start), you can shift the tasks time wise.

It is recommended to have two tabs opened in your browser window. One tab shows the department load and in the other tab you can change the planned start of your tasks (see Edit planned start). ProMaSi checks if your task can be booked on this resources without any conflict (= overlapping tasks with other projects for the same resource). If there is a conflict, either choose another start date for your task (and also for all subsequent tasks) or assign another resource to this module.

3.8 Edit planned start

Changing the planned start of a task is necessary for balancing resources (see Department load). You can change the planned start of a task by a click on the task ID within the tasks view (course -> project -> module -> tasks). This possibility is available as long the task didn’t started already, as long no actual start date is visible in the taks view.

If you change the planned start of a tasks, the planned finish will be calculated automatically. Furthermore all subsequent tasks of this module will be shifted accordingly. So if you shift the planned start of the concept task, the planned start and planned finish of the prototype and final task also get changed automatically. If you change the prototype task, the final task get changed also.

3.9 Export project data

Whenever you want to export your project data to a csv-file (comma separated values) you can use the menu item export project data on the left-sided menu within your project view within ProMaSi. The project view is the page where you can see all modules for your project and is available after passing Milestone M1.3 (see Project Milestones (Details)). Exporting project data is useful for undertaking the necessary calculations for answering the questions. It is recommended to do this calculations within a spreadsheet calculation program (e.g. MS Excel).