Skip to content
BENIBIX Learn

Risk, Quality & Procurement

What could go wrong, what good enough means, and buying work in from outside · 35 terms

Sort
Compare

Project Risk

7

What a risk is, good and bad, how risks are ranked, how much risk to take, and who watches each one.

Something that may or may not happen. If it did, it would change the project.

A risk that would help the project if it happened. People also call it a good chance.

How much risk a group is willing to take on to reach its goals.

A warning sign that a risk is about to happen. It tells the owner to act.

The one person who watches a risk and makes sure it is handled.

A grid that ranks risks by how likely they are and how bad they would be.

A risk's chance times its cost, in money. It shows what the risk is worth.

Risk Responses

8

The moves a team can make about a risk, the plan kept ready for when it happens, and the risk a response leaves behind.

The plan for what to do about a risk. Avoid it, shrink it, hand it off or accept it.

Changing the plan so a threat cannot happen at all.

Acting now to make a threat less likely. Or to make it hurt less if it comes.

Moving the cost of a threat to someone else. Insurance and contracts do this.

Choosing to live with a risk. You do not act on it ahead of time.

A plan made ahead of time. It is used only if the risk comes true.

The risk that is still left after you have dealt with it.

A new risk that is created by the response to another risk.

RAID Log

5

The logs a project keeps for its risks, guesses and problems, and the things that go in them.

One table for four lists. It holds a project's risks, guesses, problems and waits.

The list where a project keeps each risk, its owner and its plan.

A guess the plan treats as true. Nobody has proved it yet.

A problem that has already happened on a project. It needs a fix now.

A list of a project's open problems. It says who fixes each one, and by when.

Project Quality

8

What good enough means for a result, how the work and the product are checked, and what quality costs.

How well a project's result meets the needs it was built for.

The level of features a product has. A low grade is a choice, not a fault.

Checking and fixing how work is done, so faults do not happen.

Testing the finished work for faults. It is done before the customer gets it.

The money spent to get quality right. Plus the cost of getting it wrong.

Quality Tools

3

Charts and methods for finding why faults happen and which causes matter most.

Finding the deepest reason a problem happened. Then it can be fixed for good.

A chart shaped like a fish skeleton. It sorts the causes of one problem.

A sorted bar chart that shows which few causes make most of the problems.

Procurement

7

Buying goods or work from outside: deciding to buy, describing the work, asking for offers and signing the deal.

How a group buys goods or work from sellers outside it.

Choosing to do the work yourself, or to buy it in. Cost is only one part of it.

A paper that spells out the work a seller will do. It says by when, and how well.

A paper that asks sellers how they would do a job. It also asks the price.

Contract Types

3

Ways to pay a seller, sorted by who pays when the job costs more than planned.

A contract with one set price for the job. The seller pays if it costs more.

A contract that pays for each hour worked. It also pays for the materials.

A contract that pays the seller's real costs. A fee on top is their profit.