Learning Environment Project Assesment

Purpose of the Course Project: Solving a business problem for someone who is receptive to your recommendations is an excellent way to improve your professional effectiveness and get ahead. Learning how to identify problems and propose solutions will benefit you now and in the future. The Final Project Report should conform to your text’s Ch. 10 guidelines of how to write a formal report. Note that the format is quite different from an academic paper. (spacing, graphics, each section begins new page) The Groupon example for Cali’s Low-Fat Frozen Yogurt in the Ch. 10 of the text is a good model to follow. Directions for Final Paper: 1. Consider how best to present your findings on this opportunity for the organization, the viable alternatives, the benefits and risks, and your strategic recommendations. 2. Follow this basic outline for the Formal Project Report. Refer to Ch. 10 for a more detailed guide and expectations for the Formal Report 

Running head: PROJECT
Project
Name of Student
Name of University
Author Note

1
PROJECT
Executive Summary
The paper provides an idea of the key problem that HCC is currently facing. HCC is known for
providing an excellent learning environment to the students. The A.S Division of the college is in
charge of the computer labs. The main problem that this paper aims to solve, is related to the
difficulty in fulfillment of the service requests in times, when technical issues are faced in the
lab. The paper provides a comprehensive idea of the problem and proposes a solution to the
problem. The solution that is proposed is to develop of a suitable software system that will track
all the service requests related to the technical issues that are faced in the computer labs. The
report provides a brief idea of the implementation plan prepared for development and the launch
of the proposed software system and outlines the recommendations for successful project
implementation.

2
PROJECT
Table of Contents
1. Introduction......................................................................................................................3
2. Opportunity......................................................................................................................4
2.1. Current Situation.......................................................................................................4
2.2. Key Success Factor...................................................................................................4
3. Benefits and Risks of Strategic Solution.........................................................................5
3.1. Benefits.....................................................................................................................5
3.2. Risk...........................................................................................................................6
4. Final Recommendations..................................................................................................7
4.1. Implementation Plan.................................................................................................8
Bibliography......................................................................................................................10

3
PROJECT
1. Introduction
The Hillsborough community college was founded in the year 1968 as a part of the 28-
member Florida College system. It is dedicated in creation of an engaging environment for the
students and educated more than 47,000 students each year. The college is supported by 2200
dedicated faculty and staff members (Hillsborough Community College, 2020). The mission of
the organization is to transform the lives of students by giving them an access to an exceptional
teaching as well as learning environment. The vision of the college is to promote a thriving
community for students to achieve full potential by providing an access to an affordable,
innovative and high quality education.
The A.S division of HCC is in charge of the computer Labs on the whole college campus.
When there is a need of handling the technical issues, a technician is called to solve the technical
issue. However, the current system is not able to track the resolutions to each email and the
manual process is time consuming as well. Therefore, it is necessary to develop a system which
will help in easier tracking of the similar services in future. The main problem of the existing
system is that there is an uncertainty about information being confidential and therefore, there is
a need of analyzing and finding solution to the current situation.
As a solution to the current problem, a software system can be developed and installed to
place service request to the technicians. The technicians will accept the service request on the
portal and provide a suitable time for resolution of the problem. On basis of the same a service
ticket will be generated which will remind the technician about the date and time allocated for
the completion of the work through email and text messages. The service ticket will be closed

4
PROJECT
only after completion of the service request. This will help in easier tracking of services
requested.
2. Opportunity
In the following sub section, the current situation and the key success factor of the
proposed solution is discussed.
2.1. Current Situation
The current situation deals with the problem of lack of a proper system that can track the
service requests. The AS division is in charge of the computer labs on the whole college campus.
The main problem is that when a service is requested, proper follow up is not taken, which
increases the complexity as the technical difficulty might or might not be solved in time.
Therefore, development of a software system is proposed which will enable the AS division to
keep a track of the service request and will help in timely solving of the technical difficulties that
are being faced in the computer labs (Zavattoni et al., 2014). The system should also be able to
maintain the confidentiality of the information and therefore, adding password protection to the
portal to be designed, becomes a necessity. The following sub sections outlines the key success
factors that will ascertain successful project execution.
2.2. Key Success Factor
The success of project will be determined by successful fulfillment of the following
factors related to development of the online software system in HCC. The key success factors are
indicated as follows-

5
PROJECT
1. All the identified goals of the project are needed to be fulfilled to ensure project
success.
2. The project is completed within the allocated time (Khan & Keung, 2016).
3. The software system that is developed is able to address the current problem and will
be able to provide a feasible solution.
4. The system is able to track the service request and the technical issues are solved in an
effective manner.
The fulfillment of the above four success factors will ensure successful project execution
and completion.
3. Benefits and Risks of Strategic Solution
The proposed solution will be able to solve the technical difficulties of HCC computer
Labs in a timely manner. The benefits and risks are indicated as follows-
3.1. Benefits
The key benefit of the proposed system are indicated as follows –
1. The system will be able to solve the problem of difficulty in tracking the service
requests associated with handling the technical issues.
2. The success of the project will help in easier tracking of the services and the resolution
to each main.

6
PROJECT
3. The automated software system will manage and store the details of all the service
requests thus replacing the manual system (Al-Shargabi & Sabri, 2015). This will help in saving
time.
4. The lab supervisors and all the faculty members will largely be benefited by the
proposed system as the key problem associated with the existing system will be solved. All the
key stakeholders of this project will be benefited by the successful completion of the project.
The above four points indicate the key business benefit that can be realized with the
implementation of the system. However, there are certain risks that can affect the normal
execution process of the project which are indicated in the following subsection.
3.2. Risk
Presence of certain risk can affect the normal execution and completion of the project
(Kliem & Ludin, 2019). The following risk register provides an idea of the key project risks,
their probability and impact on the project along with the mitigation approach of each of the
identified project risks.
Risk Description Probability of
Occurrence
in the Project
[On a scale of
1-3]
Impact
of the
Risk [On
a scale of
1-3]
Risk
Score
Mitigation Strategy
Technical
Risk
The technical
issues might
arise while
2 3 6 The entire project is
needed to be
supervised and for

7
PROJECT
designing the
proposed
software system
that a technical expert
will be hired to look
after the entire project
execution process.
Time Issue The project is a
high priority
project and
therefore cannot
be delayed
1 2 2 The time issue can be
addressed by
allocating maximum
resources to a task
and by ensuring
timely resource
availability.
Resource
Issues
The lack of
timely resource
availability can
risk the timely
project
completion
2 2 4 The resource issue
can be mitigated by
ensuring no resource
over allocation
Resistance
to learning
new System
The project
might fail if the
users refuse to
make use of the
new system
1 3 3 The staffs and the
stakeholders are
needed to be educated
about the benefits of
the proposed system
to mitigate this risk.

8
PROJECT
Table 1: Demonstrating the Risks with the project and its mitigation strategy
4. Final Recommendations
On analysis of the current situation and the benefits of the proposed solution, the
following recommendations are made-
1. It is necessary to develop a realistic project plan to ensure timely execution of the
project
2. A user acceptance testing is recommended to be done, prior to the release of the
system.
4.1. Implementation Plan
The implementation plan for the proposed project are indicated in the table below
Task Start Date End Date Comments
Problem Definition Mon 03-02-20 Tue 04-02-20 The key problem is
identified in this
stage
Analysis of the Issues
and Problems
Wed 05-02-20 Thu 13-02-20 The problems are
analyzed to propose a
suitable solution
Identification of the
Solution
Fri 14-02-20 Thu 20-02-20 The suitable solution
to the existing

9
PROJECT
problem is identified
Preparation of
Business Case
Fri 21-02-20 Tue 25-02-20 The business case for
the proposed system
is prepared
Development of
Project Plan
Wed 26-02-20 Tue 03-03-20 A detailed project
plan is prepared after
approval of business
case
System
Implementation
Wed 04-03-20 Tue 14-04-20 The software system
is developed
System Testing Wed 15-04-20 Wed 15-04-20 The software system
is tested
User Acceptance
Testing
Wed 22-04-20 Wed 22-04-20 User acceptance
testing is completed
System Launch Wed 06-05-20 Wed 06-05-20 The system is
launched
Feedback Collection Thu 07-05-20 Wed 13-05-20 Feedback is collected
from users.

10
PROJECT
Bibliography
Al-Shargabi, B., & Sabri, O. (2015, September). An evaluation of MIS implementation success
factors. In Proceedings of the The International Conference on Engineering & MIS
2015 (pp. 1-3).
Elzamly, A., Hussin, B., Abu-Naser, S. S., & Doheir, M. (2015). Classification of Software
Risks with Discriminant Analysis Techniques in Software planning Development
Process.
Hillsborough Community College. (2020). Retrieved 19 February 2020, from http://hccfl.edu/
Khan, A. A., & Keung, J. (2016). Systematic review of success factors and barriers for software
process improvement in global software development. IET software, 10(5), 125-135.
Kliem, R. L., & Ludin, I. S. (2019). Reducing project risk. Routledge.
Permana, P. A. G. (2015). Scrum method implementation in a software development project
management. International Journal of Advanced Computer Science and
Applications, 6(9), 198-204.
Zavattoni, E., Perez, L. J. D., Mitsunari, S., Sánchez-Ramírez, A. H., Teruya, T., & Rodríguez-
Henríquez, F. (2014). Software implementation of an attribute-based encryption
scheme. IEEE Transactions on Computers, 64(5), 1429-1441.