CH05. L06. Project and product risk

Summary

This video script delves into the concept of 'Risk' in project and product management, emphasizing its unpredictability and impact. It outlines the main objective of testing as identifying defects and reducing risks, distinguishing between project risks, influenced by organizational, technical, and supplier factors, and product risks, which pertain to post-deployment challenges. The script highlights the test manager's crucial role in mitigating these risks through proactive risk identification and management strategies, ultimately aiming to decrease product failure and enhance quality.

Takeaways

• 🔍 Risk is defined as an unexpected event with identifiable levels based on the probability and impact of adverse outcomes.
• 📊 The main objective of testing is to discover defects, reduce risks, and determine the start, continuation, and end of the testing process.
• 🏗️ Project risk involves risks that affect the project's ability to meet its objectives, categorized into Organizational, Technical, and Supplier factors.
• 👥 Organizational factors include skill shortages, personal issues, political issues, and a lack of respect for the test team's efforts.
• 💻 Technical issues encompass incorrect requirements, unprepared test environments, and low-quality design, code, and test data.
• 🛠️ Supplier issues arise when third-party components or tools lack support, causing work stoppages and technical problems.
• 👨‍💼 The test manager is responsible for using project management skills to analyze, manage, and mitigate all identified risks.
• 📝 The test manager should document test plans, requirements, and contingencies in the summary report according to IEEE standards.
• 🛡️ Post-deployment, product risks include potential failure areas, poor product quality, data integrity issues, and failure to meet intended actions.
• 📉 Testing should lead to a decrease in risks, with continuous feedback to address and reduce problems in the product.
• 🛑 A proactive risk-based approach is essential from the initial stage of a project to reduce product risk levels.
• 📋 Risk identification is crucial for determining which parts of the product may cause bugs, prioritizing tests, and employing non-testing activities to improve quality.
• 🤝 Risk-based testing ensures that all stakeholders are aware of expected risks and the necessary testing to mitigate them.

Q & A

What is the definition of 'risk' as discussed in the video?

Risk is defined as any event that is unexpected to happen, which can be identified according to the probability of the adverse event or the impact caused by this event.

What is the primary objective of testing in the context of risk management?

The main objective of testing is to find defects, decrease risks, and determine when to start, continue, and stop the testing process.

How is risk categorized in the context of a project and a product?

Risk is categorized into 'project risk', which refers to risks affecting the project's ability to deliver objectives before completion, and 'product risk', which refers to risks after the project is deployed and becomes a product.

What are the three factors that contribute to project risk?

The three factors contributing to project risk are Organizational, Technical, and Supplier factors.

Can you explain the Organizational factor in project risk?

The Organizational factor includes issues such as skill shortages, personal conflicts within the team, political issues affecting communication, and a lack of respect or improper attitude towards the test team's efforts.

What are some examples of Technical issues that can contribute to project risk?

Technical issues include incorrect requirements, constraints preventing meeting requirements, unprepared test environments, late data conversion, and low-quality design, code, configuration data, test data, and tests.

What does the Supplier factor in project risk entail?

The Supplier factor involves issues with components or tools obtained from outside sources, including lack of support or training, and problems arising from using outdated or unsupported tools.

Who is responsible for addressing the risks identified in a project?

The test manager is responsible for addressing the risks, utilizing high project management skills to analyze, manage, and mitigate all risks.

What should the test manager include in the summary report according to IEEE standards?

The test manager should include what the test plans require and what the contingencies are in the summary report.

What are potential failure areas in the context of product risk?

Potential failure areas refer to adverse future events or hazards that can affect the quality of the product, including issues in functionality, reliability, usability, performance, and data integrity and quality.

How does testing help in managing product risk?

Testing helps in managing product risk by identifying where to start testing, where to test more, and reducing the adverse effects or impact of potential issues through feedback and continuous improvement.

What is the importance of risk identification in the risk-based approach?

Risk identification is crucial as it helps in determining which parts can cause bugs and form product risks, prioritizing important parts for suitable solutions, and implementing actions to reduce the product failure percentage.

