Risk identification: Use the table above as a “checklist” to identify some specific risks for the Web project.

Information Technology Project Management
9th Edition
ISBN:9781337101356
Author:Kathy Schwalbe
Publisher:Kathy Schwalbe
Chapter5: Project Scope Management
Section: Chapter Questions
Problem 3QQ
icon
Related questions
Question

Assignment Two: Web Process and Project management: Project Risks

Student Name:

ID:

Look at the table below, which are concerned with WEB Project Risks. In here, you are going to consider project risks that you might encounter, or wish to avoid, in developing 3-tier Banking Application. Assume that the development is being done by a Simi-established team, which has done this sort of development before (some are new). Answer the following questions:

 

Characteristics

Descriptions (Risks)

Content

· Lack of understand the structuring of content.

· No explicit define about the standard of project qualities.

Navigation

·Difficult to navigate and finds problems.

· Too large volume of information contains.

Presentation

· Difficult in operate and simplicity.

· Lack of the aesthetic used in content

Social Context

· Difficult in define content and functional requirement.

· Hard to term possible threaten from competitors

Technical Context

· Complexity of designing models increases by using mobile devices.

· Lack of understand delivery medium concept

Natural Context

· Time and location from where the applications were access could not be predicting.

· Meet user’s expectation to have accessibility around the clock.

Development Team

· Lack of development concerning on safety, security, reliability.

· Build on emerging technology and methodology.

· Web developers have variety of background, experience and age.

Technical Infrastructure

· The inhomogeneity and immaturity of used components

· Hard to predicted operational environment.

Process

· Lack of define user categories.

· Continually change project/scope/ objectives

Integration

· Many external suppliers involve in the development project.

· Legacy systems are poor documented.

 

  1. Risk identification: Use the table above as a “checklist” to identify some specific risks for the Web project.

 

 

  1. Risk analysis: Discuss the likelihood of each risk (low, medium, high). For each risk, decide what sort of effect it would have if it were realised (minimal, acceptable, serious, critical).

 

  1. Risk analysis: Discuss the affects of each possible risk (Project, Product, and Business).

 

  1. Risk planning: For any risk that is serious or critical, and for risks with a moderate to high likelihood, consider how project planning can reduce the likelihood of that risk or mitigate the effect.
Expert Solution
steps

Step by step

Solved in 3 steps

Blurred answer
Knowledge Booster
Business Analysis Strategies
Learn more about
Need a deep-dive on the concept behind this application? Look no further. Learn more about this topic, computer-science and related others by exploring similar questions and additional content below.
Similar questions
  • SEE MORE QUESTIONS
Recommended textbooks for you
Information Technology Project Management
Information Technology Project Management
Computer Science
ISBN:
9781337101356
Author:
Kathy Schwalbe
Publisher:
Cengage Learning
Principles of Information Systems (MindTap Course…
Principles of Information Systems (MindTap Course…
Computer Science
ISBN:
9781285867168
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning
Principles of Information Systems (MindTap Course…
Principles of Information Systems (MindTap Course…
Computer Science
ISBN:
9781305971776
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning