# Project Management

Delivered to you by Marlon Lannoy and Tanno Quintens

## Assignment 1: PlayStation 5

### PERT
The length of the critical path is 22.

The original image can be found as 'Assignment_1_PERT.PNG'.
### Gantt
Various tasks can be delayed to keep the critical path on track.

The original image can be found as 'Assignment_1_Gantt.xlsx'.
## Assignment 2: Webshop

### WBS
The WBS can either be found in the corresponding PDF file or via the following url (sign in is needed):

https://planhammer.io/project/5ebf0a67a0610b25040338de/show/detailed

### Risk Management

* #### Availability of internal testers during test periods is not guaranteed
Size of Risk = likely (50%) x moderate
It's likely this risk will take place and if it happens the consequence will be moderate.

A possible resolution would be to transfer the risk and hire external testers.

* #### Tests with payment institution will not go as expected
Size of Risk = unlikely (10%) x significant
It's not likely this risk will take place but if it happens the consequence will be significant.

A possible resolution would be to prevent this risk by making sure the application to the relevant payment institution(s) is taken care of beforehand.

* #### A developer can leave the project for various reasons
Size of Risk = unlikely (15%) x significant
It's not likely this risk will take place but if it happens the consequence will be significant.

Depending on the stage the project is in when the developer leaves, there are various solutions.
If the problem arises in the beginning of, or halfway through the project:
1. You could reduce the impact of the risk by making sure the project is well documented.
2. Another way of reducing the impact is to hire an extra external developer throughout the project.

If the problem arises near the end of the project, it may be a better choice to accept the impact of the risk and not hire a new developer. Since this might cause more delays (training, catching up with the project).

### Project Planning

| | Activity | Time (days) | Follows |
|----|-------- | -------- | -------- |
|A| Defining Project Scope|6|-|
|B| Analyzing User- & (Non-)Functional Requirements|3|A|
|C| Design Application Architecture|2|B|
|D| UI Wireframe|5|B|
|E| Design Payment System|2|C|
|F| Design Database|2|C|
|G| Design Security Plan|2|C|
|H| Database Realisation|20|F|
|I| Developing Back-end Architecture|30|E,G,H|
|J| API Implementation|10|I|
|K| Developing CMS|18|J|
|L| Developing Shopping Cart System|15|J|
|M| Developing Payment System|12|J|
|N| Developing Delivery System|10|L,M|
|O| Integrating Shopping Cart, Payment and Delivery System|12|N|
|P| Functional Testing|18|O|
|Q| Main Front-End Implementation|15|D,J|
|R| Developing Shopping Cart and Payment System UI|12|L,M,Q|
|S| Developing Delivery System UI|5|O,R|
|T| Developing CMS UI|5|K,Q|
|U| UI Testing|12|S,T|
|V| Integration Testing|10|S,T|
|W| Mobile Optimization|2|U,V|
|X| Pilot Deployment|2|W|
|Y| Acceptance Testing|20|X|
|Z| Final Deployment|4|Y|

#### PERT
The length of the critical path is 92.

The original image can be found as 'Assignment_2_PERT.PNG'.

#### Gantt

The image can be found as 'Assignment_2_Gantt.xlsx'. The dimensions are too big for giving a clear overview.