University Café Control System: Project Management Report

This report details the project management aspects of developing a cloud-based cafe control system for a university. It begins with a description of the original project plan, which involved implementing a system for a 24-hour cafe with various food and drink options, integrated with the university's automated student enrollment process. The report then discusses the changes to the initial plan, including the challenges of a bankrupt company and the subsequent adoption of an agile methodology. The project explores learning experiences gained through observation, concept development, and testing. A key focus is on risk planning strategies, addressing financial, time-related, connection, implementation, staffing, security, and system disruption risks. The report provides a detailed table outlining risk descriptions, avoidance methods, transfer strategies, mitigation approaches, and acceptance strategies for each identified risk. References to relevant sources support the analysis.

Running head: PROJECT MANAGEMENT
Development of café control system
Name of the Student
Name of the University
Author Name

1
PROJECT MANAGEMENT
Table of Contents
Description of the original plan..................................................................................................2
Changing of plan........................................................................................................................2
Learning experiences.................................................................................................................3
Risk planning strategies.............................................................................................................4
References..................................................................................................................................8

2
PROJECT MANAGEMENT
Description of the original plan
According to the case project, it needs to develop a system for a dining café for the
university which will open for 24 hours. There will have various kinds of foods as well as
drinks in the dining café (Bansal & Desai, 2017). No extra charges will be taken with all
foods and drinks because the food charges will include in the annual residence charge. The
university wants to install a cloud based system for this dining café though it have so many
physical devices. But the main advantage of the cloud based system is that it does not require
to take any additional maintenance of the physical devices of the dining café (Curry & Lynch,
2015). Another advantage is that it is in relation with automatic enrolment process for the
students. The students are filling their applicants over the internet which process is totally
automated. For implementation of this project, a number of stakeholders such as project
manager, finance manager as well as technical manager are required. In this way, the overall
process of this project will be done.
Changing of plan
Sprint is one kind of time based iteration along with a nonstop development cycle.
This methodology is full of work and the overall process of the work must complete within
the time period. This methodology undergoes within the Agile process.
According to the case project, in the initial time, this project has been handled by a
company which was bankrupt due to some problems. For that, the project was rejected. There
was no other employees of that company to take this project for the execution purposes. So,
this project has handover to another company. For the completion purpose, if the company
wants to follow up the strategies related to previous company then it needs to install two
cards that is swipe cards and another is special access cards. For the swipe cards, the cost will
estimate $12,000 and the time needs to take 4 weeks (BANSAL & Desai, 2019). For another

3
PROJECT MANAGEMENT
card that means special access cards, the estimated cost will be at $5,000. For that case, the
time will take 8weeks. But if the company wants to develop a new system, then for set up,
training as well as orientation for the new system, the budget will higher than the previous
cases that means $30,000. In the new system, the following students can be identified through
red light trigger by these cards if they have any food allergies and in that cases, the anti-
allergen food are provided to that students (Davne et al., 2014). All of the cards are accessed
by the fingerprint recognition. In this way, the new plan has been developed for execution of
this project.
Learning experiences
Mainly the learning experiences has been achieved through few steps. In the first step,
the responsibility of a team is to make an experience about the case project. Then they has to
move in the observation as well as reflections stage for proper observation of the project
(Helo et al., 2014). After that, the team has to develop such concepts that are related to the
case project and at the last stage, the team members have to move the testing stage to execute
the project related concepts. In this way, the project has been completed by the team
members.
According to the case project, the university wants to develop a café control system in
its institute which must be a cloud based system. The café will open for 24 hours for the
university students and the students can handle the café control system over the internet.
However, the café control system consists of various advantages including no extra chargers
for food, anti-allergen foods for particular students having food allergy, 24hours food
availability etc. At the initial time, the project team should gather experiences related to this
case project (Kumar & Pollutro, 2015). Then the duty of the project team has to observe the
case properly so that they can understand in which process the case project is executed. And

