Detailed Risk Assessment: Online Electronic Shopping Website Project

This report presents a comprehensive risk assessment for a project focused on designing and delivering an online electronic shopping website for 'Tech Online,' a client aiming to expand its reach and revenue through e-commerce. The project scope includes essential e-commerce features like product viewing, cart management, and online payment processing, with strict requirements regarding website loading speed, product quality, and revenue generation. Key stakeholders emphasize adherence to project requirements and budget, while potential risks include technical faults, hacking, and conflicts arising from requirement violations. The risk treatment methods discussed involve risk avoidance (excluding Windows platform support), risk acceptance combined with mitigation techniques, and risk transference (outsourcing specialist knowledge). The report also differentiates between risk avoidance and risk acceptance, highlighting their fundamental differences in addressing project risks, with Desklib providing access to similar solved assignments and past papers.

Running head: RISK ASSESSMENT OF PROJECT
RISK ASSESSMENT OF PROJECT
Name of the Student
Name of the University
Author Note

RISK ASSESSMENT OF PROJECT
Question1
Project Scope
Part 1:
Organisation
Design of an online electronic shopping website Date
Project Description In this project a website will be designed and delivered to the client to help
them sell electronic products online
This ecommerce website provide “tech online”, client organisation for this
project an opportunity to reach to wide range of consumers through online
platform for showcasing various electronics products and sell it online to
increase revenue
A complete ecommerce website
 Ecommerce website should have all the basic feature such as option
for viewing products online, adding product to the cart , modifying
product cart and playing online after product purchase
 Website need to load faster without delay
 To Ensure quality for the products that are sold and purchased on the
platform
 To ensure if consumers buy products or not through the platform
 Ensure revenue for the client through this online business through the
online platform designed in this project
choice of proper technology for website design is not often clearly specified
time delay and budget overflow to enhance project quality is strictly rejected
by stakeholders
stakeholders want to establish own requirement in the project
1.requirements for the project once agreed does not change while project is
being executed and if any change is required time and budget is possible to
change with client permission
2.there will be no issues regarding resource allocation and investment
throughout the project execution
3.resources required for the project will be arranged properly and client will
provide financial support for the project

RISK ASSESSMENT OF PROJECT
Key Stakeholders
violation of project requirements and project budget might lead to conflict
with the stakeholders
website might not provide best performance as intended and it might crash
as well sometime due to technical faults
hacking of the website is possible which might exploit important business
related data
28/03/2019 15/04/2019
Part 2:
Question
Design of an online electronic shopping In this project a website will be designed and

RISK ASSESSMENT OF PROJECT
website delivered to the client to help them sell
electronic products online
A complete ecommerce website This ecommerce website provide “tech online”,
client organization for this project an opportunity
to reach to wide range of consumers through
online platform for showcasing various retail
products and sell it online to increase revenue
4 laptops with i5 8gb ram, 1
TB HDD and 256GB SSD,
text editor, server for
database hosting and browser
with support for HTML5
$20,000
28-03-2019
15-04-2019

RISK ASSESSMENT OF PROJECT
Risk Treatment Methods:
1.As Windows phones occupy just a tiny portion of the world market (0.7%), and are being
deprecated by Microsoft, hence implementation of the project with integration of windows platform
increases risk for the project as it is difficult for the project to ensure success. If the project is
executed with windows platform, it might prove to be a risk for the project as the market demand is
less and it will be difficult for the application to be commercialized and it is something that no
organization wants as it lead to loss in the business. In order to mitigate risk the best possible option
is to exclude support for the windows compatibility as it will increase the cost of the project and
there is no scope for the project to ensure revenue from windows based app.
When support for windows platform is excluded it reduces the risk of poor financial performance in
the project. These type of risk treatment method is known as risk avoidance as here risk is mitigated
with elimination of a risk contributing factor to the project. When this risk factor is eliminated from
the project, associated risk in the project is reduced significantly.
2. A combination of risk acceptance and residual risk should be used as part of the risk treatment
method when a section of the project is too difficult for the company to perform. In this context, this
should be the approach.
While risk acceptance provides basis for the risk mitigation, it then needs to be treated with
possible risk mitigation techniques decided while execution for the project has to be conducted so
that the effect of the risk accepted is minimized as low as possible and the remaining risk that is
known as the residual risk should not have significant impact on the project.
When a part of a project is too difficult to execute, it is possible that the project needs to consider
risks. Now the part of the project itself being so difficult to execute, risk mitigation will be complex
as well. hence it is often required to sometime consider that risk will occur in the project which if

RISK ASSESSMENT OF PROJECT
not completely mitigated should at least be accepted so that plan and strategies are designed to
mitigate the risk and its effect on the project are minimized as low as possible.
3. When the HR department is suggested to employ someone with specialist knowledge in the area
it is intended to reduce the project risk due to lack of skill and knowledge. Hence this an example of
“Transference” as part of the risk of the project is transferred through outsourcing.
4. The main difference between “Avoidance” and “Acceptance is that in risk avoidance, strategies
are established so that it is possible to eliminate factors that are associated with project risk and in
risk acceptance, it is accepted that risk is not possible to eliminate completely but is possible to
mitigate to some extent. Hence in risk avoidance the primary focus is to develop techniques and
plans which eliminates the risk factor so that risk in the project is avoided. However, in risk
acceptance the main focus is to design and develop techniques and strategies so that effect on the
project is minimized. Therefore these two risk treatment techniques have some fundamental
difference.