What are the four important aspects identified through risk identification?

The four important aspects identified through risk identification are the test techniques needed, the extent of testing to be done, prioritizing tests to find critical defects early, and non-testing activities that can reduce risks, such as team training.

Why is it important for stakeholders to be aware of expected risks in risk-based testing?

It is important for stakeholders to be aware of expected risks so that they understand the required testing that will be relied upon to face these risks, ensuring that there are ways and solutions in place to reduce uncertainty about potential problems.

Outlines

00:00

🚧 Project and Product Risk Management

This paragraph introduces the concept of 'Risk' in the context of project and product development, emphasizing its unpredictability and potential impact. The main objective of testing is highlighted as identifying defects and mitigating risks to ensure the project's successful completion. The paragraph distinguishes between 'project risk', which involves organizational, technical, and supplier factors that can impede the project's objectives, and 'product risk', which pertains to the potential failure areas of a deployed product. The responsibilities of the test manager in analyzing and mitigating these risks are underscored, along with the importance of including risk considerations in the project's summary report according to IEEE standards.

05:01

🛡️ Proactive Risk-Based Approach in Testing

The second paragraph delves into the proactive versus reactive approaches to risk management, advocating for a proactive stance to reduce product risk from the project's inception. It discusses the significance of risk identification in the initial stages of testing, emphasizing its role in shaping test planning and execution. The paragraph outlines the benefits of risk identification, including the determination of necessary test techniques, the extent of testing required, prioritization of tests to uncover critical defects early, and the identification of non-testing activities that can enhance product quality. The focus on risk-based testing and the need for stakeholders to be aware of expected risks and the testing strategies to address them is also highlighted, aiming to minimize uncertainty and increase the effectiveness of risk management.

Keywords

💡Risk

Risk, in the context of the video, refers to an unexpected event that could potentially impact a project or product negatively. It is characterized by its probability of occurrence and the severity of its impact. The video emphasizes the importance of identifying and managing risks to ensure the successful completion and deployment of a project or product. For example, the script mentions that risk can be assessed based on the 'probability of the adverse event' and the 'impact which is caused by this event'.

💡Project Risk

Project Risk pertains to the potential hazards that could affect the ability to achieve the project's objectives. The video divides these risks into three categories: Organizational, Technical, and Supplier risks. Organizational risks might include team skill shortages or interpersonal conflicts, as mentioned in the script, such as 'shortage of skills, or training that the team needs' or 'personal issues, between members of the team'.

💡Product Risk

Product Risk is the set of potential issues that could affect the product after it has been deployed. These risks are the responsibility of the testers and can include the quality of the product, its functionality, and its ability to meet the intended objectives. The script illustrates this with examples such as 'poor data integrity & quality' and 'if our software didn't achieve the intended action'.

💡Testing

Testing, as discussed in the video, is the process of evaluating a system or its components to detect defects and decrease risks. The main objective of testing is to find defects and identify when to start, continue, or stop the testing process. The script connects testing with risk management by stating that 'the main objective of course is to find defects and decrease risks'.

💡Test Manager

The Test Manager is responsible for overseeing the testing process and ensuring that risks are identified, managed, and mitigated. The video highlights the importance of the Test Manager's role in having 'high project management skills' to handle risks effectively. For instance, the script states that the Test Manager should be able to 'analyze, manage and mitigate all risks'.

💡Risk Management

Risk Management is the process of identifying, assessing, and controlling risks. The video describes it as a critical part of the testing process, where the Test Manager must plan and execute strategies to mitigate risks. The script mentions that 'solving all these problems is the responsibility of the test manager', emphasizing the proactive approach needed in risk management.

💡Proactive

Being proactive in the context of the video means taking action in anticipation of risks to prevent or minimize their impact. The video encourages a proactive approach to risk management, rather than a reactive one, to reduce product risk levels from the initial stages of a project. The script uses the term in the phrase 'a proactive opportunity to reduce the product risk level'.

💡Risk Identification

Risk Identification is the first stage of risk management, where potential risks are recognized and assessed. The video explains that this process should be considered during various stages of testing to ensure that all possible risks are known and addressed. The script points out that risk identification helps in determining 'which parts can cause bugs and form a product risk'.

💡Risk Based Approach

A Risk Based Approach is a strategy that focuses on identifying and addressing risks that could potentially have the most significant impact on a project or product. The video discusses this approach in the context of testing, where it is used to prioritize testing efforts and reduce uncertainties about risks. The script mentions that 'the risk based approach we previously mentioned, we've said that we should be either, proactive or reactive'.

💡Risk Based Testing

Risk Based Testing is a testing methodology that focuses on identifying and testing areas of a project or product that pose the most significant risks. The video emphasizes the importance of stakeholders being aware of expected risks and the testing required to mitigate them. The script states that 'risk based testing' ensures that all stakeholders 'should be aware of all the expected risks'.

💡Defects

Defects are errors or faults in a system that can cause it to behave incorrectly or fail to perform its intended functions. The video discusses defects in the context of testing, where the main objective is to find and fix these defects to decrease project and product risks. The script mentions that testing aims 'to find defects and decrease risks'.

Highlights

Risk is defined as any unexpected event that can be identified by its probability and impact.

The main objective of testing is to find defects, decrease risks, and determine when to start, continue, or stop the testing process.

Risks can be categorized into project risks, affecting the ability to deliver objectives, and product risks, impacting the deployed product.

Project risks include organizational, technical, and supplier factors that can negatively affect the project.

Organizational factors encompass skill shortages, personal issues, political issues, and disrespect towards testing efforts.

Technical issues involve incorrect requirements, test environment unavailability, and low-quality design, code, and data.

Supplier issues arise when external components or tools lack support, causing work stoppages and problems.

The test manager is responsible for solving project risks using high project management skills to analyze, manage, and mitigate risks.

Product risks include potential failure areas, poor product quality, data integrity issues, and software not achieving its intended action.

Testing aims to reduce the risks of adverse effects by identifying where to start testing and where to test more intensively.

Risk identification is crucial for determining test techniques, extent of testing, prioritization of tests, and non-testing activities to reduce risks.

A proactive risk-based approach is essential for reducing product risk levels from the initial stage of a project.

Risk management effectiveness depends on identifying and considering product risks during test planning and execution.

Risk identification helps in prioritizing important parts of the product to find suitable solutions and reduce product failure rates.

Risk-based testing ensures that stakeholders are aware of expected risks and the required testing to mitigate them.

The focus of risk management, control activities, and risk-based approaches is on finding and addressing risks to reduce uncertainty.

Transcripts

Project & Product Risk

In this video, we will talk about one topic

called "Risk". Without explaining

what is risk? Any event which is

unexpected to happen.

In case it happened

what is its level?

It can be identified according to

the probability of the adverse event

or the impact which is caused by this event.

Before discussing this part,

we need to remember

what was the objective of testing?

The main objective of course is to find defects and decrease risks,

and to say when we need to start testing process

when we need to continue

and when to stop.

In this part, we'll talk about risk

and that we can divide it into

two sections:

Either I am still working on the project

and not finished, and we call it

"the project risk"

or the project was deployed and

became a product, and therefor we will call it

"the product risk". Let's see which factors

we will find in both of them.

The project risk is all the risks around the project

which affect capability to deliver objectives.

They are 3 factors:

Organizational- Technical- Supplier.

The first one is Organization factor.

We may find shortage of skills

or training that the team needs

or a shortage of stuff.

Also, there may be personal issues

between members of the team, and this,

of course, will affect our project negatively.

There are also the political issues

e.g. if the testers have a problem with

communicating to their needs and test result.

There may be also a team failure

to follow up on the information they found

in the testing and reviews.

For example, they don't try to

improve the development and test practice.

There is a very important issue happens

in the organization which is

disrespect or improper attitude

towards the efforts of the test team.

These are most of the organization factors

that can put our project at risk.

So, what are the technical issues?

It is to take incorrect requirement

or not being able to meet the requirements because of

some existing constrains.

Another example: the test environment

may not be ready at the beginning

of testing. Moreover,

if you are working on an application and

you were merging data from a platform to another.

then this data had late conversion

or when migration planning and development

have technical issue. In addition,

you may have design, code,

configuration data,

test data and test of low quality .

The third category is

the supplier issues like:

If I get the components from outside

or If I work with a tool which

is no longer used, I don't have anyone that can teach me

how to use it. and when it has a problem

I can't find any technical support.

so any third party that I get

from another company, has some

issues, and when I get back to the company

I got it from, I don't find any support.

Of course, this will stop my work

and cause many problems.

So, who is the responsible for solving these problems.

Solving all these problems is the responsibility

of the test manager. He should has

high project management skills

to be able to analyze,

manage and mitigate all risks.

At the end of the project and according to IEEE standards,

as we previously mentioned, the test manager

should mention in the summary report

what the test plans requires are

and what the contingencies are.

Now we've finished the risks that threats

the project. what about the risks that

threats the product!

After finishing the project deployment,

there are many other factors for which

we as testers are responsible,

for this product to pass or fail

or to have risks. For example:

potential failure areas,

these are the adverse future events or hazards.

here we are talking about the quality of the product,

whether during the software delivery

or also software or hardware.

This can cause problems to the company

or the individuals.

The software also may be produced with

poor characteristics, whether in

functionality, reliability, usability or performance.

we may have poor data integrity & quality

Such problems will be clear

in data migration, data conversion ,

and data transport problem

in addition to violating data standards.

Finally, we may face the worst which is that

if our software didn't achieve the intended action,

which was required.

this means that the software didn't

achieve the objective for which it was made.

so, here, we use the risk to

identify where to start testing ,

and where to test more.

Therefore,

testing reduces the risks of

the adverse effect or it decreases

the impact of adverse effect.

Let's talk about

the product risk and its responsibility

towards the project success.

Does every time we conduct testing,

the risks increased or decreased?

Of course, they should decreased.

as while I am testing

I should give feedback all the time.

so whenever problems appear

they will be reduced in our product.

At the end, according to the risk based

approach we previously mentioned

we've said that we should be either

proactive or reactive.

As it is a risk, and it still will happen

so will you deal with it as proactive or reactive?

Ofcourse, proactive.

So the risk based approach you chose to

use is a proactive opportunity to

reduce the product risk level,

starting from the initial stage of a project.

one of the tasks that affects the choice of

the approach we will use is,

the identification of product risks.

what is this?

This is the first stag of risk management.

so it has to be considered

during the test planning and

control, specification,

preparation and execution of test.

If it wasn't considered

and we didn't confirm that

we've known the risks very well

and we have covered all the possibilities from

the beginning, so the risk management

effectiveness will not have an

effective role in handling

those kinds of risks.

what does it determine?

It determines which parts can

cause bugs and form a product risk

in addition to prioritizing the important

parts to find suitable solutions.

Then we should implement actions

to deal with these risks

In order to reduce the percentage

of the product failure.

One of the advantages of

the risk identification that by doing it

I will be able to identify 4 important things:

-the test techniques which I need

to apply during testing.

-the extant of testing which will be done.

-Prioritizing the tests

and this allows us to find

the critical defects as early as possible.

-the non-testing activities could be employed

to reduce risks, but how?

e.g. if we need the working team

to have a training course, this is not related

to the testing activities in the project.

but it may affect its quality.

we've discussed the risk based approaches

and we should have risk identification

from the beginning.

The last point is

the risk based testing. this one cares

that all the stakeholders

should be aware of all the expected risks.

and what is the required testing

that we can relay on in order to

face the risks. All what we've discussed

starting from: risk management and

control activities, risk based approach,

identification of product testing,

and the risk based testing,

their focus is on

how to find out risks

that may happen.

and you should have some ways

and solutions to face this type of problems

in order to reduce the uncertainty about risks.