4
PROJECT MANAGEMENT
also, they have to follow about the reflections of this case project. In the third step, they have
been developed the concepts for the project execution purpose (Raphel et al., 2014). This step
is vital for managing the project in a right way. If the project team takes any wrong decision
about this project, then the project will not be considered as feasible depending budget as
well as timeframe. At the previous case of this project, the previous company was failed to
develop this project because they were bankrupt for taking wrong decision on this project. So,
in the present case, the team has to maintain the proper decision making for completion of the
project within the budget and timeframe (Singh et al., 2015). In the last step of the project
development cycle, the project team must execute the planning as well as concepts related to
the case project which they were developed for this project. The testing process should
maintain a right strategy, so that the project can complete properly.
Risk planning strategies
The table shows the risk planning strategies that are given as below:
Risk Id Risk
description
Avoid Transfer Mitigation Acceptance
1. Financial risk If the
company
follows the
previous
concept
provided by
previous
company,
then the
The project
team must
transfer their
concepts ton
the previous
concepts.
The project
team must
maintain the
continuation
process
provided by
previous
company
The project
team should
accept the
previous
concepts
provided by
the previous
company.

5
PROJECT MANAGEMENT
financial
risk can be
avoided
2. Time-related
risk
If the project
manager
will take the
decision in a
right time,
then this risk
can be
avoided.
The overall
process will
transfer into
a model that
has several
small
sections for
avoidance of
this project
risk
The project
team must
maintain the
proper
decision
making, then
this risk can
be mitigate.
If the
concept of
dividing a
big process
into small
sections will
be
developed.
3. Connection
related risk
If the overall
process of
the system
will sustain
with a
speedy
internet
connection
then this risk
can be
avoided
The system
should
undergo in a
high speed
internet
connection.
Always it
needs to
secure the
internet
connection
of this
system.
The high
speed
secured
internet
connection
can be
accepted.
4. Ease of The system The The system The easy

6
PROJECT MANAGEMENT
implementation will design
in an easy
way, so that
all the staffs
as well as
students can
handle the
system
designing
process of
the system
will transfer
within an
easy process
must
implement in
an easy
process.
designing
process will
be accepted
for this
system.
5. Involving
staffs in
checking
purpose
The shifting
process will
be designed
for the staffs
The staffs
are selected
as per their
shifting
hours
The shifting
structure
needs to
install
The shifts
are designed
with
particular
timeframe.
6. Security needs Maintain
proper
security.
The system
will transfer
in a security
system
Cyber
security
must be
installed
The security
system will
be accepted
7. Crushing with
another system
The
development
of the
system
should
maintain a
proper way.
The
designing
process of
the system
should be
unique.
It needs
proper
development
The system
should be
developed in
a technique
so that it
cannot crush
with another
system

7
PROJECT MANAGEMENT
8. Disruption of
system
The correct
software and
algorithms
are
developed
The system
should
undergo
within
correct
algorithm
It needs to
develop
proper
algorithm
The system
should be
developed
within right
algorithms.
9. Updating the
system
The system
will update
for 24 hours
The system
will transfer
in an auto
update
process
Requirement
for updating
every
moment
The system
will accept
with
updating
process

8
PROJECT MANAGEMENT
References
Bansal, A., & Desai, P. (2017). U.S. Patent Application No. 15/377,126.
BANSAL, A., & Desai, P. (2019). U.S. Patent Application No. 10/225,740.
Curry, S. L., & Lynch, S. P. (2015). U.S. Patent Application No. 14/549,500.
Davne, J., Volkov, A., Yankelevich, M., & Malamud, M. (2014). U.S. Patent No. 8,910,278.
Washington, DC: U.S. Patent and Trademark Office.
Helo, P., Suorsa, M., Hao, Y., & Anussornnitisarn, P. (2014). Toward a cloud-based
manufacturing execution system for distributed manufacturing. Computers in
Industry, 65(4), 646-656.
Kumar, S., & Pollutro, D. (2015). U.S. Patent No. 9,027,125. Washington, DC: U.S. Patent
and Trademark Office.
Raphel, J., Kailash, K., Apte, M. S., & Chaudhry, J. S. (2014). U.S. Patent No. 8,806,593.
Washington, DC: U.S. Patent and Trademark Office.
Singh, J., Pasquier, T., Bacon, J., Ko, H., & Eyers, D. (2015). Twenty security considerations
for cloud-supported Internet of Things. IEEE Internet of things Journal, 3(3), 269-
284.