Project Plan V3

ProP Group 3 – Fyre Music Festival (FMF)

Project Versions
Version:

1. Draft project plan, consists of project statements which has problem description and
Moscow List (deliverables), as well as Project phasing and a critical path diagram.

2. Improved version, added a project goal as well as a more detailed Moscow List
(deliverables), furthermore a section about risks and constraints was also added in the project
statement.

3. Added a project justification as well as an even more improved Moscow List

(deliverables).

2|Page
 Project Statement
Client: Mr. Andre Postma

Team:

1. Edgaras Spridonovas

2. Rafael Aditama Karno

3. Cristin Rusnac

4. Abraham Nataniel

Task Distribution:

Task Executor
Web Wireframe All members

Web Design (Static) Cristin, Rafael, Edgaras

Programming Functionalities (C#) Edgaras, Abraham

Documentation Abraham, Rafael

Database Design All members

Problem Description:

A commercial company that is specialized in organising events has asked us to make a software solution
so that managing events are easier. This is the result of the rapidly increase in popularity of the events
that are advertised by this company, hence it has become nearly impossible got them to manage these
events without having a proper software solution. The company were wondering whether it is possible
to make a software that not only solves their problem in managing the events but also user friendly as
well as easy to use.

Project Goal:

The goal of this project is to create a website with multiple implemented functions. The minimal
requested functions are as follows; A website that informs people of the event and allows reservation of
tickets and camping spots, applications that not only allows visitors to check-in and check-out but also
supporting shops and loan stands. Furthermore, our client wants an application that allows the
organisation to get a clear status overview of the ongoing event. A database supporting all applications is
a must and last but not least an application that changes the balance of the visitors according to certain
logfiles.

Project justification:
3|Page
This project is about creating a software solution for a client to manage as well as organize thousands of
people easily during a certain event. We do believe that a proper and yet user-friendly software solution
is needed in order to manage and organise an event that is this big, where many employees and workers
are needed, let alone the thousands of people that will be participating in the event. This software will
allow the client to have an overview of the current situation of the event as well as track the activities
that are happening of both visitors and employees, such as how many visitors are there, what items have
been bought, etc. This software will be a better way to manage this event compare to the conventional
method that client is using.

4|Page
 Deliverables:

Deliverable Must Have Should Have Could Have Won’t Have

Festival’s Website:

Have many related pages (Home,

Tickets, Artists, Info, Profile, Sign-
up)

Check in and Check out:

Application to manage check-in

and check-out

Check-in and check-out time is

dependant by the tickets

App to loan stands:

Different stands every day

Status overview app:

Track how many people are in the

festival

Track visitors status and history

Track total visitors

Track how many employees are in

the festival

Track borrowed items

Track transactions

5|Page
Track total money sold per shop

Track total amount of a certain

product are sold

Track total balance of all visitors

Track total money spent

Track free and booked camping

spots

Database supporting all apps

ATM app:

ATM is available at both website

and on site

Tickets for the festival:

More than one type of tickets

Each tickets produces its own

unique ID-numbers (static
numbers)

One type of tickets

Logfiles for transactions

App to borrow extra equipment

Camp area size are definite

Camp location in first page

Risk and Constraints:

Deliverables Risk

6|Page
Check in and Check out People might not check-in or check-out

Status overview app Software might crash due to data overload

Database supporting all apps Relationships might not be set up perfectly and
data loss might occur

ATM app People might see the account number of another

person

Refundable Tickets Refunds may take a while to return

Refundable Camp reservations Refunds may take a while to return

App to borrow extra equipment Equipment might not be given back by the
borrower

Possible constraints:

1. Client’s expectations:

We, of course, need to manage the client’s expectations because there is a possibility that we
might not be able to do everything that he/she requested, hence expectations must manage in
such a way that the task is not too overbearing for the team but satisfies the client.

2. Time limit:

We have limited time for this project, hence time is of the essence and needs to be managed
properly so that we can use it well to ensure that this project is successful.

3. Limited Resources:

Apart from limited budget, we are also limited on human resources, thus this project will require
the full attention as well as cooperation of all members of the group.

Project Phasing:
Task Time Blocks

7|Page
Name and Logo Week 1

Web Wireframe Week 2

Web Design static Week 3-5

Database Design Week 5-6

Functionality Implementations If possible, along the weeks in block 1

Critical Path Diagram

8|Page