Q1 Flashcards

(52 cards)

1
Q

is the potential of gaining or losing something of value

A

Risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Types of Risk (3)

A
  • Business risk
  • Financial risk
  • Organizational risk
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Taken by business enterprises in order to maximize shareholder value and profits.

A

Business risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

The risk that involves financial loss of firms

A

Financial risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Arises out of operational failures such as mismanagement or technical failures

A

Organizational risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Five Types of Risk in Software Project Management

A
  • New, unproven technologies
  • User and functional requirements
  • Application and system architecture
  • Performance
  • Organizational
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

The majority of software projects entail the use of new technologies. Ever-changing tools, techniques, protocols, standards, and development systems increase the probability that technology risks will arise in virtually any substantial software engineering effort.

A

New, unproven technologies

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Software requirements capture all user needs with respect to the software system features, functions, and quality of service. Too often, the process of requirements definition is lengthy, tedious, and complex.

A

User and functional requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Taking the wrong direction with a platform, component, or architecture can have disastrous consequences. As with the technological risks, it is vital that the team includes experts who understand the architecture and have the capability to make sound design choices.

A

Application and system architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Consideration must be given to benchmarks and threshold testing throughout the project to ensure that the work products are moving in the right direction.

A

Performance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Project management must plan for efficient execution of the project, and find a balance between the needs of the development team and the expectations of the customers.

A

Organizational

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Nature of Risk (2)

A
  • Internal Risk

- External Risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

These risks happen within the organization and arise during normal operations.

A

Internal Risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

These risks come from outside the organization/project and is outside of the team’s control.

A

External Risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Risk Categories (13)

A
  • Operational Risk
  • Schedule Risk
  • Budget Risk
  • Business Risk
  • Technical Environment Risk
  • Information Security Risk
  • Programmatic Risk
  • Infrastructure Risk
  • Quality and Process Risk
  • Resource Risk
  • Supplier Risk
  • Technology Risk
  • Technical and Architectural Risk
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Risks of loss due to improper process implementation, failed system or some external events risks.

A

Operational Risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Project schedule get slip when project tasks and schedule release risks are not addressed properly.

A

Schedule Risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

This risk may lead to either a delay in the delivery of the project or sometimes even an incomplete closure of the project.

A

Budget Risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Non-availability of contracts or purchase order at the start of the project or delay in receiving proper inputs from the customer or business analyst may lead to business risks.

A

Business Risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

These are the risks related to the environment under which both the client and the customer work.

A

Technical Environment Risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

The risks related to the security of information like confidentiality or integrity of customer’s personal / business data.

A

Information Security Risk

22
Q

The external risks beyond the operational limits. These are outside the control of the program.

A

Programmatic Risk

23
Q

Improper planning of infrastructure / resources may lead to risks related to slow network connectivity or complete failure of connectivity at both the client and the customer sites.

A

Infrastructure Risk

24
Q

This risk occured due to

  1. Incorrect application of process tailoring and deviation guidelines
  2. New employees allocated to the project not trained in the quality processes and procedures adopted by the organization
A

Quality and Process Risk

25
This risk depends on factors like Schedule, Staff, Budget and Facilities. Improper management of any of these factors leads to resource risk.
Resource Risk
26
This type of risk may occur when some third party supplier is involved in the development of the project. This risk occurs due to the uncertain or inadequate capability of supplier.
Supplier Risk
27
It is related to the complete change in technology or introduction of a new technology.
Technology Risk
28
These types of risks generally generally leads to failure of functionality and performance. It addresses the hardware and software tools & supporting equipments used in the project. The risk for this category may be due to — Capacity, Suitability, Usability, Familiarity, Reliability, System Support and Deliverability.
Technical and Architectural Risk
29
Risk Management Process (4)
- Identification - Analysis - Planning - Monitoring
30
Identify Risk (3)
- Uncover - Recognize - Describe
31
Review the Past Project History
Uncover
32
Assess the practices of the present project
Recognize
33
Come up with creative ideas for future projects
Describe
34
Determine how likely each risks | are to happen
Analyze the Risk
35
Possible consequence of risk in case it happens
Impact of Risk
36
Categorize the Risk (2)
- Qualitative Risk Analysis | - Quantitative Risk Analysis
37
Qualitative Risk Analysis (3)
- High - Low - Medium
38
Risk level is defined in % which does not give a very clear picture
Quantitative Risk Analysis
39
Defining preventive measures
Planning
40
depicts the different activities involved in the management of risk associated with software development.
Risk Management Paradigm
41
RMP Activities (6)
- Identify - Analyze - Plan - Track - Control - Communication
42
Before risks can be managed, they must be identified. Identification surfaces risks before they become problems.
Identify
43
is the conversion of risk data into risk decision-making information.
Analysis
44
turns risk information into decisions and actions.
Planning
45
consists of monitoring the status of risks and the actions taken to ameliorate them.
Tracking
46
corrects deviations from planned risk actions.
Risk control
47
lies at the center of the model to emphasize both its pervasiveness and its criticality.
Risk communication
48
RMMM
Risk Mitigation Monitoring and Management
49
covers efforts taken to reduce either the probability or consequences of a threat.
Risk Mitigation
50
is the process of identifying, analyzing, and planning for newly discovered risks and managing identified risks.
Risk Monitoring and Control
51
is the identification, assessment, and prioritization of risks.
Risk Management
52
documents all work performed as part of risk analysis and used by the project manager as part of the overall project plan
RMMM plan