Running head: SBRU RISKS

Spring Breaks R Us Project Risks and Feasibility

Aaron Hall
Group A
Walden University

Spring Breaks R Us Project Risks and Feasibility

Development projects must be evaluated for potential risks as well as feasibility. The
project for Spring Breaks R Us possesses risks in several key areas. The extent to which the
risks associated with a project can be mitigated determines the feasibility of the project. While
concerns exist in several areas, I believe the project is feasible as long as the project team
monitors and manages the risks throughout the term of the project.
Identified Potential Risks
The proposed changes to SBRUs system represent a significant shift in how the
company performs its work. When employees face changes to their day to day workflows,
organizational risks must be considered. Each company has its own culture, and any new
system must be accommodated to that culture (Satzinger, Jackson, and Burd, 2012, p. 269).
Failure to allow for possible cultural impact at SBRU will cause measurable risk to the success
of the project. In addition to cultural impact, the technological requirements to execute the

SBRU RISKS

project also carry risk. The company must have the expertise available for the project, define a
clear training process for employees, and understand how the new system impacts the current
infrastructure. These needs directly correlate to resource requirements. The greatest resource to
the project is people. Required people may not be available to the team at the necessary times,
and people assigned to the team may not have the necessary skills for the project (Satzinger, et.
al., 2012, p. 270). Finally, these and other factors create risks to the schedule for the project.
SBRUs operations are at their peak during the spring, and the timeline for the project must fall
between the booking seasons. The capacity of the current staff is also an unknown which may
limit availability for interviews, testing, and feedback on the work throughout the project plan.
In order to insure feasibility of the project, all risks must be considered and managed. The table
below lists the potential risks I identified in the four key areas.
Aaron Hall
Risk Category
Organizational Risks

Technological Risks

Resource Risks

Potential Risks
Changes in long-standing work procedures could create a
culture shock internally
Fear of loss of employment due to automation in resort
relations Fewer representatives will be required
Potential power shift dues to changing responsibilities
Individual reps will not be keepers of information in the new
system; it will be accessible to all
Perceived loss of control Interaction with students will be
automated more meaning less responsibilities to booking reps
Potential shortage of expertise to configure and deploy/build
the new system
Need for training staff on the new system
Hardware issues based on new demands interoperability,
necessary upgrades
Hardware requirements for ongoing communication of the
project to all stakeholders Resorts are remote (not local)
Potential shortage of team members for the project and their
availability

SBRU RISKS

Schedule Risks

Employees with inappropriate level of skill to use the new

system
Adequate infrastructure to support the new system
The capacity of the staff is an unknown at this point
Scheduling deadlines The booking season for spring break
could affect the feasibility of beginning the project and
completing it in time
The potential risk for schedule slippage and how it can affect
timeline and deliverables
The availability of stakeholders for capturing necessary use
cases could impact the schedule at each phase

Project Feasibility
The risks detailed in the table above can be managed by the project management team.
As Satzinger, Jackson, and Burd argue, the project management team can take positive steps to
counter them (2012, p. 270). I recommend a high level of user involvement based on the
potential cultural risks with the project. The amount of buy in by employees is paramount to a
successful process. The technological risks should be addressed as early as possible. A
thorough investigation of current systems, hardware, and facilities must be conducted during the
project approval process. This evaluation protects the project against failure. The same holds
true for the required resources for the project. A preliminary understanding and assessment of
needs will make sure resource constraints do not threaten the success of the plan. The most
important aspect of the development project for SBRU is the schedule. The companys business
is seasonal, and poor scheduling could cause conflict with operations. A properly planned kickoff- during the appropriate time of the year- manages concerns around timing and deployment.
Conclusion
All projects possess risk. Proper planning and evaluation can remove concerns around
the feasibility of a development project. In the case of SBRU, the team has an opportunity to
identify risks early and put safe-guards in place to insure successful completion of the new
systems. While I believe the project is feasible, I believe the company should consider working

SBRU RISKS

on the most critical business needs in the first iterations in case problems arise that could threaten
deliverables.

SBRU RISKS

Group Top Ten Risks

Risk Category
Organizational Risks

Technological Risks

Resource Risks

Schedule Risks

Potential Risks
Fear of loss of employment due to automation in resort
relations Fewer representatives will be required (poor
morale)
Potential power shift dues to changing responsibilities
Individual reps will not be keepers of information in the new
system; it will be accessible to all
Perceived loss of control Interaction with students will be
automated more meaning less responsibilities to booking reps
Potential shortage of expertise to configure and deploy/build
the new system (Need for vendors)
Need for training staff on the new system
Hardware issues based on new demands interoperability,
necessary upgrades
Potential shortage of team members for the project and their
availability (Hiring needs)
Employees with inappropriate level of skill to use the new
system
Adequate infrastructure to support the new system
Scheduling deadlines The booking season for spring break
could affect the feasibility of beginning the project and
completing it in time

Craig Malsona
Risk Category
Organizational Risks
Technological Risks

Resource Risks

Scheduling Risks

Potential Risks
Fear of changing job responsibilities
Outside Vendor Issues Who is the expert, is the request too
much for a vendor, hiring more people and training them
(making sure not to hire too many)
How many people to hire Are they full time or consultants,
do the employees have the required skills, do we have the right
equipment
Will they finish on time, do they have the time to do all the
research needed

SBRU RISKS

Andre Pettis
Risk Category
Organizational Risks
Technological Risks
Resource Risks
Scheduling Risks

Potential Risks
Poor morale of employees with technology taking over
positions
Malware and Hacking potential to either booking or student
interface
Potential waste of resources creating a new social media
network
Not enough time to prepare for season and become profitable

Martin Chabarria
Risk Category
Organizational Risks
Technological Risks
Resource Risks
Scheduling Risks

Potential Risks
No data posted at time of project submission

SBRU RISKS

7
Reference

Satzinger, J., Jackson, R., & Burd, S. (2012). Systems analysis & design in a changing world (6th
ed.). Boston: Course Technology, Cengage Learning.